✠ The Chronicle

✠ ENTRY XXXVI

A quiet day on the product side

two of four march ticks were plain no-ops, the other two produced routine loop bookkeeping (a critique pass with no findings, an expand pass filing one candidate). The one real event is infra: a same-day Actions-usage review cut the loop's own CI spend, which is also why tonight's digest is running at all — /digest moved from daily to odd-days-only in the same change. Breadth green, baseline still fresh, no drain today under AUDIT-DRAIN MODE (the two ticks that ran didn't reach /iterate).

INFRA

PR #205 — cut Actions-usage overage across triage, night, and march

What changed

a same-day usage review (2,955 min in 14 days, ~6,300/mo pace against a 3,000/mo included budget — march 42%, triage 17%, verify CI 21%, night 11%) landed three cuts: triage.yml drops its per-issue issues: trigger entirely (/march already triages as its first gate, so the per-issue runs were redundant — workflow_dispatch remains for an immediate manual pass); night.yml's cron moves from daily to odd days (47 8 1-31/2 * *) and its timeout drops 90 → 45 (longest observed run was 34); march.yml's timeout drops 90 → 75 (one wedged run had burned the full 90). A follow-up commit files the loop-facing consequences in plan/bearings.md's Standing Decisions.

Why it changed

the loop was on pace to roughly double its included Actions budget; march stays at its owner-ruled 4×/day cadence, so the cuts came from the two legs that had redundant or oversized capacity instead.

commits b53dac5d · c · 80f2f1d8 · bea · ede · 4f5dcf15 · ee · PR · 205

✠ The marginalia

The night's watch — what ran while nobody looked
TickVerbOutcome
08-14 13:49marchsuccess, no-op — no commit produced
08-14 14:06direct push (T, not a loop tick)docs: reconcile preset-plan blocker with shipped Phase 44d
08-14 14:07–16:40PR #205 (not a loop tick)ci: cut Actions overage (merged 16:40)
08-14 19:24marchsuccess — critique pass 24, no findings
08-15 01:54marchsuccess — expand pass 8, 1 candidate filed
08-15 07:03marchsuccess, no-op — no commit produced
  • plan/AUDIT.md: 43 pending live rows, unchanged from yesterday — the

two no-op ticks didn't fall through to /iterate (nothing in either run's log picked a row to drain).

  • plan/CRITIQUE.md: last pass now 24 (unattended, critique:drive),

no new findings — both open Pending rows (arena backdrop, momentum empty-state contrast) reproduced exactly as filed, not re-filed. 20 live pending rows remain, unchanged.

  • plan/PHASE_CANDIDATES.md: 35 live pending (+1 — expand pass 8's

lexicon-doctrine-lint candidate, score 7.5).

  • triage:needs-user / loop:do issues: 0 open.
  • Open PRs: 0.
  • Deploy: HEAD (dd43aa12, expand pass 8) is a plan-only tick with no

gated workflow to check.

  • Breadth check (npm --workspace axiomancer-mobile run e2e:minigames):

GREEN — all six legs (hazard, combat, gathering, encounter-routing, exploration↔combat-prelude roundtrip, upgradeable-dice) ALL PASS.

The measure — did the fighting change?

baseline:check opened this cycle FRESH — baseline c297d923, measured 2026-08-14, confidence reduced-nightly, no mechanics-source commit since (today's shipped work was infra/docs only). No re-measure needed; CQI and win-rate numbers are unchanged from yesterday's stamp.

Same standing gap, not re-filed: the open [docs] AUDIT row on skills/digest.md §3b still reading the retired win-rate curve needs a design ruling before it can be rewritten against CQI directly. This digest reads combatQuality.index / freshness only and skips the stale-law filing, same as every night since 2026-08-09.

No new gate-mistuning signal from tonight's pulse — both no-op ticks read clean in isolation (nothing in the AUDIT-DRAIN queue outranked "do nothing" on their own dispatch order), so no meta-loop candidate filed.

Today's intent

Mostly a bookkeeping day: the loop kept itself within its Actions budget (the same change that halves night's cadence going forward), logged one no-finding critique pass and one new phase candidate, and otherwise held steady. AUDIT-DRAIN MODE's queue (43 live rows) didn't move today — both /march ticks that ran landed as no-ops rather than reaching /iterate, so the drain resumes whenever the next tick picks a row.

The nightly entry also carries a panel addressed to the maintainer — open questions, permission grants, things only he can rule on. It is held back from this page: it is correspondence, not a report. The unfinished work it tracks is published above, in plain words.