FIXLOG.md

Produced by brief 47 · The Fixer, run against this repo (goal-prompts). Part of the sample-report gallery — this is the acting half of the catalog dogfooding itself: the reports at this root became the commits below. Newest session first.

Session — every finding, worked through (2026-07-26)

• Branch: claude/product-engagement-stickiness-1cril7
• Focus: the operator's "work through every finding" — all 8 findings from the

same-day POLISH run (shipped earlier on this branch), all 32 findings from the fresh All-Craft run (DEFAULTS, PERCEIVED-SPEED, COMPOUNDING, SIGNATURE), and a full re-verification of the 18 defect-shaped legacy reports (~300 findings triaged against current code by 11 parallel read-only passes; the venture and strategy reports are analysis artifacts and were left out of fixing scope). Triage verdict on the legacy backlog: the overwhelming majority had already shipped in rounds R01–R66 — 26 items were still live, and all are closed below or declined with reasons. Every behavioral fix was verified in a real browser.

Fixed (this round)

Declined by design, with reasons

• COLOR C7 (merge/retire family hues): 24 families now share the hue wheel,

but color stopped being the sole family signal when C8 shipped famchips (icon + name). Recoloring families is an identity decision ADR-12/13 reserve for the operator — flagged, not executed.

• LAYOUT L5 (collapse 11 breakpoints to 3): rewriting @media literals

changes real behavior at in-between widths for near-zero user-visible payoff — fails the round-3 "no perceptible change" bar for value remaps.

• LAYOUT L6 tail (map 14/18/26/34px onto the 4pt grid): those maps ARE

perceptible 2px shifts at dozens of call sites; the on-scale values are tokenized, the off-scale tail is documented instead of silently moved.

• TYPO T3's aggressive half (a 5-step type scale in brand.json): folding

14/15/16 into one step shifts running text — same decline as round 3; the half-pixel defect itself is re-fixed.

Ops-only remainder (no code path)

• Raw-fetch counting (FUNNEL §4.3/§4.4, RETENTION): enable the Vercel

Observability filter on pathname:/raw/ (+ commands archives) and date it in docs/usage-metrics.md — dashboard access only the operator has.

• SIGNATURE §2's gallery transcript: wants the debrief of a real external

run, not a mockup — becomes available the first time one is captured.

Session — open-items backlog, round 3 (2026-07-09)

• Branch: claude/open-items-backlog-rm6wzx
• Focus: build the "irreducible remainder" round 2 left behind — the spacing/type

value remap and the "product seen working" visual — anything buildable without fabricating a credential or a fake media asset. Every change verified in headless Chromium at desktop + mobile, dark + light, with a hard rule: no perceptible visual change from the remaps (they were called "indistinguishable"; if a fold would actually shift what a reader sees, it wasn't done).

Fixed (this round)

Honest about the remap

The audit's aggressive target (collapse ~27 sizes to a 9-step scale, folding 14/15/16→one 15) was declined by design: those full-pixel steps are perceptible and folding them shifts running body text. What shipped removes the defect the audit actually named — the six indistinguishable half-pixel pairs — and puts the off-grid spacing on a real, tokenized scale, with zero perceptible change. That is the correct, non-destructive reading of "map every value onto the scale."

SHOWCASE F1 — built honestly, not faked

F1 asked to see the product working. The ideal asset is a real screen recording, which this environment can't capture — and a staged screenshot/GIF would cut against the site's own "Real reports, not screenshots" stance and reintroduce media staleness. So instead of fabricating one, the Proof section now animates a walk-through built only from real content (the real slash command, the real four phases, the real BUGS.md finding), labeled "walk-through, not a screen capture" in the header and caption. It's the honest proxy; a true recording remains a nice-to-have for a maintainer with capture tooling.

The one true remainder — a credential, not code

• npm publish (IMPROVEMENTS 11). The package is publish-ready and the

Release-triggered workflow ships (.github/publish.example.yml); publishing is an irreversible, outward-facing action that requires an NPM_TOKEN this agent must not fabricate and is not authorized to run. It is one maintainer step (add the secret, cut a release) — deliberately left to a human, not an unbuilt item.

Integration with the parallel product-visuals work

main had meanwhile merged a parallel implementation (#23) of the same backlog’s "remainder" — a real Report Studio screenshot (img/studio.png), a real finding→commit before/after, a mobile hero stat-block, retention R1–R4, and credibility scaffolding (CREDIBILITY.md, maintainer credit, an armed adoption badge). This branch was merged onto it as a de-duplicated union: overlapping features (the retention R2 SW handler, export/import, the welcome-back banner, the before/after) resolve to main’s tested version; this branch’s unique work (the TYPO/LAYOUT value-remap, SHOWCASE F1, container tokens, ACTIVATION A2/A3, CRO F1/F5, HIERARCHY F4) layers on top, and the value-remap was re-run over main’s new code so its half-pixels fold too. The Proof section now shows the loop three honest ways — animated walk-through (F1), real Studio screenshot (F2), real finding→commit (F3). Verified: scripts/check green; exactly one of every component (no duplication); mobile hero shows the injected 135/21/35; no console errors. SHOWCASE F2/F5 and PROOF F5/F2 ledgers flipped to the now-live assets.

Session — open-items backlog, round 2 (2026-07-09)

• Branch: claude/open-items-backlog-rm6wzx, restarted off main (f03bc06, the round-1 squash-merge)
• Focus: after round 1, take the "deferred" findings and build every one that's

buildable and safe — including the design-judgment calls — with a default grounded in each audit's own recommendation, verified in headless Chromium. Left only what genuinely needs a human decision, a real media asset, or npm credentials.

Fixed (this round)

Also built after the first round-2 pass

COLOR C2–C5 (semantic-colour separation); HIERARCHY F3/F4/F5/F6; COMPREHENSION F1; CRO F1/F2/F5/F6/F7; ACTIVATION A2/A3/A4/A5; RETENTION R1–R5 (incl. the opt-in PWA reminder and anonymous cohort analytics); LAYOUT L1/L3 + TYPO T4 (container/ gutter/line-height/nav-breakpoint tokens); SHOWCASE F3 (real inline before/after); package.json 0.9.0→0.11.0 + a Release-triggered npm-publish workflow; and a copy-hint show-on-load regression fix. Each verified in headless Chromium.

The irreducible remainder

• A dedicated, low-value refactor: the full spacing/type value remap (TYPO

T3/T5, LAYOUT L2/L4/L6) — its structural "define once" parts shipped (container/ gutter/line-height/breakpoint tokens); the remaining value-by-value remap is what the audit itself calls the "deepest cleanup," with the half-steps "indistinguishable" (near-zero user benefit) and real regression + citation- restaleness risk. A deliberate pass, not a blind fold-in.

• Needs a real media asset: SHOWCASE F1 — a screen recording of an agent run,

which can't be produced here (and cuts against the site's "real reports, not screenshots" stance). SHOWCASE F2's screenshot was declined for the same reason.

• Needs a credential: IMPROVEMENTS 11's actual npm publish — the automation

now ships (.github/publish.example.yml); it runs once the maintainer adds an NPM_TOKEN secret and cuts a release.

Session — open-items backlog (2026-07-09)

• Branch: claude/open-items-backlog-rm6wzx · off main (b7d0988)
• Reports consumed: the Design family (HIERARCHY, TYPOGRAPHY, COLOR, LAYOUT,

STATES, BRAND) and the experience suite (COMPREHENSION, SHOWCASE, PROOF, RETENTION, ACTIVATION, CRO), plus DX — every finding given a disposition (FIXED / already-done / deferred / blocked) in its own report.

• Protocol: one finding per commit, scripts/check green after each;

visual/interaction fixes verified in headless Chromium.

• Theme: the biggest debt was staleness — the public counts and much of the

design backlog were already out of date, so this pass shipped the genuine remainder and reconciled every ledger.

Fixed

Already resolved by the earlier redesign (reconciled, not re-fixed)

• TYPO T2 — unused plexmono-500 was dropped in the font redesign (400/600 only).
• BRAND B1–B4 — favicon is now the bar mark; --radius is one shared token;

og.py renders in Schibsted/Plex; a --r-sm/--r-md/--r-pill scale exists.

• HIERARCHY F1/F2 — the nav CTA is a ghost and cards promote the title (mobile pass).
• COLOR C1 (dark) — the palette redesign lifted dark faint most of the way; this

pass finished it (light mode + --panel-2).

Deferred (disposition recorded in each report)

• Subjective visual-hierarchy / color-meaning changes (HIERARCHY F3–F7, COLOR

C2–C8) and type/spacing-scale systematization (TYPO T3–T5, LAYOUT L1–L6) — large, citation-shifting, design-judgment work best done as dedicated passes.

• Hero/CTA copy rewrites (COMPREHENSION F1/F3, CRO F1/F2/F6/F7) — wording is the

maintainer's call.

• Product features with local-first tradeoffs (RETENTION R1–R5, ACTIVATION

A1–A5), STATES S4 input-error state, j/k nav (DX) — buildable follow-ups.

• New minor issue found: .drop-big / Studio checkbox request --sans @700 where

Plex Sans ships only 400/600 (a fresh faux-bold).

Blocked (need assets/credentials this environment lacks)

• SHOWCASE F1–F3 — product-in-action GIF, Studio screenshot, finding→commit

before/after: need real screen captures.

• IMPROVEMENTS 11 — npm publish + MCP-registry listing: needs npm credentials

(unchanged from prior sessions).

Follow-ups the fixes revealed

• With counts build-injected and README-guarded, og.png (a hand-made raster) is

the last surface that can still misstate the catalog size — a build-time regeneration (Pillow) would close it.

• A fresh Color and Typography audit against the current dark+light palette

would replace the pre-redesign COLOR/TYPO findings that now measure code that no longer ships.

Session — 0.8 cycle (2026-07-07)

• Branch: claude/product-improvement-discovery-7yhdyg · off 0.7.0 (97ad4fe)
• Reports consumed: IMPROVEMENTS.md (the v0.7 re-run), plus carried-forward BUGS.md and SECURITY.md findings
• Protocol: one finding per commit, scripts/check green after each. Selection = the whole 16-item opportunity map.

Fixed

Skipped / partial

• npm publish itself (IMPROVEMENTS 11, big bet) — the package is now publish-ready but the actual npm publish and MCP-registry listing are blocked on npm credentials this environment doesn't have. Prep shipped; the publish is the one remaining manual step.
• Community brief index (prior IMPROVEMENTS big bet) — still a project, not a one-commit fix; not in this run's scope.

Follow-ups the fixes revealed

• scripts/og.py needs Pillow — a heavier dep than the stdlib-only site build. It's a dev/generate-time tool (the build only checks cards exist), but worth a note in CONTRIBUTING if brief-adding contributors hit it.
• The Studio's GitHub loader and the report grammar (items 7–8) now make a report schema validator tractable — a natural next audit of the report format itself.
• Family colors still live in two places (template.html CSS + scripts/og.py); only order/questions got unified. A future pass could inject colors too.

Session — 0.5 cycle (2026-07-07)

• Date: 2026-07-07 · branch: v0.5-round · off 0.4.0 (d041b3f)
• Reports consumed: IMPROVEMENTS.md, SECURITY.md, DX.md
• Protocol: one finding per commit, the repo's own scripts/check run green after each

Fixed

These eight fixes were selected from the reports; the same cycle also shipped features that were not fix-findings (the Act family and briefs 48–53, the Report Studio, make_conductor, and GOAL_PROMPTS_BASE fork support), committed separately.

Skipped (findings deliberately not taken this cycle)

• Self-host the two fonts — SECURITY finding 4 / IMPROVEMENTS quick win 3 / DX. Effort M and a genuine tradeoff (offline + privacy vs. a build-time font pipeline); left open for its own change.
• j/k keyboard navigation — IMPROVEMENTS quick win 4. Additive, no report depends on it.
• Deep-link scroll-margin under the sticky toolbar — BUGS finding 3 (BUGS was not in this run's consumed set; belongs to a Fixer pass over BUGS.md).
• Three-digit hash router — BUGS finding 4, forward-compat only (ids reach 53; the cap bites at 100).
• npm publish, report-diff viewer, community index, "surprise me" — IMPROVEMENTS big bets / engagement; scoped as projects, not one-commit fixes.

Follow-ups the fixes revealed

• The rarity weighting is deliberately clamped (df floor 5) so a single vivid tagline can't dominate; worth revisiting if the catalog grows past ~100 briefs, where true IDF would behave differently.
• scripts/check now defines the contribution contract end to end — a natural home for a future link-checker over the example and raw URLs.
• With the Studio consuming reports and 47 consuming reports, the report format itself is now load-bearing; a light report schema could make both parsers stricter.

Report only — which of the skipped findings should the next Fixer run take?