public-demo-session

# Public Demo Session Use this skill when the goal is a public recording, README demo, screenshot, or clean transcript. The priority is a short, reliable demo surface, not exhaustive orchestration. ## Goals - Show only a public-safe workspace path such as `/llm-cli-gateway`. - Keep the llm-cli-gateway MCP server and workspace skills available. - Prefer direct, synchronous provider calls that return compact text. - Avoid validation wrappers, async polling, nested Codex, and repeated stuck-job polling unless the user explicitly asks for those features. ## Full-access review handoff A public demo is not a review shortcut. If the user explicitly asks for a full-access, native-MCP, evidence-backed review, leave demo mode and follow the `multi-llm-review` full-access protocol. Build the exact target checkout and launch `node dist/index.js --transport=stdio` from it, rather than using a demo or globally installed gateway. Reapply the provider-native grant per new job, send the corrective-program verification report and exact diff/file identity, require independent code/docs/tests inspection, set no caller caps, and honor a user-required 90-second progress cadence. Do not use direct provider calls or a public demo home as a substitute for that review path. ## Path Hygiene Do not start Codex directly from an internal checkout path for public demos. A symlink may still leak a resolved path in some tools. Prefer a bind-mounted public path: ```bash bwrap \ --bind "$REAL_REPO" /...