docs: refresh documentation for v1.2.0 elevation

.codex/rules/compaction.md

@@ -10,8 +10,8 @@ pipeline safely.
 3. Open `ESCALATE` gates and their `decision_needed` text.
 4. Open `QUESTION:` and `CONCERN:` entries in `pipeline/context.md`.
 5. Stage 4 build areas that are complete.
-6. Stage 5 review files that have been written.
-7. Stage 5 review round count per area, including changes-requested cycles.
+6. Stage 6 review files that have been written.
+7. Stage 6 review round count per area, including changes-requested cycles.
 8. Retry count and owning role for any stage currently retrying.
 9. Stage 9a agents that have contributed.
 10. Whether Stage 9b synthesis completed and which lessons were promoted or

.codex/skills/pipeline/SKILL.md

@@ -132,6 +132,19 @@ If the retrospective contains durable learning, write lines beginning with
 npm run lessons -- promote
 ```
 
+To visualize the final pipeline state:
+
+```bash
+npm run visualize
+```
+
+If budget tracking is enabled (`budget.enabled: true` in `.codex/config.yml`),
+check running totals at any time with:
+
+```bash
+npm run budget -- check
+```
+
 ## Stage Gates
 
 High-value stages have schema-backed required fields:

.gitignore

@@ -22,3 +22,6 @@ pipeline/adr/
 
 # Generated local packaging notes
 docs/pr/
+
+# Runtime visualize artifact (generated by npm run visualize)
+pipeline/diagram.md

AGENTS.md

@@ -69,6 +69,10 @@ instead of creating package metadata just for the framework.
 | `/audit-quick [scope]` | `npm run audit:quick -- "<scope>"` |
 | `/health-check` | `npm run health-check` |
 | Claude parity checklist | `npm run parity:check` |
+| Init budget tracking | `npm run budget -- init` |
+| Update budget after stage | `npm run budget -- update <stage>` |
+| Check budget totals | `npm run budget -- check` |
+| Visualize pipeline state | `npm run visualize` |
 
 ## Local vs Cloud
 

CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to the `codex-dev-team` framework are recorded here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
 the project follows [Semantic Versioning](https://semver.org/).
 
-Per-release detail lives in [`docs/releases/`](docs/releases/). This file
+Per-release detail lives in [`docs/release-notes/`](docs/release-notes/). This file
 is the index and the rolling `[Unreleased]` pointer — it stays thin so
 `git log` diffs between tags are readable.
 
@@ -122,8 +122,8 @@ Codex-native conventions.
 
 ## How to add a new release entry
 
-1. Create `docs/releases/vX.Y.Z.md` following the shape in
-   [`docs/releases/README.md`](docs/releases/README.md).
+1. Create `docs/release-notes/vX.Y.Z.md` following the shape of
+   [`docs/release-notes/v1.0.0.md`](docs/release-notes/v1.0.0.md).
 2. Add a row to the release map table above (reverse chronological).
 3. Move the relevant `[Unreleased]` entries into the release file,
    leaving `[Unreleased]` empty or listing only changes not yet released.

README.md

@@ -73,10 +73,18 @@ examples/
 
 ## Status
 
-`v1.0.0` is at feature parity with the local `claude-dev-team` framework and
-adds Codex-native CLI automation, JSON status/roadmap outputs, deployment
-adapters, strict parity checks, and dogfood install coverage. It remains
-local-only by design until you decide to publish a remote.
+`v1.0.0` shipped at feature parity with the local `claude-dev-team` framework
+and added Codex-native CLI automation, JSON status/roadmap outputs, deployment
+adapters, strict parity checks, and dogfood install coverage.
+
+`v1.1.0` deepened that parity: role prompts fleshed out, audit-phases reference
+added, budget/checkpoint config blocks added to `.codex/config.yml`, approval
+locking hardened, and parity-check coverage expanded.
+
+`v1.2.0` (unreleased, on branch `codex/elevate-with-claude-depth`) adds prose
+depth to all rule files, `scripts/budget.js` and `scripts/visualize.js`, async
+checkpoint auto-pass logic, `EXAMPLE.md`, `CHANGELOG.md`, and `CONTRIBUTING.md`.
+The framework remains local-only by design until you decide to publish a remote.
 
 ## CLI
 
@@ -132,6 +140,10 @@ npm run review:derive
 npm run security:check -- src/backend/auth/session.js
 npm run runbook:check
 npm run autofold
+npm run budget -- init
+npm run budget -- update <stage>
+npm run budget -- check
+npm run visualize
 npm run lessons -- show
 npm run lessons -- promote
 ```

docs/parity/claude-dev-team-parity.md

@@ -1,9 +1,9 @@
 # Claude Dev Team Parity Checklist
 
-Last updated: 2026-04-30
+Last updated: 2026-05-01
 
 This checklist tracks whether `codex-dev-team` is on par with the local
-`claude-dev-team` framework. Release notes remain deferred until v1.0.
+`claude-dev-team` framework.
 
 ## Summary
 
@@ -77,6 +77,13 @@ This checklist tracks whether `codex-dev-team` is on par with the local
 - Deployment adapters are documented and configured locally.
 - Track-aware `next`, `prompt`, and `autofold` helpers reduce manual orchestration.
 - Gate schemas and contract tests guard framework drift.
+- `scripts/budget.js` (`npm run budget`) — opt-in token and wall-clock tracking
+  per pipeline run; escalates or warns when configured maxima are exceeded.
+- `scripts/visualize.js` (`npm run visualize`) — Mermaid stateDiagram-v2
+  generator colors each stage by gate status; output is `pipeline/diagram.md`.
+- Async checkpoint auto-pass logic — `checkpoints.a/b/c` in `.codex/config.yml`
+  accept `no_warnings` or `all_criteria_passed` conditions so unattended runs can
+  advance without a human `proceed` when the precondition holds.
 
 ## Stage Numbering Divergence
 
@@ -108,5 +115,11 @@ eliminates one extra JSON gate file, not the security check itself.
 
 ## v1.0 Blockers
 
-- None. `npm run parity:check` now fails if any command row, required rule,
-  required skill, partial area, or v1.0 gap is present.
+- None. `npm run parity:check` fails if any command row, required rule,
+  required skill, partial area, or known gap is present.
+
+## Parity Status
+
+`v1.0.0` was the initial parity release. `v1.1.0` deepened structural coverage.
+`v1.2.0` (unreleased) adds shared runtime features (budget, visualize,
+checkpoint auto-pass) that go beyond what `claude-dev-team` offers.

docs/release-notes/v1.1.0.md

@@ -0,0 +1,35 @@
+# Release v1.1.0
+
+Date: 2026-05-01
+
+Deepening commit `f852b91 feat: deepen claude-dev-team parity`.
+
+## Verification
+
+- npm run lint
+- npm test
+- npm run doctor
+- npm run parity:check
+
+## What Changed
+
+### Fixed / Expanded
+
+- **Role definitions** fleshed out to 1,287 lines with full working rules and
+  output formats for every role (`pm`, `principal`, `backend`, `frontend`,
+  `platform`, `qa`, `reviewer`, `security`).
+- **Audit phases reference** added at `.codex/references/audit-phases.md` (264
+  lines) covering quick, full, and health-check audit modes.
+- **Budget gate** — `.codex/config.yml` now has `budget.enabled`, `tokens_max`,
+  `wall_clock_max_minutes`, and `on_exceed` fields.
+- **Async checkpoints** — `.codex/config.yml` now has `checkpoints.a/b/c`
+  with `auto_pass_when` conditions.
+- **Stoplist enforcement** — `.codex/rules/pipeline.md` Stage 0 documents the
+  six stoplist triggers that force the full track.
+- **Approval locking** — `scripts/approval-derivation.js` uses atomic file
+  writes to prevent race conditions when the hook fires concurrently.
+- **Parity check** — `scripts/parity-check.js` performs deep structural checks.
+
+## Commits
+
+- f852b91 feat: deepen claude-dev-team parity

docs/release-notes/v1.2.0.md

@@ -0,0 +1,54 @@
+# Release v1.2.0
+
+Date: Unreleased (branch `codex/elevate-with-claude-depth`)
+
+## Verification
+
+- npm run lint
+- npm test
+- npm run doctor
+- npm run parity:check
+
+## What Changed
+
+### Added
+
+- `.codex/rules/pipeline.md` expanded to ~400 lines with full prose for review
+  shape (scoped vs matrix), review file format, READ-ONLY Reviewer Rule, gate
+  merge strategy, review round limit, Stage Duration Expectations, and Parallel
+  Execution Model.
+- `.codex/rules/gates.md` expanded to ~200 lines with Stage-Specific Extra
+  Fields including concrete JSON examples for every codex stage, scoped vs
+  matrix review shape JSON, Stage 08 auto-fold semantics, retry protocol, and
+  ESCALATE shape examples.
+- `.codex/rules/coding-principles.md` expanded to ~110 lines with numbered
+  principles, "what TO do / what NOT to do" code examples, and a Precedence
+  section.
+- `.codex/rules/execution-profiles.md` expanded to ~80 lines covering the three
+  execution profiles (`local`, `app_worktree`, `cloud`) in detail, including a
+  "Parallelism in Stage 4" subsection.
+- `EXAMPLE.md` at repo root — end-to-end pipeline walkthrough for "Add password
+  reset via email", covering Stages 1–9 with real artifact excerpts.
+- `CHANGELOG.md` at repo root — version history following Keep a Changelog.
+- `CONTRIBUTING.md` at repo root — local dev setup, test/lint/parity commands,
+  PR conventions, and stage numbering note.
+- `scripts/budget.js` — budget tracking: `init`, `update`, `check` subcommands.
+  Writes `pipeline/budget.md`, appends per-stage rows, and checks totals against
+  config maxima. No-op when `budget.enabled: false`.
+- `scripts/visualize.js` — Mermaid stateDiagram-v2 generator. Reads active
+  track stages and gate files, colors by status, writes `pipeline/diagram.md`.
+- `scripts/codex-team.js`: `budget` and `visualize` subcommands wired in.
+- Checkpoint auto-pass logic in `scripts/codex-team.js`:
+  `applyCheckpointAutoPass()` called after gate writes; supports `no_warnings`
+  and `all_criteria_passed` conditions; suppressed when stoplist triggers appear
+  in `pipeline/context.md`.
+- `tests/budget.test.js`, `tests/checkpoints.test.js`, `tests/visualize.test.js`.
+- `npm run budget` and `npm run visualize` scripts in `package.json`.
+- `pipeline/diagram.md` added to `.gitignore` (runtime visualize artifact).
+- `docs/release-notes/v1.1.0.md` and `docs/release-notes/v1.2.0.md` created.
+
+## Commits
+
+- 40c29d1 fix(gate-validator): deterministic tiebreaker for latest-gate sort
+- 016d989 feat: elevate codex with claude depth and shared runtime features
+- f852b91 feat: deepen claude-dev-team parity