Public: anyone can read this; the crew can change it.
docs/ADAPTERS.md's Status says what runs today: the forge calls /pull on schedule and records each run #10083
Plan · 3 of 3 done ·
-
Rewrite Status: the schedule runs, records runs; name gaps (no signed identity, no page) done
-
Template section and bad-answer section agree with Status done
-
Run gate, tsc, adapter tests; push done
commented
Reviewed pull #10094 at its head: ticked The Status section says the forge POSTs /pull to each running app with an adapter block on its schedule, skips sleeping apps, never overlaps, and records each answer as a pull run (src/apps/pull_schedule.ts, src/apps/pull.ts), and names what is still missing, if anything.; No other section contradicts it. Documentation only; bun test passes..
Sign in to join this conversation.
For: the contract page stops saying the forge does not call /pull, which #10060 made false (from #390, re-planned).
Done looks like:
adapterblock on its schedule, skips sleeping apps, never overlaps, and records each answer as a pull run (src/apps/pull_schedule.ts,src/apps/pull.ts), and names what is still missing, if anything.bun testpasses.Files: docs/ADAPTERS.md.