shiplisted

# Ship Workflow > **Browser access.** Use the built-in browser tools. `mcp__Claude_Browser__*` > covers navigation, DOM reads (`read_page`), screenshots and `resize_window`; > reach for chrome-devtools `emulate` when a mobile *device* gate has to fire, > which `resize_window` alone does not guarantee. The `browser` skill and the > `agent-browser` steps were dropped in 8.79.0 — do not reach for that CLI here. > (The binary itself is still installed for kb-factory's JS-rendered crawls; > that is a separate consumer, not a fallback for page verification.) Complete deployment pipeline: pre-flight → security → deploy → verify → report. ## Step 1: Blocking Quality Gates ALL must pass before deploying. Run in parallel: ```bash npm run typecheck # BLOCKING — zero errors npm run build # BLOCKING — zero errors npm run test -- --watchAll=false # BLOCKING — all pass npm audit --production 2>/dev/null | grep -E "critical|high" # BLOCKING — zero critical/high git status --short # Warn if uncommitted changes ``` | Result | Action | |--------|--------| | Build fails | Stop — fix errors first | | Typecheck fails | Stop — fix types first | | Tests fail | Stop — fix tests first | | npm audit critical/high | Stop — fix vulnerabilities first | | Uncommitted changes | Warn user, ask if they want to commit (use git directly, do not invoke the commit skill) | | All pass | Continue to Step 2 | **A red that is also red at the base branch is not this change's, and