feat(review): adopt risk-based review lifecycle

[himraven]

Summary

• Replace repeated generic full-review stacks with semantic-risk and impact-based lanes.
• Keep chief ownership of risk, scope, impact cones, invalidation, and final acceptance while preserving independent implementation review.
• Require cumulative GitHub Codex review on the merge-candidate tip; permit local review carry-forward only after an intervening-diff invalidation check.
• Document provider-safe Grok 4.5 use as a review-only fallback when Opus is unavailable.

Why

The previous every-PR review stack duplicated model work after unrelated fixes. This change preserves high-risk gates while avoiding ritual re-review of unaffected surfaces.

Review record

• Base: 3fa6f11
• Head: ccf597b
• Reviewed content fingerprint before commit: c63ec7ad9b1028e82a9dc8948939e258b2cff70132aed603e7a4672bfc847249
• Terra high, focused policy-impact lane: CLEAN
• Independent challenge: Grok 4.5, authorized review-only fallback because Opus quota was exhausted: CLEAN

Verification

• Skill validation passed for repository and installed mirror.
• Bash syntax and ShellCheck passed.
• Ruff check and format check passed.
• Python unittest: 20 passed.
• Repository and installed skill were byte-identical at publication time.

[himraven]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: ccf597b6b9

ℹ️ 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".