claim(M1): per-recipe history sourced from local /var/lib/cc-ci-runs artifacts (full history, not Drone 100-build slice)

history_for() now enumerates run dirs' results.json, groups by recipe, sorts
newest-first by finished timestamp (mixed numeric+named ids — timestamp is the
only correct key), caps at HISTORY_CAP=30, skips malformed/empty/no-recipe dirs.
Overview + badges + /runs + security guards + stdlib-only unchanged.
Local verify: 13/13 unit tests; full-fixture vs 308 real results.json →
bluesky-pds=8 in exact ts order, plausible capped 30 newest, edge dirs skipped.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

machine-docs/JOURNAL-dash.md

@@ -0,0 +1,44 @@
+# JOURNAL — phase `dash` (reasoning; Adversary does not read before verdict)
+
+## 2026-06-17 — M1 design + implementation
+
+**Root cause (confirmed against plan §1 + host):** `history_for` read `_custom_recipe_builds()`,
+which fetches a single Drone page `…/builds?per_page=100`. The recent `regall` sweep `!testme`'d all
+21 recipes once, filling the latest-100 window, so each recipe's older runs fell outside it → most
+recipes rendered exactly 1 history row. Host has 432 run dirs (308 parseable `results.json`).
+
+**Why source from local artifacts, not paginate Drone:** the plan's chosen design. Local artifacts
+are complete (308 finished runs vs 100-build Drone window), durable (independent of Drone
+retention/pagination), already bind-mounted read-only, and already read per-run by `_results_for`.
+Pure-local also removes a network dependency + failure mode from the history page. I deliberately did
+NOT merge in Drone "currently running" live status (plan lists it as an optional "e.g." value-add):
+it re-introduces the Drone dependency and the overview already shows live status; the DoD asks only
+that the *historical* list come from local artifacts. Recorded as a decision.
+
+**Status derivation:** `results.json` (schema 2) has no top-level status field. Derived from the
+per-stage `results` map: any `fail`/`error` → failure; all `pass`/`skip` → success; else unknown.
+A skip alone is not a failure (e.g. custom-html-bkp-bad: backup=fail → failure; level-5 plausible:
+all pass → success). This matches what the run actually did without inventing a Drone call.
+
+**The sort trap (flagged by Adversary's pre-claim baseline too):** run ids are MIXED numeric
+(`753`,`556`) and named (`m2r-bluesky-pds`,`ab-bluesky-pds-oldmain`). `int(run_id)` would crash on
+named ids; lexical sort would scatter them and misorder `9…` vs `7…`. The ONLY correct order is by
+`finished` timestamp. Sort key = `(finished, _numeric_id)` reverse — finished is primary, numeric id
+is a stable tiebreak (named ids get -1, so timestamp always decides their slot). Verified the output
+matches the Adversary's independently-derived bluesky-pds order byte-for-byte.
+
+**Cap:** `HISTORY_CAP=30` (env-overridable). Sorted newest-first BEFORE slicing, so the cap keeps the
+30 newest and drops the oldest — verified plausible (33 runs) keeps the newest 30, drops oldest 3.
+
+**Caching:** `_local_history` scans the whole runs dir once per `CACHE_TTL` (reuses the existing 30s
+TTL) and groups by recipe, so a busy page doesn't json-load 300+ files per request. `_results_for`
+(already traversal-guarded) is reused for each dir read, so the path-traversal guarantee is unchanged.
+
+**Retention:** 308 parseable runs present spanning many days — retention is adequate; no trimming of
+`/var/lib/cc-ci-runs` observed that would vanish history. Will confirm no cleanlogs/prune job trims it
+during M2 and record in DECISIONS if a cap is ever needed (none needed now).
+
+**Local verification (M1):** 13/13 unit tests pass (incl. new local-sourcing test). Full-fixture run
+against all 308 real `results.json` + injected malformed/empty/no-recipe dirs: bluesky-pds=8 in exact
+timestamp order, plausible capped 30 (newest kept), 308 total grouped, edge dirs skipped without
+raising, security guards (`_RUN_ID_RE`, `_results_for`, `serve_run_file`) all still reject traversal.