docs(process-hardening): consolidate repo-productivity tooling + rollout state

[BigSimmo]

What

Tier D (memory consolidation). Promotes the durable knowledge about the repo-productivity program out of session/chat memory into the shared repo record, so future contributors and agents discover the tooling — and how to enable the disabled pieces — without relying on private memory.

Adds a dated "Repo-productivity & automation tooling (2026-07-13)" entry to docs/process-hardening.md covering: pre-push guards + installer, stale-base tripwire, the spend / ops-digest / ingestion-autopilot / ci-triage monitoring (with enablement state), env-parity + branch sweeper, session skills, and the bundle-budget / docs:check-scripts / deps:report CI guards. docs/operator-backlog.md remains the index of human-only enablement steps.

Verification

docs:check-links (774 path refs) and docs:check-scripts (263 npm-run refs) both pass — the entry's own references are validated by the linters this program added. Prettier clean. Docs-only.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added documentation for repository productivity and automation tooling.
  • Documented safeguards for pre-push validation, stale-base detection, environment parity, and branch hygiene.
  • Documented production health monitoring, operational digests, ingestion dry-run support, and CI failure triage.
  • Added guidance for local session skills and advisory or manually triggered checks.

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 second

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 68933499-d264-49eb-9624-a67f6253a828

📥 Commits

Reviewing files that changed from the base of the PR and between b71cc8e and 2ecd302.

📒 Files selected for processing (1)

• docs/process-hardening.md

📝 Walkthrough

Walkthrough

Documents newly added repository automation, operational monitoring, ingestion and CI triage tooling, hygiene checks, local session skills, and advisory or dispatch-only checks.

Changes

Process hardening

Layer / File(s)	Summary
Automation and guardrail inventory docs/process-hardening.md	Adds the “Repo-productivity & automation tooling (2026-07-13)” section covering pre-push guards, monitoring, ingestion, CI triage, hygiene checks, session skills, and advisory checks.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: claude, copilot

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the docs-only update to repo-productivity tooling and rollout state.
Description check	✅ Passed	The description covers the change purpose and verification, though it does not exactly follow the template headings.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/process-hardening-consolidation

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b71cc8ee91

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[BigSimmo]

@codex resolve actionable Codex review findings for this pull request and current head using the repository instructions. This is the pull request's single automatic repair pass: do not perform a fresh review, create new standalone findings, or request another review. Work only the existing unresolved Codex threads on the current head. Always fix P0 and P1 findings. For P2 and lower findings, fix only clear, scoped, low-risk issues; otherwise disposition them with a concise reason. After fixing or dispositioning a thread, reply in that thread with as the first line, followed by a concise summary; that marker authorizes the workflow to close that exact thread. If human input or new authorization is required, do not use the marker and leave the thread open with the blocker. Finish only after every actionable thread is fixed or dispositioned and closed, or explicitly left open for a human decision. Do not update the branch from main, address unrelated reviews, broaden scope, or create more than one scoped fix commit. Do not use external APIs, paid services, credentials, dependency changes, or broad refactors unless explicitly authorized. Add targeted tests where behavior changes and run the narrowest relevant validation.