Skip to content
Pokered Save Editor 2
Pokemon Red & Blue save file editor - Qt 6 C++/QML
Loading...
Searching...
No Matches
2026-06-25 — Session Log

Onboarded the project into the fairyfox.io hub mesh (project side)

Followed the hub's onboarding-existing-project runbook to fold this established repo into the fairyfox.io standards mesh — reconcile, not clobber. Surveyed first: the repo already satisfies most of the end state (branch model dev→main FF-only, real SemVer VERSION 0.14.2-alpha, a mature notes/ system, README + Doxygen/Pages docs), so onboarding here was layering the few missing mesh pieces around the existing work, not creating from blank.

Done this session (all project-side, file edits only — see below for what was handed off):

  • CLAUDE.md — added the required mesh-awareness block ("Cross-project standards & checking the fairyfox system for updates"). This is the piece the runbook flags as easiest to miss on a mature repo that already has its own polished CLAUDE.md — without it the project never learns it's a node. Also added a cross-project-sync.md row to the notes table.
  • .gitignore — ignore /assets/references/ so the read-only hub clone (and the existing pret/pokered
    • v1-editor reference clones already living there) stay untracked.
  • Adopted the cross-project-sync standard as this project's committed copy at notes/reference/cross-project-sync.md (the mesh block points to it); registered its \subpage in notes/_nav.dox under Reference.

Handed off (couldn't be done reliably from the Cowork bash sandbox — it can't write .git files over the mount; that's also why a stuck .git/index.lock made git status report spurious Ms):

  • Pull the read-only hub clone into assets/references/fairyfox.io/ (a broken partial dir was left there; remove and re-clone from PowerShell).
  • Commit the above on dev + FF main per the normal workflow (no VERSION bump — docs/infra only).
  • Hub-side registration (a commit in the junebug12851.github.io repo): add to hub/registry.yml and _data/projects.yml with branch: dev and honest adopts_hub / notes_system flags.
  • Themed docs site at fairyfox.io/pokered-save-editor-2/ — currently the Doxygen/Pages site is at junebug12851.github.io/pokered-save-editor-2/ on the default doxygen-awesome theme. Re-skinning toward the fairyfox docs-site design system + the way-home link is a separate, larger effort (and a design decision). This is the main remaining gap; the project is partially onboarded until it's done.

Follow-up verification pass (later 2026-06-25, no-bash session)

Re-audited the above with the file tools only (bash forbidden this session). Findings — the project-side file work from the earlier attempt is all present and correct, not broken:

  • CLAUDE.md mesh-awareness block ✓, .gitignore /assets/references/ ✓, notes/reference/cross-project-sync.md ✓, its \subpage in notes/_nav.dox (Reference hub) ✓.
  • The assets/references/fairyfox.io/ clone is in fact a complete, valid shallow clone on dev — full _docs/, _posts/, _data/, a real refs/heads/dev. The earlier "broken partial dir" call was a stale-mount misread by the Cowork bash sandbox, not an actual breakage. No re-clone needed.
  • The real leftover from the borked attempt is three stale git lock files in the project's .git/ that block all git ops (and caused the spurious Ms the earlier session saw): .git/index.lock, .git/objects/maintenance.lock, .git/trash_config.lock. They must be deleted from a real shell (PowerShell) — couldn't be removed this session (no bash; the file tools can't delete).

Still-open handoff (all require a shell — unchanged): delete the 3 stale .git locks → commit the project-side edits on dev + FF main (no VERSION bump; docs/infra only) → hub-side machine registry (hub/registry.yml; the site _data/projects.yml already lists the project) → themed docs site.

Themed the docs site to the fairyfox.io design system (the last mandatory gap)

Closed the one hard blocker to fully joining the mesh: the Pages docs site was on the stock doxygen-awesome theme. This docs site is the Doxygen output (the generator is the whole site), so per the hub docs-site standard (Case B) the fix is to theme the generator itself, not bolt a shell on top.

Added docs/fairyfox/:

  • fairyfox-doxygen.css — a theme layer (loads after doxygen-awesome) that re-points doxygen-awesome's CSS variables at the exact hub tokens from 02-design-tokens.md / 11-measurements-reference.md: dark-first, OS-following light via prefers-color-scheme; Fraunces/Inter/JetBrains type; the one per-project change is the accent = the registry pink #e6488f (every neutral stays on the shared palette). Plus treeview/menu/blockquote/code/focus/reduced-motion rules.
  • header.html / footer.html — the customised Doxygen templates: load the shared fonts, set the theme-color metas, and inject the project brand + a persistent "← Back to Fairy Fox" way-home (required on every page) and a footer linking the hub / project page / repo / notes.
  • pse-logo.png — brand glyph (the app 64px icon), copied into the output via HTML_EXTRA_FILES.

Wired in the Doxyfile (HTML_HEADER/HTML_FOOTER/HTML_EXTRA_STYLESHEET/HTML_EXTRA_FILES, HTML_COLORSTYLE = AUTO_DARK). pages.yml needs no change — it pipes the Doxyfile, so the theme flows through on the next main deploy. The hub standard + compliance checklist live read-only at assets/references/fairyfox.io/hub/standards/docs-site/.

Verified with a local doxygen build (1.17.0, graphs off) + a dark-mode browser screenshot: the Fairy Fox bar, pink brand, way-home pill, Fraunces headings, themed sidebar/blockquote and warm dark palette all render cohesively and seamlessly with the hub. Spot-check still recommended: light mode and a mobile width (both implemented via the same token system + doxygen-awesome's responsive rules, but not yet eyeballed), and the /screenshots/ gallery page is still the minimal unstyled page from pages.yml (a small, optional polish). With this, the project-side onboarding is complete pending the hub-side registry commit (Twilight) and the next main deploy.