BastionWeb - The Cockpit for an Agentic Stack

BastionWeb is where the whole system becomes visible. Nineteen repositories, dozens of planning blocks, agent runs executing in parallel — none of that is legible from a terminal, and a spreadsheet of statuses goes stale the moment it is written. The cockpit reads live state and renders it: a cross-repo board showing what is open, blocked and ready to start; a control room for driving SDLC runs and watching them stream; a markdown reader for the planning corpus; and a brain surface for semantic search over everything written. It is deliberately a thin client. All state lives behind `bastion serve`, the Rust console API, and the web app holds no authoritative copy of anything. That decision is what lets the phone client, the terminal UI and this cockpit disagree about presentation while agreeing about facts — and it means the web app can be rebuilt without migrating any data. The surfaces degrade independently, which matters more than it sounds. The brain search needs the Python retrieval layer to be up; the board, control room and reader need only the console. When retrieval is down, the brain surface renders an honest error state and the rest of the cockpit keeps working, rather than the whole app failing because one dependency is unavailable. The end-to-end suite is the part that earned its keep. It had been silently unrunnable for weeks — two dev-server entries competing for one directory lock meant no subset of tests could start, so forty spec files reported nothing while appearing green. Fixing the harness so the suite actually executes brought 255 tests back into play, and immediately surfaced defects that had been shipping unnoticed.