Essay: GitHub Doesn't Play Nice with Connectors. So We Fixed That.

[git-repo-auth]

What this is

New public homepage essay (public: true, exposure: public) announcing the Git Repo Auth credential relay as the auth layer of the substrate stack. Captain's pitch as the spine: GitHub + connectors friction fixed; free self-host or $24/2yr ($1/mo) hosted; open so you (or your agents) can audit it.

Gauntlet evidence

• Preflight: run; constraints surfaced (ai-voice-cliches, author-identity-language, dual-context-writing) and fetched at hashes from main @ c503504
• Frontmatter: validate-frontmatter.py ✅ 0 findings
• Cliché audit: 0 em dashes; no negation parallelism, no summary clichés; pacing varied
• Challenge (published-essay mode): block-until-addressed fired; addressed comparative-positioning (fairness + as-of-this-writing recency on the OAuth connector), disconfirmer (the We-Were-the-Wire swap-out offer extended to this layer), reversibility (same)
• Live evidence in-text: today's session — down-scoped mint, 404 scope check, mid-session expiry + remint

Deliberately left unstated (for captain's eyes)

• Hosted custody shape: the essay makes no claims about what the hosted offering holds (your keys vs. installs-our-app). The exploration doc flagged custody as a strategy question; pricing is now declared but architecture claims await verification. Self-host claims are limited to what's verifiable.
• Carried from execution to validation, not blocked on: "doesn't play nice" in the title is punchier than the body's calibrated version; the body does the calibration work.

Review

Authorial voice — nothing merges without the captain's review of the exact text. Committed as oddkit-steward[bot] via relay-minted token (provenance demo included).

[github-actions]

Canon Quality — Frontmatter Schema ✅

All 47 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: #255}

[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: #255}

[github-actions]

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 669 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': 49, 'canon': 223, 'apocrypha': 38, 'docs': 296, 'journals': 57, 'unknown': 6}
Kind source: {'path': 542, 'frontmatter': 121, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 568 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: #255}

[github-actions]

Canon Quality — Homepage Surfacing ✅

47 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}