Tutorial: 2026-07-19

2026-07-19

Newest entry on top.

fairyfox system update → adopted six new mesh standards

Trigger: owner ran fairyfox system update (the check-for-updates flow).

Check. Refreshed the read-only hub mirror assets/references/fairyfox.io/. --ff-only aborted (hub dev force-pushed, as usual) → recovered with fetch + reset --hard origin/dev on the mirror only. Mirror moved 0.14.3 (63fef52) → 0.20.2 (697bc5c) — a 5-version catch-up. Read hub/authorizations.yml: the standing adopt-standards-by-default grant (2026-07-02, no expiry) covers all of hub/standards/ + hub/templates/, so standards adoption here is pre-authorized (skips only the report-then-wait pause; the verification floor still holds).

Finding. Mapped all 27 hub standards against what RAP carries. Most were already held (RAP is the mesh's standards-bearing co-author). Six were new-and-applicable but had no first-class home in the tree, though RAP already practices every one: engineering-quality, planning, research-capture, working-rhythm, self-hosted-assets, agent-tooling. The rest are out of scope for this node (farm-operating-model, coins, new-project-setup, onboarding-existing-project, docs-site). Wrote the check-only process report and committed it (482d68c), then asked the owner for adoption scope → "adopt all, in as many phases as needed to do it well."

Adopt. Added the six as notes/reference/*.md adoption notes — each states the rule set, points to the hub canonical (assets/references/fairyfox.io/hub/standards/<file>), and cross-links to where RAP already satisfies it (working-agreements.md, the Default Workflow, self-hosted fonts, PowerShell/file tools, notes-first). Wiring:

  • CLAUDE.md Default Workflow gained a step 0: plan before you execute (non-trivial work), plus an agent-tooling.md cross-ref on the PowerShell landmine bullet.
  • notes/reference/compliance.md audit matrix gained a row for each of the six (→ its note's ## Verify).
  • notes/README.md reference index + folder map list the six (and the previously-unlisted maintenance-sweep / repo-hygiene) under the fairyfox-mesh-standards group.

Notes-only → no VERSION bump (stays 2.60.1). Verification floor green: check:docs (461 links resolve), prettier --check on all touched files, npm run smoke. Second process report written: notes/fairyfox-reports/2026-07-19-adopting-updates.md.

Friction (folded into the reports): the diff anchor is fuzzy across a 6-version jump — RAP already held content newer than its last recorded check anchor (it authored several standards), and the shallow mirror can't git diff the 0.12→0.20 window, so "what's genuinely new" needed judgment, not a mechanical diff. Standards carry no per-file version stamp.

Follow-up: coins was required — added it to the docs-site chrome

Owner correction: I had filed coins as out-of-scope for this node — wrong. Coins ships as part of the shared docs-site chrome (a counter beside the reader "Aa" button), and RAP's docs site is served same-origin under fairyfox.io/<key>/, so it shares the hub wallet. RAP had adopted the chrome/reader at hub 0.14.3 (2026-07-05) but coins was never included. Chrome bundle is now 2.2.1.

Verified the rest of the chrome first: RAP's reader.js matches the master on every constant (SIZES/LH/WIDTH/ACCENT_VARS/DEFAULTS/fairyfox:reader:b), and the header/subnav/footer match docs-site standard 05. Coins was the sole gap.

Integrated it (RAP's chrome already uses the exact classes coins.js expects — .site-header .wrap, .ff-reader-btn, #ff-reader-panel — so it drops in unmodified):

  • assets/docs-theme/modules/coins.js — the master coins.js vendored verbatim (byte-identical, 19,196 bytes; the earning engine must not be reimplemented per the standard).
  • assets/docs-theme/fairyfox-docs.js — injects it as a plain <script> after initReader(), so the coin button lands left of "Aa".
  • assets/docs-theme/theme/coins.css — button/panel/"+1"-pop/read-time/hidden-coin styles on RAP's own tokens (all present in tokens.css); @imported after reader.css in fairyfox-docs.css.
  • notes/reference/coins.md + a compliance-matrix row + README index entry.

build-docs.mjs copies modules/ and theme/ wholesale, so both files auto-install into docs/jsdoc/ — no build change. Same-origin with the hub means no project legal-page change (the hub /legal/coins/ covers fairyfox:coins:a); the web app doesn't carry coins. Verified: npm run docs builds, coin button renders beside "Aa" and pops "+1" on a new page. Lint/format/check:docs green.