ENNEAGRAM-EN13-EVIDENCE-REFRESH-READBACK-REPAIR-01: normalize evidence refresh readback

[fermatmind]

What changed

• compare JSON evidence/provenance fields by normalized semantic value while keeping scalar fields exact
• add MySQL object-key-order, 26-page idempotent readback, and scalar mismatch regressions
• isolate each Ops run in a fresh temp directory and always upload a redacted phase summary before fail-closed enforcement
• initialize the authorized repair train item and block evidence CMS refresh on this repair

Why

MySQL normalizes JSON object key order, so strict PHP associative-array equality falsely classified an already refreshed 26-page cohort as stale. Fixed /tmp names also allowed a failed run to reuse stale summaries.

Validation

• php artisan test tests/Feature/Console/PersonalityEnneagramEvidenceRefreshCommandTest.php tests/Feature/Console/PersonalityEnneagramCmsDraftCommandTest.php tests/Feature/Console/PersonalityEnneagramLlmsTxtReleaseGateCommandTest.php — 18 tests, 857 assertions
• vendor/bin/pint --test ... — pass
• actionlint .github/workflows/enneagram-en13-evidence-production-ops.yml — pass
• YAML/JSON parse, exact five-file scope, git diff --check — pass
• bash backend/scripts/ci_verify_mbti.sh — pass after PR test(bigfive): scope personality warmup diff assertion #3019 merged and this branch rebased to latest main

Intentionally deferred

• no deployment
• no CMS or production writes
• no llms eligibility/Search/cache operation
• post-merge deployment and idempotent production readback require separate exact-SHA authorization

Repository rule impact

No authority ownership change. The existing backend-authoritative, fail-closed evidence refresh boundary is preserved and made deterministic.