What problem does it solve? Re-applying the brain repo's v2 demo stack involves a fragile sequence of secret-store setup, recipe application, corpus git initialization, and smoke verification, where small mistakes (stale servers, concurrent applies, unsigned commits) silently wipe the stack or revert credentials. ## Core Features & Use Cases - Guided demo apply procedure: Walks through secrets.ts store setup, apply-recipe.ts execution, and serve-ui.sh restart in the correct order with fail-closed gates. - Pitfall catalog: Documents concrete failure modes such as git signing breaking corpus commits, concurrent applies overwriting .sandbox-credentials.json, and semantic retrieval invalidating denied probes. - LLM provider wiring: Explains how GBrain reads provider keys from Postgres config, the openrouter:<vendor>/<model> id format, and includes a scored model decision matrix in references/model-choice.md. - Use Case: After editing demo-v2.recipe.yaml, follow the skill to re-apply the recipe, restart serve-ui.sh, and confirm the per-persona smoke suite passes before presenting the demo. ## Quick Start Ask the assistant to re-apply the v2 demo recipe in ~/dev/brain and verify the smoke suite passes before launching the demo UI.