ENNEAGRAM-LLMS-TXT-PRODUCTION-REVALIDATION-01: revalidate Enneagram llms.txt release

[fermatmind]

What changed

• Added read-only production revalidation evidence for Enneagram llms.txt release.
• Recorded /llms.txt Enneagram 116/116 and /llms-full.txt Enneagram 0/116 with locale/entity distribution and safety counters.
• Reconciled stale LLMS release ledger state using the exact prior authorization/deploy/readback evidence.

Why

• ENNEAGRAM-LLMS-TXT-RELEASE-01 has completed and the frontend fix is deployed; this PR closes the production evidence loop before llms-full readiness work.

Validation

• ruby -e "require 'yaml'; YAML.load_file('docs/codex/pr-train.yaml'); puts 'yaml ok'"
• python3 -m json.tool docs/codex/pr-train-state.json >/dev/null
• python3 -m json.tool generated/enneagram-llms-txt-production-revalidation/revalidation-report.json >/dev/null
• Python report assertions for llms.txt 116, llms-full 0, exact locale/entity counts, zero duplicate/malformed/non-apex/forbidden counters, and zero side effects
• git diff --check

Deferred items

• No CMS/DB write.
• No llms eligibility mutation.
• No Search Queue or IndexNow.
• No cache warm.
• No deploy.
• llms-full release remains gated by separate readiness and authorization.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 91f29da961

ℹ️ 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]

Do not complete release while EN13 refresh is blocked

This item still declares ENNEAGRAM-EN13-EVIDENCE-CMS-REFRESH-01 as its dependency, but that dependency is currently blocked_readback_repair in the same state file (docs/codex/pr-train-state.json:88824-88830), and the manifest says the llms release runs only after the exact EN13 refresh (docs/codex/pr-train.yaml:41320-41329). Marking the release completed here unblocks the dependent production revalidation and records a production llms release despite the failed prerequisite, so keep this blocked/pending until the refresh item is completed or reconcile that dependency first.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e12bbfc79e

ℹ️ 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]

Close the release authorization check before completion

When this production-write release is marked completed, the ledger still leaves its primary authorization check at pending_exact_production_authorization. Any downstream PR-train check or reviewer that treats checks.*.status as the audit source will see a completed llms release whose exact deployed-SHA authorization is still pending, which makes the release state internally contradictory; either update this authorization check with the pass evidence or keep the item non-completed until the authorization is closed.

Useful? React with 👍 / 👎.