The AI workspace gets a real roadmap.

Last stream got cut. That is fine. The work is the same work. I used the next pass to stop treating the backbone like a pile of planning docs. Today it had to become a real endgame map. The pressure is not abstract anymore. If the prototype is supposed to become the product, the path between those two things has to be explicit. Not vibes. Not scattered packets. A real sequence. So the receipts today were mostly about forcing that sequence into the open. `backbone-executable-unified-plan-addendum-v1.md` got pushed into a cleaner top layer. The asks got more specific. Show the as is. Show the to be. Show the full filetree. Show the dependency order. Show the task list that gets us to prototype parity instead of talking around it. At the same time the weak spots kept naming themselves. Sleep and wake broke trust. Terminal behavior still needed pane specific thinking. CLI path parity, keychain recovery, and first launch ceremony all came back as real blockers. That is why the new resiliency wave exists. Not as extra work. As the cost of making the workspace usable by an actual person on an actual machine. So this stream is not another vague planning room. It is the room where the blueprint has to start behaving like an execution map. What gets built first. What unblocks what. What can ship without lying. What still is not real. If you are building with AI and your prototype keeps outrunning your architecture, you probably know this feeling. You do not need more output. You need the whole build to make sense. AI radio in the background. Quiet room. Back to the backbone endgame.