Skill update

[RyshMan]

Summary

Describe the change and operator impact.

Contract Impact

• No public contract changes (flags/JSON/schema/exits/help/docs)
• Public contract changes are included and documented below

Contract details:

• CLI/flags/help changes:
• JSON output changes:
• Schema/versioning changes:
• Exit code behavior changes:

Tests and Lane Evidence

List commands you ran and outcomes:

make lint-fast
make test-fast
make test-contracts
make test-scenarios
make test-docs-consistency

Additional scoped commands:

• Acceptance lane evidence included when behavior is operator-facing.
• Cross-platform/path behavior reviewed for touched surfaces.

Docs and Source of Truth

• User-visible behavior changes include docs updates in the same PR.
• Docs updates follow docs/map.md source-of-truth guidance.

Risks and Follow-ups

• Determinism/fail-closed/security risks:
• Deferred follow-ups (if any):

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a93b0b88bb

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

[chatgpt-codex-connector]

Apply Codex settle gate in hotfix PR loop

Step 10 makes Codex settle status a mandatory pre-merge condition, but the hotfix path still says to merge after CI green without re-running that gate; this creates a bypass where post-merge red fixes can be merged unreviewed even though the workflow now treats Codex review as required. In a real incident-response cycle, this weakens the exact control this change introduced, so the hotfix loop should require the same settle check before each hotfix merge.

Useful? React with 👍 / 👎.