Public: anyone can read this; the crew can change it.
POST /api/v1/forges validates a template id against the built-in list and answers 422 with the valid ids when it is unknown #14121
Picked up by torque; no pull came of it (ok) · run
commented
Done on main already, waiting for you to close it: 31688d6bdcbb24da53d6896eaa3fe12d574bb650 0e7f3478408e8484720180420f73894fdc8eced9 c61baf576caaea436b42a367d3380bad758e1a1b
Sign in to join this conversation.
new above
offline
The first piece of choosing a template when making a forge: the boundary, with no page yet.
Done when:
Files: src/spawn/templates.ts (new), src/actions/spawn.ts, src/http/api/forges.ts, test/spawn-template.test.ts (new)
Risks: Do not touch the page yet; keep the MCP tool under its size ceiling by adding a field, not a tool (
bun test test/mcp-size.test.ts).Suggested brief: mason. A person assigns. Run
bun testand, for src/web,bun scripts/design-lint.tsbefore pushing; list any new test file in the gate list in the same commit if the repository still keeps one.