Turn the workshop references into Codex workflows

Create a Codex primitive map for this repo.
Read AGENTS.md, package scripts, existing skills/plugins/hooks, and MCP config first.
For each repeated workflow, decide whether it belongs in AGENTS.md, a skill, a plugin, a hook, MCP, or a goal file.
Write .notes/codex-primitives/decision.md with the decision, files to create, verification command, and rollback path.

Use browser proof before claiming this UI task is done.
Inspect package.json and AGENTS.md first.
Pick the browser surface that matches the auth and repeatability needs.
Save .notes/browser-proof/<task>/browser-proof.md with URL, viewport, auth context, actions, expected/observed result, console errors, network failures, artifacts, command output, diff summary, and pass/fail.
Redact cookies, tokens, customer data, QR codes, and auth headers.

Act as the CMUX manager.
Inspect the current repo and create a pane plan before opening workers.
Each worker gets one bounded task, writes one markdown receipt, and does not edit outside its assigned files.
Keep a dev-server pane and browser-proof pane visible for web work.
Collate findings into .notes/cmux-summary.md before asking me for decisions.

Use Oracle + PackX for this broad codebase question.
Preview the bundle first.
Build a markdown bundle under ~/.oracle/bundles/<slug>.txt.
Run Oracle in browser mode with a 3-5 word slug.
Read the full Oracle output, write a local plan, implement the first shippable slice, and verify locally before asking Oracle again.

Before starting this goal, externalize state.
Create .goals/<task>.md with objective, constraints, stop condition, and verification.
Create .notes/<task>/ for receipts.
Every major phase must write a checkpoint: research, plan, implementation, verification, final diff review.
If context gets large, compact to .notes/<task>/handoff.md and resume from that artifact.

Design a narrow Codex daemon profile for this repeated task.
Use one command map, one output shape, low reasoning by default, and no broad memory/MCP/plugin access unless required.
Keep it read-only first.
Write docs, examples, and a smoke test before using it on a real repo.

Treat the visual artifact as requirements, not decoration.
Extract acceptance criteria, user stories, responsive states, and proof moves.
Implement only the selected direction.
Verify in browser with screenshots/logs.
Write the durable contract to design.md, .goals/<feature>.md, or .notes/qa/<flow>.md depending on the task.