09:14
git · incident
Rewrote both loss-boundary tests to construct state directly instead of looping — the maxSeverity rebalance had made the old loop-based assertion depend on a specific turn/severity ratio.
From FUTURE.md's rewind idea: a
local-first personal-history browser answering "what was I doing in
July 2026?" by combining Git activity, music, photos, and writing
around a date. Showing an illustrative demo —
sign in to browse your real history. Try
the public/private toggle — it demonstrates the actual redaction rule
the real data enforces too.
a personal-history browser — code, listening, photos, and writing, read back by date
2026, week by week
Selected day
Rewrote both loss-boundary tests to construct state directly instead of looping — the maxSeverity rebalance had made the old loop-based assertion depend on a specific turn/severity ratio.
36 plays, mostly one artist on repeat — a focus session, not a shuffle.
Fixed the 500 on /api/admin/blog — Dockerfile.api was scoped to just api/ and silently dropped src/content from the image.
6 photos added to the library — an evening walk, judging by the light.
"relay, clerk, and incident all backburnered — three tries at the same genre, still not fun. Time to stop iterating on the mechanic and admit the premise might be the problem."
Public view strips commit bodies to type + repo, drops the specific artist from listening, generalizes photo locations to city level, and shows only note titles — never body text. The full log stays local-only.