docs(audit): refresh production audit dashboard and release checklists

[POWERFULMOVES]

Summary\n- refresh pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md with 2026-02-24 lock-step release closeout status\n- add current production addendum to pmoves/docs/audit/PRODUCTION_VALIDATION_CHECKLIST.md with deterministic validation chain\n- update pmoves/docs/integrations/SUBMODULE_PRODUCTION_RELEASE_CHECKLIST.md with release-wave status and remaining blockers\n- sync pmoves/docs/PMOVES.AI PLANS/ROADMAP.md and pmoves/docs/NEXT_STEPS.md to current merge/backlog state\n\n## Context\nThis follows completed merge wave #703 -> #704 -> #700 -> #701 -> #702 -> #699 and records remaining production blockers (AB-4/5/6/9) plus runner queue recovery work.\n\n## Testing\n- docs-only update\n- verified repository state and PR/merge metadata via gh pr view and gh pr list before writing updates

Summary by CodeRabbit

• Documentation
  • Updated release status and production readiness tracking across audit and validation documents.
  • Added comprehensive production validation procedures, bring-up commands, and rollback guidance.
  • Enhanced release wave checklists with deterministic validation sequences and deployment health checks.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Rate limit exceeded

@POWERFULMOVES has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 50 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 28fa979 and f1471dd.

📒 Files selected for processing (2)

• pmoves/docs/NEXT_STEPS.md
• pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md

📝 Walkthrough

Walkthrough

Documentation updates across production release and audit files reflecting a completed lock-step production merge wave (Feb 24, 2026), updated blockers status, expanded release procedures, and comprehensive validation sequences for bring-up and security requirements.

Changes

Cohort / File(s)	Summary
Release Status & Metadata pmoves/docs/NEXT_STEPS.md, pmoves/docs/PMOVES.AI\ PLANS/ROADMAP.md, pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md	Updated release timeline from 2026-02-20 to 2026-02-24; logged lock-step production merge closure with commit chain and final promotion hash; updated blocker count from 3 to 4 (added AB-9 runner queue deadlock); incremented PR queue from 0 to 1 (PR #705); refreshed CodeQL and Dependabot alert baselines.
Production Validation & Checklist pmoves/docs/audit/PRODUCTION_VALIDATION_CHECKLIST.md	Added comprehensive addendum with release wave status checkpoints, deterministic validation sequence (shell/gh CLI commands), six-phase bring-up guide with environment audits and health checks, production security checklist, and rollback procedures.
Submodule Release Gates pmoves/docs/integrations/SUBMODULE_PRODUCTION_RELEASE_CHECKLIST.md	Added current release wave status (2026-02-24) and expanded global deterministic gates sequence with ten additional validation steps (submodule-branch-policy-check, submodule-integrity-strict, secrets-audit, ci-runners-lockdown-strict, SUPABASE\_RUNTIME gate, smoke-prod, GPU gate, and others).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Suggested labels

codex

Poem

🐰 Hops through the docs with careful cheer,
Release wave complete—the path is clear!
New gates and checks, procedures bright,
Production ready—all systems tight! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: refreshing production audit documentation and release checklists, which matches the primary focus of the changeset.
Description check	✅ Passed	The description includes a complete summary of changes, context explaining the completed merge wave and blockers, and testing methodology. It covers all critical sections from the template.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/production-audit-dashboard-refresh

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pmoves/docs/NEXT_STEPS.md`:
- Around line 7-13: The commit reference in the NEXT_STEPS.md bullet uses the
full 40-char hash (`1a21c0384a4ed3913bc2ce8a5f68544723ac79d4`) while the
dashboard uses the short hash (`1a21c038`); update the line "final promotion
landed on `main` at commit `1a21c0384a4ed3913bc2ce8a5f68544723ac79d4`" to use
the short hash for consistency (or include both formats like `1a21c038
(1a21c0384a4ed3...)`) so commit formatting matches the dashboard and avoids
confusion.

In `@pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md`:
- Around line 239-256: The checklist runs supa-runtime-guard without the
SUPABASE_RUNTIME env var; update the invocation so it sets
SUPABASE_RUNTIME=compose when calling the supa-runtime-guard target (align with
other docs), e.g., invoke SUPABASE_RUNTIME=compose before the make -C pmoves
supa-runtime-guard call so the guard runs against the compose runtime.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a21c03 and 28fa979.

📒 Files selected for processing (5)

• pmoves/docs/NEXT_STEPS.md
• pmoves/docs/PMOVES.AI PLANS/ROADMAP.md
• pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md
• pmoves/docs/audit/PRODUCTION_VALIDATION_CHECKLIST.md
• pmoves/docs/integrations/SUBMODULE_PRODUCTION_RELEASE_CHECKLIST.md