Test paths, then save a draft you can recover
A rehearsal trace is evidence of one route, not full coverage.
Read the transitions aloud
Start a fresh rehearsal, choose one route and read the destination immediately after the previous scene. Check pronouns, place, time and objects. A graph can be fully connected while the prose still contradicts itself.
Use the visit trace
The reader shows passage visits in order, including repeated visits. Back removes the last visit and returns to the preceding passage. Restart begins again at the current start. Editing a passage or changing the start restarts the rehearsal, so the trace never pretends to describe an older version of the story.
A rehearsal stops accepting further visits at 200 to keep accidental loops bounded. Restart if you need another test. That limit is an application safeguard, not a limit on how many paths a reader could take in a published story.
Test more than the shortest ending
Try each outgoing choice at every reachable passage. Then revisit shared scenes through different incoming routes. Finally test loops and deliberately missing links. The shortest-path report can help you reach an ending quickly, but cannot certify all combinations or narrative consistency.
Choose the right export
JSON preserves the editable passage graph and start setting. Markdown is a plain-text review draft. SVG is a static diagram with shortened passage titles; the full titles remain in the workspace and JSON. None is an automatic public upload. All three files are generated locally. Review your story before sharing it through another service.
For larger projects that need state or scripting, consider established tools such as Twine or ink. ForkFable is independent and does not import their file formats.