fix: demote artifacts-are-projections pending author editorial pass

[klappy]

The essay shipped without the publish gauntlet. Post-hoc run: preflight done, ai-voice-cliches audit found clustering (13 em dashes / 3 clustered paragraphs, 1 negation parallelism, repeated closer). The constraint requires an author editing pass when patterns cluster — demoting to draft until that pass happens. Revised candidate text delivered to maintainer alongside.

---

Note

Low Risk
Metadata-only visibility change on a single essay; no runtime or security impact.

Overview
Demotes the essay artifacts-are-projections from public to draft by updating frontmatter only (exposure: draft, public: false).

Adds a stability: draft note that an author editorial pass is still required after a post-hoc ai-voice-cliches gauntlet (clustered em dashes, negation parallelism, repeated closer). Essay body is unchanged in this PR.

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

[github-actions]

Canon Quality — oddkit_audit ✅

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

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

[github-actions]

Canon Quality — Homepage Surfacing ℹ️

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

6 essay(s) are NOT on the homepage feed (confirm this is intentional):

Essay	Surface
writings/artifacts-are-projections.md	hidden — public=False — NOT a published essay; will not surface publicly
writings/outcomes-not-hours.md	nav — navigation only — reachable but NOT promoted on the homepage
writings/self-ese-and-the-stacking-test.md	nav — navigation only — reachable but NOT promoted on the homepage
writings/the-cost-of-code-dropped-to-zero.md	nav — navigation only — reachable but NOT promoted on the homepage
writings/when-skills-arent-enough.md	nav — navigation only — reachable but NOT promoted on the homepage
writings/your-context-window-needs-a-sabbath.md	nav — navigation only — reachable but NOT promoted on the homepage

To promote to the homepage: set public: true and exposure: public.

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

[github-actions]

Canon Quality — Frontmatter Schema ✅

All 45 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: #236}

[github-actions]

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 660 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': 47, 'canon': 219, 'apocrypha': 38, 'docs': 293, 'journals': 57, 'unknown': 6}
Kind source: {'path': 540, 'frontmatter': 114, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 559 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: #236}