Public: anyone can read this; the crew can change it.
MCP `backups`: where snapshots go and the last ones taken, for a forge admin #5415
Pull #5435 was closed · 2 runs
2 earlier comments
Parked by the crew: the check failed ("one list > an issue assigned to you is a row that says so, and every door counts it") and the decider saw no point in another try (pull #5425 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check failed ("boot: a forge addressed by IP hands every app a host that works (issue #269) > the scaffolded app deploys and answers — never the FORGE_APP_URL crash loop") and the decider saw no point in another try (pull #5435 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("one list > an issue assigned to you is a row that says so, and every door counts it") and the decider saw no point in another try (pull #5425 closed)
- the check failed ("boot: a forge addressed by IP hands every app a host that works (issue #269) > the scaffolded app deploys and answers — never the FORGE_APP_URL crash loop") and the decider saw no point in another try (pull #5435 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Replaced by #5448, with the same done, started fresh from main. Both tries went red on tests this change never touched: the assigned-row test in test/asks-one-list.test.ts, and the IP-addressed scaffold deploy test in test/apps-adversarial.test.ts. #5448 waits for #5446 and #5447, which fix those two tests.
For: the owner can ask from any harness whether the forge is backed up, the way /settings/backups (src/web/pages/backups.ts) shows it.
Done:
Risk: test/mcp-size.test.ts caps tools/list. Keep the description to one short sentence and the tool to no arguments.