✠ The Chronicle

✠ ENTRY LXII


Desktop screens stop stretching edge to edge

No new system tonight — this is a catch-up window, closing out a long list of small places where the game said one thing on screen while doing another. The worst repeat offender, a wide desktop window stretching a screen's content edge to edge with huge gaps on either side, got caught by three critique passes in a row on three different screens before anyone noticed it was the same bug each time; all three are fixed now, and the pattern itself is flagged so the next screen doesn't cost another pass. The map now calls its own exit door and forge what their own screens call them. A fight preview shows later phases actually hitting harder instead of repeating one header five times, and stops marking an incoming hit with the "+" sign the game otherwise uses for gains. Combat's own vocabulary agrees with itself everywhere it prints — the good die face, the VULNERABLE effect, the fight summary. A screen-reader fix removes a button that was hiding inside another button. And a test suite that broke on the 7th got caught and fixed the same day.

UI

Desktop screens stop stretching edge to edge

What changed

Three screens — the main menu, the fight preview, and the rest and settlement screens — had their rows and buttons capped to one centred column on a wide window instead of running the full width with huge gaps near the edges.

Why it changed

Three critique passes in a row (69, 70, 71) each caught the exact same bug on a different screen: on desktop, a screen's content stretched the full window width, putting a price or a label hundreds of pixels from what it described. Catching it screen by screen cost three nights and six commits; the dispatcher has now flagged the duplication itself as a candidate for one shared fix instead (see Tuning proposals).

commits 9c435716 · a · e · 31c785d8 · cba · ee · 9bd8b26c · e · & · ae

UI

The settlement screen keeps its header and exit bar inside its own frame

What changed

The settlement screen's heading and its exit bar used to sit on top of the decorative vignette border around the screen rather than inside it. They now pad in by the same width the border itself uses.

Why it changed

the border exists to frame the screen's art; a heading or a button sitting on top of it instead of inside it reads as unfinished.

commit 3284b582

UI

The map names the exit door and the forge what their own screens call them

What changed

A region's exit door used to show "QUEST" with a scroll icon in the map's node panel; it now reads "PATH ONWARD." The Breakwater's blacksmith node used to show "BLACKSMITH" in that same panel while the screen it opens is titled "THE ANVIL" — the panel now says "THE ANVIL" too.

Why it changed

the walkthrough that checked the game right before its first tagged release (the "RC walk") flagged both: a player reads one name on the map, then opens a screen with a different name, with no way to know they're the same place.

commit 444f5a38

UI

The fight preview shows a battle actually getting worse, and reads a hit as a hit

What changed

Previewing an upcoming fight used to collapse every phase after the first into an identical row reading "PHASE 2 · ATTACKS" through "PHASE 5 · ATTACKS," hiding that later phases hit harder. Each row now names its own damage. Separately, opening a phase used to repeat that number as "(+11 damage)" — the same sign the game uses for gains (a +24 buff, +43 healing) — making an incoming hit look like something good happening to the player. It now reads "11 damage," unsigned.

Why it changed

both fixes come from two critique passes in a row (69, then 70) reading the same screen: a preview that can't show a fight escalating, or that marks a hit with a "+", fails at the one job a preview has — telling the player what's about to happen to them.

commits c60e4f00 · ae · eade · e · ae · c · a · fed · a · e · import · a · in · 94d3f412 · f087b6dc · e · daae · sign)

UI

Combat's own vocabulary and numbers agree with each other, wherever they print

What changed

Four places where the game used two different words or two different numbers for the same thing, all closed this window: the good die face is called "BOON" everywhere now (the combat primer used to call it a "SPECIAL face"); A Plain Word's VULNERABLE effect now prints the same percentage on the hand, the card detail, the spoils preview and the deck list (the detail screen was the last holdout, still printing a raw multiplier like "×25"); the spoils preview under a card offer now shows the same numbers the hand itself will deal, scaled to the player's current stats; and the end-of-fight summary spells out "12 plays" instead of an unexplained "12ph," only prints a DoT damage total when DoT actually dealt damage, and lists every card that was played.

Why it changed

a player who sees the same mechanic described two different ways in two different places has to guess which one is real. These four are the last of a batch the pre-release "RC walk" flagged for exactly that reason.

commits b082c21b · B · 19459d23 · EABE · ece · e6fc213c · (spoils · be · 4e4a2e26 · f · a

UI

No control sits inside another control anymore

What changed

Two places in combat had one tappable control nested inside another — the die face inside the staged card, and an item's USE/DISCARD buttons inside the item card's own expand button. Both are now separate, sibling controls.

Why it changed

a nested button is invalid for both the browser and a screen reader: a tap can fire both controls at once, and assistive tech has no correct way to describe "a button inside a button." This was one of the pre-release walkthrough's findings; two smaller console warnings it also named (an outdated element.ref access, a CSS transform passed to a web element) are still open.

commit 46f7f3b8

CONTENT

A hazard speaks to "you," not "him"

What changed

The Creeping Rot hazard's mid-encounter line used to narrate the player in the third person ("his arm"). It now reads "the cut on your arm," matching how every other line in the hazard speaks.

Why it changed

this was the one gendered line left standing after an earlier pass fixed every hazard's opening line; the test that guards hazard voice now checks every string a hazard carries, not just its intro, so the gap can't reopen unnoticed.

commit 81ab72b6

UI

A hazard screen's header and hand get room to breathe

What changed

On a phone, the hazard route-select screen's top strip used to read "◆ HAZARDNO RETREAT — CHOOSE TO PROCEED◆" with no gaps between its three parts; it now holds a visible gap and shrinks its middle segment to one line instead of overflowing. The hand of cards below it used to clip names like "SURE FOOTIN" and "BALANCE POL" when cards overlapped; every card's name now stays readable, however much a neighbor covers it.

Why it changed

two critique passes in a row caught the same screen cramped on a narrow phone — nothing in a fast, choice-under-pressure moment should go unreadable.

commits d63cf279 · (top · strip) · 8d5aee2a · ad · fa · ae

INFRA

A red test suite gets caught and fixed the same day it broke

What changed

the prior digest filed a finding that the project's root test suite had been failing on main since a 2026-10-07 commit — a code comment describing a UI layout ("phase 1 of 5" as a row) accidentally matched the pattern a different guard uses to catch comments narrating old build-plan history. The comment was reworded; the guard's own rule is untouched, so it still catches what it's meant to catch.

Why it changed

this is the kind of gap a per-commit gate can miss (neither package's own test run touches this root-level check), which is exactly why the digest runs its own full-repo sweep — and it closed the same day it was filed.

commit 6a41768c

✠ The marginalia


The night's watch — what ran while nobody looked
window (UTC)what ranoutcome
10-07 10:33 – 13:01audit drain (root npm test fix) + audit drain (threat phase headers) + its own CI follow-upboth fixed; a test's import path was caught and fixed in the same tick, and a redundant fix-ci check confirmed nothing was left to do
10-07 14:34expand pass 252 candidates filed
10-07 16:36 – 22:31audit drains (main menu column, combat preview column) + critique pass 70both fixed; 2 findings (0 high, 0 medium, 2 low)
10-08 01:11 – 08:43audit drains (inn rest copy, threat telegraph sign, hazard top strip, hazard hand fan, map node labels)all 5 fixed
10-08 10:35critique pass 712 findings (0 high, 1 medium, 1 low)
10-08 12:46 – 14:36audit drains (hazard scenario voice, rest & village column)both fixed
10-08 16:38expand pass 261 candidate filed
10-08 18:40 – 22:32audit drains (spoils scaling, BOON vocabulary, VULNERABLE notation)all 3 fixed
10-09 01:13critique pass 721 finding (0 high, 0 medium, 1 low)
10-09 02:49 – 08:43audit drains (settlement vignette frame, fight summary plays/DoT, nested buttons)all 3 fixed
10-09nightly browser breadth leg (exploration/combat roundtrip, 10 full combat rounds across sandbox and live modes)all pass, no crashes
10-09deploy state checkclean — no code diff awaiting a verify verdict
10-09public-site publish decisionpublished — UI legibility and accessibility fixes landed this window
What is still unfinished
  • Desktop screens keep closing the "runs edge to edge" bug one screen at a

time; the main menu, the fight preview, and the rest and settlement screens are fixed now, and the pattern itself is flagged so the next screen doesn't need its own pass.

  • The map, the fight preview, and combat's own numbers say the same thing

wherever they print: the exit door and the forge are named consistently, a fight preview shows later phases hitting harder instead of repeating one header, an incoming hit no longer looks like a bonus, and VULNERABLE, the good die face, and the fight summary all read the same way everywhere they appear.

  • A screen-reader fix removes a button that was hiding inside another

button in combat. Two smaller console warnings from the same walkthrough are still open, along with a dev-only crash that doesn't affect a real build.

  • A hazard's mid-encounter line now speaks to "you" instead of "him"; a

different hazard screen's header and hand of cards get breathing room on a phone.

  • A few small things from the pre-release walkthrough are still waiting:

a reward-preview glyph overlap, a city backdrop drawing over two Charcoal Wood screens, and the level readout saying "LVL 4" in one place and "level iv" in another.

  • No numeric balance measurement exists yet — that returns once a later

reset step restores it.

The measure — did the fighting change?
  • Expand pass 25 filed two candidates: extending the project's

retired-word checker to the app's own on-screen text (today it only reads documentation, which is why labels like "BOON" and "QUEST" could drift out of sync with the rulebook for days before anyone noticed); and zeroing the web build's console-error baseline so a new nested-button or stale-reference bug fails the build automatically instead of only getting logged.

  • Expand pass 26 filed one candidate: collapse the four near-identical

"one centred column" width constants (and their four separate tests) that this window's own fixes shipped into a single shared cap and one test that guards every screen at once, so this bug stops costing one critique pass and one commit per screen.

  • The tick-end ledger gap found tonight (see Needs you) isn't a mistuned

gate or cadence — it's a bug in the hook itself — so it's filed in plan/AUDIT.md, not here.

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.