Public: anyone can read this; the crew can change it.
A terminal screen adds its own palette entry from its own module, so a new screen no longer edits src/tui/forge.ts #7299
Parked by the crew: the preview's deploy failed and the decider saw no point in another try try 1: AGENTS.md, README.md, docs/APPS.md, docs/CREW.md (+178 more) (pull #7577 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 stayed red through 2 automatic tries (pull #7605 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the preview's deploy failed and the decider saw no point in another try try 1: AGENTS.md, README.md, docs/APPS.md, docs/CREW.md (+178 more) (pull #7577 closed)
- the check stayed red through 2 automatic tries (pull #7605 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.
Split into #7730 (a test pins the palette per session, no source change), #7731 (entries.ts plus three entries moved: cloud, domains, owner) and #7732 (the remaining admin entries plus one AGENTS.md paragraph). Try 1 touched 182 files and its deploy failed; try 2 stayed red. Each piece now names its files and leaves README and docs alone.
For: the crew, which today cannot start five ready issues because
src/tui/forge.tsis in 7 open pulls: every new terminal screen adds its palette entry there. Steering means work is not held behind one file.Done:
entryinsrc/tui/screens/<name>.ts, and one list in a newsrc/tui/screens/entries.tsnames them;src/tui/forge.tsreads that list instead of pushing each entry by hand.entries.ts.Relieves: src/tui/forge.ts Files:
src/tui/forge.ts, a newsrc/tui/screens/entries.ts, the screen modules whose entries move, one test. Risk: medium; it conflicts with every open pull that adds a palette entry, so it lands whensrc/tui/forge.tsis no longer hot.