Fairy Fox

2026-07-20

Newest on top. (v1.3.4/v1.3.5 ship + live verification ran just past midnight UTC on 07-21; logged here with the day's thread.)

Legal pages built + Legal subnav item (v1.3.6) — another wrong N/A caught by the owner

Fairy Fox flagged legal missing. Root finding: legal-docs is mandatory per-repo; the manifest's "N/A — hub serves /legal/" was a wrong lenient read and the chrome footer's legal links had 404'd since the chrome adoption. Built the three self-hosted code-accurate pages (local-storage disclosure with reset controls, coins no-value + shared explainer, GitHub Pages as processor, Google Fonts IP flagged, plugin-side operator-controlled storage stated, Apache-2.0 as-is, legal@fairyfox.io, dated) at legal/{privacy,terms,cookies}/ + index; added a Legal subnav item on every page (owner-directed addition to the canonical set — recorded in decisions). Manifest row corrected; CLAUDE.md notes table gains the legal-update trigger.

v1.3.4 shipped; live-deploy verification found + fixed one more defect (v1.3.5)

Shipped v1.3.4 via the PR path (PR #10, both builds green, hand-tag, back-merge, branch-sync re-run green after the known race). Then verified the served site with cache-busted fetches (first fetch hit a stale CDN copy — cache-bust before judging): overview landing is the default page, full canonical subnav on hand + API pages, API boundaried under /api/ (Dokka bar shows 1.3.4, way-back to overview), Notes landing + sidebar complete, fox icon vendored. The live pass caught one real defect: the notes landing linked section READMEs that weren't rendered → 404s. Fixed (render READMEs, keep them out of the sidebar) and shipped as v1.3.5.

The pattern recurred inside the fix — docs site rebuilt properly (v1.3.4)

Fairy Fox caught that the v1.3.3 subnav "fix" was a lenient reading (subnav shrunk to existing pages; Dokka module page still the default; API not boundaried) — the exact F1/F5 failure the same-day report documents. Rebuilt as docs-site Case A: overview landing = default page, full canonical subnav (Notes · Tutorials · Changelog · API · Download), Notes rendered (44 pages, sidebar lists every note, data-read on articles), Tutorials page, Changelog generated from notes/version at build, Dokka boundaried under /api/ with way-back, fox icon vendored (last hot-link gone). New Gradle pipeline: renderDocsSite (flexmark) + assembleDocsSite → build/docs-site; docs.yml publishes it. Adversarial output verification caught a malformed home-pill attribute pre-commit. Report addendum §6b adds S8 (strict reading of latitude) + S9 (disclose the not-done list) to the hub proposals; both also enforced in this repo's CLAUDE.md. Open + told to the owner, not buried: breadcrumbs (recommended), live-deploy three-theme sign-off after ship, hub-side registry check.

Checklist-noncompliance failure analysis + reference enforcement (for the hub)

At Fairy Fox's direction (this is a frequent mesh-wide problem, not one repo): wrote fairyfox-reports/2026-07-20-checklist-noncompliance-failure-analysis.md — full failure tree (F1 docs rules skipped under "chrome adopted" · F2 copy-counted-as-adoption + false-green status · F3 dormant enforcement · F4 release-path drift + the branch-sync PR-path race from the v1.3.3 ship · F5 this audit's own scoping bias), six root causes, seven proposed hub mandates (S1 adoption manifest · S2 enforcement cadence + release hold · S3 rules-on-the-slots · S4 partials name their remainder + report spot-checks · S5 machine gates + branch-sync grace window · S6 "Checklists are contracts" CLAUDE.md instruction · S7 evidence-linked status). Implemented S1/S6/S7 here as the reference: reference/adoption-manifest.md (28 rows), the CLAUDE.md standing instruction, and status.md's Health row now links the manifest instead of a bare ✅.

v1.3.3 shipped via the protected PR path (first run)

PR #9 → checks green → --merge → hand-tag v1.3.3 → release workflow green (provenance attestation succeeded, jar attached) → back-merge, dev == main. One finding: branch-sync fires on the PR-merge push before the back-merge can exist → guaranteed transient red on every compliant PR release (re-run green). Filed as F4.2/S5.

Full hub-standards audit — every expectation listed, gaps applied (v1.3.3)

Fairy Fox flagged that the docs chrome adoption missed most of the standards' rules (subnav structure, API-page/sidebar rules, which navbar item to highlight) and that the release workflow has moved past plain dev → main merges — and asked for the complete expectation list, none skipped. Compiled 108 items in plans/standards-audit-2026-07-20.md from the hub clone (docs-site 13 modules, git-workflow, supply-chain-hardening, versioning, testing + repo-hygiene detail added on a mid-session flag, plus the 27-standard adoption table).

Applied under the standing adopt-standards-by-default ledger grant:

  • header.ftl: primary nav active Docs → Projects (docs-site 05 — always, only Projects on a sub-project); subnav canonicalized to [name] · API (active) · Download · [Repository ↗] (invented "Guide" + raw-GitHub centre links removed).
  • downloads.html: real chrome-wearing Downloads page (required — we ship jars); perma-latest on releases/latest; vendored into docs root via vendorChromeAssets.
  • Release hardening: main branch-protected (solo config), dev deletion/force-push protected, auto-delete on → releases now via PR; release.yml gains build-provenance attestation (job-scope id-token/attestations).
  • Hygiene gates: check-links.mjs in CI, check-tidy.mjs for session end.
  • 17 standards copied into notes/reference/ (4 N/A recorded with reasons).
  • Bookkeeping: changelog v1.3.3 + VERSION, decisions entry (supersedes the same-day "Docs active" choice), status.md release-path note, CLAUDE.md step 4 updated to the PR path, future.md follow-ups (themed Changelog/Tutorials pages, vendored fox icon).

Verified: ./gradlew build dokkaGenerate green (suite gates build); regenerated output checked — downloads.html + 4 chrome assets present, Projects/API carry the only aria-current, exactly one footer (no Dokka footer), Dokka sidebar has zero chrome/hand-page leakage. Process report: fairyfox-reports/2026-07-20-standards-audit.md.

Docs site wears the shared fairyfox chrome (v1.3.2) — earlier today

See fairyfox-reports/2026-07-20-adopt-docs-chrome.md; two of its choices ("Docs" active, Guide/raw-GitHub subnav) were corrected by the audit above.