Public: anyone can read this; the crew can change it.
On a new forge with included credit, the first ask builds: today it says "Received" and nobody ever takes it #11278
Parked by the crew: the check stayed red through 2 automatic tries (pull #11280 closed; its branch mason/11278-on-a-new-forge-with-included-credit-the at 66853ebe5894 keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
try 1: docs/features/starter-crew.md, src/actions/first_ask.ts, src/tui/screens/dashboard.ts, src/web/pages/new-forge.ts, src/web/pages/next-steps.ts, src/web/… try 2: test/tui-first-tell.test.ts try 3: no files changed
Parked by the crew: the check stayed red through 2 automatic tries (pull #11314 closed; its branch mason/11278-on-a-new-forge-with-included-credit-the at fe0e467101a1 keeps the work so far).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check stayed red through 2 automatic tries (pull #11280 closed; its branch
mason/11278-on-a-new-forge-with-included-credit-theat 66853ebe5894 keeps the work so far) - the check stayed red through 2 automatic tries (pull #11314 closed; its branch
mason/11278-on-a-new-forge-with-included-credit-theat fe0e467101a1 keeps the work so far)
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.
try 1: docs/features/starter-crew.md, src/actions/first_ask.ts, src/tui/screens/dashboard.ts, src/web/pages/new-forge.ts, src/web/pages/next-steps.ts, src/web/… try 2: docs/MCP.md, docs/design/audit.md, docs/features/home-plans.md, src/core/reserved.ts, src/http/server.ts, src/tui/screens/dashboard.ts, src/web/chrome.t… try 3: bench/snappy.ts, docs/features/maintenance-budgets.md, src/billing/sync.ts, src/core/migration-pins/20261111130000-maintenance-run-dollars.pin, src/core…
Split by the planner. Cause on main: the first-tell form posts app=forge and composerTell only keeps a thought, so nothing is filed. Split into #11342 (first ask makes a new app and files the ask), #11343 (the card says who took it or what is missing), #11344 (/forges/new wording with included credit), #11345 (console errors on /claim and home), #11346 (journey test + the steward's production probe). Both parked pulls spread across 20+ files; each piece is one module and one test.
Evidence (production 0.7.533, forge probe-qxkv, 2026-11-11 05:40Z). The new forge's first screen showed "What do you want built?" and "The crew is building on $2 of $2 included credit. Add your own key." The ask "A page that says hello and shows today's date." answered "Received." Then the forge showed "forge / nobody is on it yet" and "Its agents are waiting for something to do". No run started and no app changed at 30 s, 90 s or 140 s. The only app on the forge was "forge" (its fork of trevato/forge); the ask appears to have gone to that repository, not to a new app. One console error on
/claimand one on the forge's home.What.
child forge name=probe-qxkvlog lines. Likely candidates to check, in order: the ask filed against the forge repository instead of a new app; autonomy off on that repository; no agent seeded or assigned; the included credit not usable by the child's crew (model access not reaching the cell). Fix the cause that the evidence shows./forges/new's "the crew starts once you add your AI account" is corrected where included credit applies.Acceptance. The journey test (#11158) on a real cell with a stub model: first ask → a new app exists, a run is in progress within 60 s, the app's link shows the change. A production probe after release does the same with the real $2 credit on a throwaway forge and its cost shows against that forge's credit. Do not close this until the production probe passes.