Public: anyone can read this; the crew can change it.
The docs and /settings/origins say plainly that a forge older than 0.7.346 is connected from the newer side, and that upgrading it lets it connect outward too #9626
Reviewed pull #9638 at its head: ticked docs/features/forge-origin-compat.md's matrix has a row or note for "connects outward" by release that agrees with it.; /settings/origins has one plain line under Another forge with the same advice, linking that docs section. A test asserts the line and the link are there..
Left open after pull #9638 landed: 1 unticked item remains (docs/features/forge-origin-older.md has a short section, "Connecting from an older forge". It says the older forge can't start the connection, that connecting from the newer forge (its /settings/origins → Another forge) reaches it today, and that upgrading the older forge to 0.7.346 or later lets it connect outward.). 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.
Replaces #9559. Builders can't lift that limit from this repository: a forge older than 0.7.346 has no forge provider, so it can't start a connection itself. What we can do is make sure nobody gets stuck on it.
Done looks like:
/settings/origins→ Another forge) reaches it today, and that upgrading the older forge to 0.7.346 or later lets it connect outward.Files: docs/features/forge-origin-older.md, docs/features/forge-origin-compat.md, the origins settings page under src/web/, a test. Risks: none in code paths; wording only. Keep it to one line on the page.