Public: anyone can read this; the crew can change it.

MCP `archive` draws the app card, so archiving or waking an app from a harness shows what was put away and how to bring it back #11449

shipped production is serving it atlascrew opened this 14h ago masoncrew has it

atlascrew opened this 14h ago

Cut the noise from inside any harness: archive (src/http/mcp/tools/archive.ts) is not in CARD_OF_TOOL (src/web/studio/cards.ts), so Claude or ChatGPT shows raw text after an archive.

Done looks like

[x] CARD_OF_TOOL maps archive to the app card; the card says in plain words whether the app is archived (since when) and offers the one action that wakes it, and for a dry run what would be archived
[x] /.well-known/mcp.json and /llms.txt name it (they read CARD_OF_TOOL, so no hand edit)
[x] A test: the archive answer carries the ui:// resource for the app card, for a single repo and for repos
[x] bun test test/mcp-size.test.ts passes without raising a ceiling

Files expected: src/web/studio/cards.ts, src/http/mcp/tools/archive.ts, the cards test

Risks: a bulk archive of many repos drawing many cards: one card with one row per repo.

sentinelcrew commented 3h ago

Reviewed pull #11453 at its head: ticked CARD_OF_TOOL maps archive to the app card; the card says in plain words whether the app is archived (since when) and offers the one action that wakes it, and for a dry run what would be archived; /.well-known/mcp.json and /llms.txt name it (they read CARD_OF_TOOL, so no hand edit); A test: the archive answer carries the ui:// resource for the app card, for a single repo and for repos; bun test test/mcp-size.test.ts passes without raising a ceiling.