fix: the captain's calendar — E0010 dates to 2026-06-09 (EST)

[klappy]

UTC-inferred dates corrected to the captain's civil date. Convention added to boarding-pass (both the project-level paste text and the update discipline). Journal renamed + learning row appended.

---

Note

Low Risk
Documentation, metadata, and paste instructions only—no runtime or auth changes; maintainer should re-paste project instructions after merge.

Overview
Corrects Epoch 10 metadata and narrative dates from 2026-06-10 to 2026-06-09 after UTC server time was mistaken for the captain’s calendar (America/New_York). Touched canon (boarding-pass, flight-deck-model, publish-gauntlet, Orville voice), docs/appendices/epoch-10, and writings/crew-not-clone (frontmatter, provenance lines, and light epilogue wording).

Boarding pass now encodes the rule in paste-ready project instructions: run oddkit_time each turn, treat server_time as UTC, and use the captain’s civil date for document, journal, and signature dates—observe the clock; don’t infer the calendar. The same rule is spelled out in update discipline so future boarding edits stay aligned.

The 2026-06-09 epoch journal batch gains a Learning row documenting the mistake and the new convention.

^{Reviewed by Cursor Bugbot for commit ca50c07. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Canon Quality — Homepage Surfacing ✅

46 essay(s) scanned. Soft report — never blocks; the hard field gate is the Frontmatter Schema job.

All published essays resolve to the homepage feed.

_{Report: scripts/surfacing-report.py · Canon: klappy://canon/constraints/frontmatter-validation-before-merge}

[github-actions]

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 666 files scanned. Never blocks — informational until the corpus is ready to enforce.

• Blocking-class findings: 12 (structural fields the contract would filter on)
• Warnings: 0 (kind resolves to unknown)
• Informational: 13 (exempt templates/archive/drafts)

Kind distribution: {'essays': 48, 'canon': 223, 'apocrypha': 38, 'docs': 294, 'journals': 57, 'unknown': 6}
Kind source: {'path': 541, 'frontmatter': 119, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 565 visible, 101 hidden (journals/apocrypha/unknown)

By rule: {'audience-invalid': 2, 'exposure-missing': 5, 'tier-missing': 5, 'tier-invalid': 7, 'kind-unresolvable': 6}

These are not schema violations (see the Frontmatter Schema job for those on writings/). They are corpus-readiness signals for the retrieval contract: invalid/missing audience, exposure, tier, and docs whose kind cannot be resolved. Fix in a corpus-cleanup PR before the contract flips to enforcing. See the retrieval-readiness-findings artifact for the full list.

_{Validator: scripts/audit-retrieval-readiness.py · Constraint: klappy://canon/constraints/retrieval-disclosure-contract · Run: #244}

[github-actions]

Canon Quality — Frontmatter Schema ✅

All 46 file(s) in writings/ conform to klappy://canon/meta/frontmatter-schema.

_{Validator: scripts/validate-frontmatter.py · Canon: klappy://canon/constraints/frontmatter-validation-before-merge · Run: #244}

[github-actions]

Canon Quality — oddkit_audit ✅

No dead klappy:// references or legacy link patterns found in writings/. 48 files scanned.

_{Spec: klappy://docs/oddkit/specs/oddkit-audit · Workflow: .github/workflows/canon-quality.yml · Run: #244}