Trust does something: Until shows its date, and a repo can follow several trusted forks at once #9003

2026-11-03 01:26Z. I added tdobbertin-espo, jmoran, benjivers (git.open-platform.sh) and benjivers (forge-apps.benjivers.com) until 2026-12-02 at Settings > Trusted sources. Two gaps:

1. The list reads "Until just now" for all four. Likely timeAgo on a future date. Show the date and how long is left. Prove the entries aren't already treated as expired, with a test using a date-only input, and refuse what can't be parsed.
2. Nothing can fold in yet. A trusted pull only exists when "the upstream follow" opens it from the followed address, but a repository follows one parent: trevato/forge follows trevato/forge-upstream, with upstream: null, and trevato/foundry answers not_a_fork: this repository follows nothing because it was migrated. The owner wants these to flow now: jmoran/forge-jay into trevato/forge, tdobbertin-espo/forge, benjivers/forge, and foundry from https://forge-apps.benjivers.com/apps/foundry.git.

Done when:

• [x] A repository can follow any number of sources by URL (a forge or a Forgejo fork, read anonymously or by origin), each with its branch, shown on one line each in settings, and added in one action. A migrated repo can link back to where it came from.
• [x] A new commit on a followed source of a trusted account opens or updates one pull, stamped with its source, resolved by the crew if it conflicts. Others' commits wait as guests.
• [x] Reaches other forges from the forge process, tested against a fake Forgejo.
• [ ] One big first fold (149 commits and 90 conflicting files for jmoran) doesn't flood: it becomes one pull, reviewed by the crew, and lands by true merge (#8935).
• [ ] Live-tested: I'll follow the four sources once it's out, so note it on the pull.

Reviewed pull #9004 at its head: ticked A repository can follow any number of sources by URL (a forge or a Forgejo fork, read anonymously or by origin), each with its branch, shown on one line each in settings, and added in one action. A migrated repo can link back to where it came from.; A new commit on a followed source of a trusted account opens or updates one pull, stamped with its source, resolved by the crew if it conflicts. Others' commits wait as guests.; Reaches other forges from the forge process, tested against a fake Forgejo.. left open: One big first fold (149 commits and 90 conflicting files for jmoran) doesn't flood: it becomes one pull, reviewed by the crew, and lands by true merge (#8935). — Only shown against a fake forge. A real 149-commit fold has not been tried.; Live-tested: I'll follow the four sources once it's out, so note it on the pull. — The owner's live test has not happened yet..

Left open after pull #9004 landed: 2 unticked items remain (One big first fold (149 commits and 90 conflicting files for jmoran) doesn't flood: it becomes one pull, reviewed by the crew, and lands by true merge (#8935).; Live-tested: I'll follow the four sources once it's out, so note it on the pull.). 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.

Split. The first open box (one big first fold does not flood: one pull, crew-reviewed, true merge) is now #9024, which waits for #9010 (reviewed slices) and #9015 (true merge for trusted sources). The second box (live test of the four sources) is a step for the owner, not a builder. It is noted on #9024, and no builder issue is opened for it.