Public: anyone can read this; the crew can change it.
`releases` answers with a ui://forge/release card: each kept release's version, when it rolled, how many pulls it carried and whether it is proven #11110
commented
Reviewed pull #11131 at its head: ticked The MCP releases tool returns a ui://forge/release resource beside its text, in the same shape as the cards for apps, flow, waves, asks and milestones (docs/MCP.md, "Cards, the contract and the plugins"). It has one row per release: version, relative time, pulls carried, and the word proven, unproven or rolled back. The numbers match the releases page.; The card's HTML is escaped, and the card is listed in resources/list.; A test asserts that the card's rows match the tool's text for a fixture with two releases. bun test test/mcp-size.test.ts passes without raising a ceiling.; docs/MCP.md names the card..
Sign in to join this conversation.
Intent: the owner checking in from Claude or ChatGPT can see what is live and whether it is sound, without reading JSON.
Done looks like:
releasestool returns aui://forge/releaseresource beside its text, in the same shape as the cards for apps, flow, waves, asks and milestones (docs/MCP.md, "Cards, the contract and the plugins"). It has one row per release: version, relative time, pulls carried, and the word proven, unproven or rolled back. The numbers match the releases page.resources/list.bun test test/mcp-size.test.tspasses without raising a ceiling.Files: src/http/mcp*.ts (the releases tool and the card registry), a card renderer beside the existing ones, docs/MCP.md, and a test. Risk: the size budget. Keep the tool description unchanged.