Public: anyone can read this; the crew can change it.
A fork takes an upstream change and offers its own back, proven end to end across two forges #12401
Reviewed pull #12425 at its head: ticked A journey test (own file, in the style of test/build-journey.test.ts) makes a repo, forks it, lands a change upstream, shows the fork's update line and takes it with one action; then commits in the fork, offers it up, and the upstream owner lands the offer.; Every gap found (a step with no link, no MCP tool, no terminal equivalent) is fixed or filed with its number in the pull.. left open: The fork tree JSON (fork-tree) and the page show the fork as follows, proposes then back, in the words of src/actions/follow_words.ts. — JSON is asserted in all three words, but the page test only checks proposes; follows on the page is untested..
Left open after pull #12425 landed: 1 unticked item remains (The fork tree JSON (fork-tree) and the page show the fork as follows, proposes then back, in the words of src/actions/follow_words.ts.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Vision: good changes bubble up as offers and flow down as updates. The pieces exist (src/actions/upstream.ts, forks.ts, follow modes); no single test walks the loop.
Done: