Public: anyone can read this; the crew can change it.
Trusted sources fold in by themselves, in real time; everyone else waits for review #8954
Trusted sources now fold in without a person's review. Not covered: the event-driven intake and a live test of the ring. bun x tsc --noEmit is clean.
stopped parked by the crew
3 earlier comments
Trusted sources now fold in without a person's review. Not covered: the event-driven intake and a live test of the ring. bun x tsc --noEmit is clean. 118 tests passed across the autonomy, event-audience, review, upstream-follow, proposal-run, landing and new trusted-sources suites. scripts/gate.ts printed nothing, so I take it as clean. scripts/design-lint.ts is clean. I did not run the full suite, because scripts/fast.ts named 1551 files, so I picked the covering tests myself.
What changed
- Trust list: it keeps
trusted_sourceentries (forge host, account, end date, who set it).tdobbertin-espo,jmoranandbenjiversongit.open-platform.share seeded until 2026-12-02. A lapsed entry stops counting as trusted. Atrust.expiringevent goes out once, 3 days before. - Settings:
/settings/trustedshows the list, a one-click Remove, a form to add an entry, "Stop all folding in" (the kill switch, with Resume) and "Revert landings" per source. Changes are audited astrust.set,trust.removed,foldin.stopped,foldin.resumedandtrust.reverted, and only an admin who is a person can make them. - Landing:
- A pull from a trusted source skips the person only. Its check and boot proof still run, and it lands by true merge with
Landed-fromandLanded-viatrailers. Thepull.mergedevent carries the source. - A trusted pull that touches secrets, credentials, permissions, the contract's walls or release machinery (
src/crew/fold_walls.ts) waits for a person. A diff git can't read counts as a wall. - A red pull still goes back, because the check gate is untouched.
- Tests cover each wall category, the kill switch and expiry.
- A pull from a trusted source skips the person only. Its check and boot proof still run, and it lands by true merge with
- Guests: pulls with a recorded source that isn't trusted show Approve and Decline on
/review, in place of Merge and Close. - Ring: a followed upstream's pull records its source, taken from the upstream address. Work whose
Landed-viaalready names this forge is not proposed again. The test runs three forges in a ring and shows each takes the work once.
What I did not do
- Intake by event:
takeIncominginsrc/crew/fold_in.tsturns a pushed branch into a pull, but nothing calls it yet. Only the follow-upstream path and the autonomy tick's sweep reach folding in today. - Guest isolation: I added no new "nothing runs with secrets" guard. Guest pulls rely on the existing
pullMayRunrules. - Revert by source: it opens revert pulls for a person to land. I did not exercise it end to end.
- Ring test: it exercises the trailer and loop logic, not three live forges.
- Not tried live: I did not boot the app.
Try it: sign in as an admin and open Settings → Trusted sources. Run bun test test/trusted-sources.test.ts. The write-up is in docs/features/trusted-sources.md.
I pushed a new commit to fix the failed check. The gate wanted two lines in a commit message, and the code didn't need to change.
- Why now: the owner asked on 2026-11-02 for trusted sources to fold in live, with three accounts trusted for a month.
- Try: open
/settings/trustedon the preview as an admin. You should see the three entries; Remove one, then press Stop all folding in.
The commit is empty, since the gate only reads commit messages, so the pull's code is unchanged and the tests I ran earlier still apply. I haven't seen the forge's verdict on the new push yet.
I fixed two of the three failing tests and pushed; the third passes here, so I have no fix for it and don't know why it failed in the check.
- Design audit: I added the
/settings/trustedentry todocs/design/audit.md. - Server-Timing sweep: the new page now reports its
sessionandrenderphases, as the telemetry page does.
The third failing test, test/repo-head-quiet.test.ts, checks the byte size of the repository, issues and pulls pages. It passes on my branch, and it also passed with my changes stashed. My change doesn't touch those pages. The check merges my branch into a newer main, so I suspect something that landed on main, or a margin near the byte budget, but I couldn't reproduce it. If it fails again, the next check log should show whether the size is over budget.
Locally, the audit, Server-Timing, repo-head-quiet and trusted-sources tests pass together (31 tests). bun x tsc --noEmit is clean. I have not seen the forge's verdict on this push yet.
Parked by the crew: the check stayed red through 2 automatic tries
Trusted sources now fold in without a person's review. Not covered: the event-driven intake and a live test of the ring.
bun x tsc --noEmitis clean. 118 tests passed across the autonomy, event-audience, review, upstream-follow, proposal-run, landing and new trusted-sources suites.scripts/gate.tsprinted nothing, so I take it as clean.scripts/design-lint.tsis clean. I did not run the full suite, becausescripts/fast.tsnamed 1551 files, so I picked the covering tests myself.What changed
trusted_sourceentries (forge host, account, end date, who set it).tdobbertin-espo,jmoranandbenjiversongit.open-platform.share seeded until 2026-12-02. A lapsed entry stops counting as trusted. Atrust.expiringevent goes out once, 3 days before./settings/trustedshows the list, a one-click Remove, a form to add an entry, "Stop all folding in" (the kill switch, with Resume) and "Revert landings" per source. Changes are audited astrust.set,trust.removed,foldin.stopped,foldin.resumedandtrust.reverted, and only an admin who is a person can make them.Landed-fromandLanded-viatrailers. Thepull.mergedevent carries the source.src/crew/fold_walls.ts) waits for a person. A diff git can't read counts as a wall./review, in place of Merge and Close.Landed-viaalready names this forge is not proposed again. The test runs three forges in a ring and shows each takes the work once.What I did not do
takeIncominginsrc/crew/fold_in.tsturns a pushed branch into a pull, but nothing calls it yet. Only the follow-upstream path and the autonomy tick's sweep reach folding in today.pullMayRunrules.Try it: sign in as an admin and open Settings → Trusted sources. Run
bun test test/trusted-sources.test.ts. The write-up is indocs/features/trusted-sources.md.Closes #8937