sandbox-aware-browser-pipeline-executionlisted

# Sandbox-aware browser pipeline execution ## When to use Use this when a Node/TypeScript CLI pipeline uses browser automation or `imperium-crawl`/Playwright-style resources and: - A command finishes its logical work but the process hangs. - Browser phases work in a normal terminal but fail or behave differently under Codex sandbox. - The user asks to use Codex in headless mode while the task includes real browser/network scraping. - The pipeline depends on a location-specific VPN, e.g. Miami, before running OCS/OR or official-records phases. - Lead outputs are generated but marked `NOT_SAFE_TO_SEND` because official evidence/enrichment gates are incomplete. ## Steps 1. **Separate “code brain” from “real browser execution.”** Treat Codex as the coding/diagnostic worker: ```bash codex exec 'Inspect why the enrichment CLI hangs after completion and propose a cleanup fix' ``` But do **not** rely on Codex sandbox for real browser pipeline runs. Browser phases should run from a normal Hermes/system terminal, not inside the Codex sandbox, because Chromium/browser sandbox and namespace operations can be blocked there. Working rule: - Codex = code, analysis, refactor, tests. - Normal Hermes terminal = real Playwright/browser/pipeline execution. 2. **Confirm you are in the correct repository before starting Codex.** Codex CLI requires a git repository. If `git status` reports: ```text fatal: not a git repository ``` locate the actua