✠ The Chronicle

✠ ENTRY LXI


The reset reaches its checkpoint, Act One tagged and released

Six days, not one: a GitHub outage silently cancelled two scheduled digests, so tonight catches up all of it. The headline buries the rest — the designer walked all four regions in person, then tagged and released v0.1.0-checkpoint, the point the game returns to if work ever needs to pause before new content starts. Getting there took a relic shelf trimmed to one survivor, a real level curve, a save fix so a reload mid-fight can't skip it, every tutorial window removed, and a full pass making the game's own documentation describe only what's actually in the tree. A laggy preview build led straight to a 200-megabyte image hiding under the map. Since the tag, four small reading bugs found by this week's critique and audit passes are already fixed.

MECHANICS

Act One reaches its checkpoint — v0.1.0-checkpoint tagged and released

What changed

The designer personally walked a new game through all four Act 1 regions — the Breakwater, the Charcoal Wood, the Beacon Crags, and the Lantern Deep — checking every region's door fight, its normal monster, its rarer elite, a mercy choice, its blacksmith, its healing potions, and the two now-sealed endpoints (an old vault door and a deep stairway). The walk proves the four regions work, not that the three starting cards can win every fight — where they couldn't, the walk used a developer menu to settle the fight and kept going. Afterward, every tutorial coach and hint screen in the game was removed outright (they'd been superseded by the simpler starting kit), and the build was tagged and released as v0.1.0-checkpoint, with an Android preview build attached.

Why it changed

The designer's own framing for this release: "get everything to a good checkpoint with the mechanics in place, the map working, and everything cleaned up. Then we'll cut a release before we start work on content, cards, people, story, ... This way, if I want to pump the brakes, we can reset to this release version." Everything else this window — the relic trim, the level curve, the save fix, the documentation pass — was groundwork clearing the way to this point.

commits 457d9608 · e · a · 859cef19 · a · ea · 5eb07c48 · e · a · ad · eeae

CONTENT

The relic shelf drops to one survivor

What changed

The ten placeholder relics that stood in since the reset began — each granting the same flat shield — are gone outright, along with the shield mechanic itself. The Suppliant's Ring is now the only relic in the game, and it's the one the player's mercy action runs through.

Why it changed

The placeholders existed only to keep old save slots and tests working while the engine purge finished; once the purge landed, there was nothing left to make them simpler for, so this window deletes the stand-ins rather than keep ten relics to rebuild from scratch later.

commits 37e77313 · ae · 7e2

INFRA

A laggy preview build traced to a 200-megabyte image under the map

What changed

The designer reported the v0.1.0-checkpoint preview build running laggy on every screen. The cause: the map drew every road and glow on a region in a single image the size of the whole map, and the phone's graphics layer turned that into one solid picture — as large as 200 megabytes on a dense display — that stayed loaded for the entire time the map was open, even behind other screens. Roads now draw as small separate pieces instead of one giant sheet, cutting that picture down to roughly 12–17 megabytes per region.

Why it changed

The fix is checked by calculation and by the browser version of the game, but nobody has actually played the fixed build on an Android phone yet — that's the one thing standing between this fix and being trusted, and it's called out explicitly as unfinished below.

commit 6e8b4042

MECHANICS

A real level curve, and a reload mid-fight can't skip it

What changed

Character levels across Act 1 now climb along a tuned curve built for the three surviving monsters and four regions, replacing placeholder numbers. Separately: closing the app in the middle of a fight and reloading used to silently skip that fight entirely — it now puts the player back in front of it, offered again from the start.

Why it changed

Both were on the short list the checkpoint release couldn't ship without: a level curve tuned for the game that actually exists, and a save system that can't let a player lose or skip a fight by force-closing at the wrong moment.

commits 61d16fcf · e · ee · 1bad8fce · ae · cec · in · f

UI

Grey cards get real art, a real name, and a cleared "learn a card" screen

What changed

The three starting cards show actual paintings now instead of a blank placeholder. The app's own name, as it appears on a phone's home screen, is "Miserere Mei, Deus." Levelling up no longer offers a card to learn — with only three cards in the whole game, that screen had nothing left to offer, so it now gives stat points only.

Why it changed

Each is pre-tag cleanup: dead screens and placeholder art that would have sat, confusingly, inside the "this is the checkpoint" release otherwise.

commits 049174f2 · ae · 8

INFRA

The game's own documentation rewritten to describe only what's real

What changed

Five more ticks rewrote the design doctrine, deleted the old pre-reset archive folder outright, and rewrote comments across both the game engine and the mobile app so they describe the code as it stands today — not the mechanics the reset already removed.

Why it changed

Any doctrine or comment still describing a deleted mechanic is a trap for the next person (or the next AI session) reading it — it can look like instructions to bring the mechanic back. This pass runs right before the checkpoint specifically so nothing stale survives into the release.

commits 2a79e596 · 29f3b174 · 6f9a74aa · 22f4e41f · 6bbca8a6

UI

Four small reading bugs, found and fixed this week

What changed

Since the checkpoint tag, this week's automated playtests and audit sweeps caught and fixed four small places where the game's UI said something different from what it actually does: the map's legend — the only key to what the node colours mean — was unreadable bone-on-terrain text at 9 pixels, and now sits on its own small plate; a phone-width combat screen's turn tracker was stacking into a tall column instead of staying a single row; a card's percent effect was printing a bare number with the % missing; and the map's "no path chosen" message claimed paths close behind you, when they actually stay open.

Why it changed

None of these are judgment calls — each is a place the interface was flatly wrong about what the game does, the kind of gap this week's critique and audit passes exist to catch.

commits ddb93536 · a · eed · 67fc1541 · cba · ae · ede · ef0e7a8b · FEE · ece · c · ae281b4d · a · dae · c

INFRA

The run history now reads events in the right order

What changed

The in-game Chronicle — the one screen that looks back at what happened recently in a run — was showing its twelve oldest buffered events first instead of its twelve newest, so a check for "did the player just change regions" was comparing against stale information.

Why it changed

Filed as a bug the day after the checkpoint walk and fixed this window, so the one place a player can review a run's recent history actually shows the recent history.

commit 09161ae7

✠ The marginalia


The night's watch — what ran while nobody looked
window (UTC)what ranoutcome
10-01 10:43 – 10-02 21:4312 build-plan phases (R7e2, B4, R8, R9, R9a, R10, R10b, R10b2, R10c, R10c2, R10c3, R10d) plus the RC walk and tagall shipped clean; v0.1.0-checkpoint tagged and released
10-01 – 10-02critique passes 64–674 passes, 2 findings (0 high, 0 medium, 2 low)
10-02 20:34expand pass 232 candidates filed
10-03 00:36perf audit + fix, off the back of a laggy preview buildroot cause found and fixed same night; device proof still owed (see Needs you)
10-03 08:55 – 10-06 16:36the night and march workflowsevery run failed at checkout with the same git-auth error ("could not read Username... terminal prompts disabled"); 2 scheduled digests (10-03, 10-05) never ran, and roughly 15 march ticks over ~30 hours shipped nothing. The failure cleared on its own by 10-06 18:20 with no code change on either side — nothing in this repository caused or fixed it
10-06 18:24 – 10-07 08:47critique pass 68–69, expand pass 24, 4 audit drains2 critique passes (2 findings, 0 high/medium, 2 low), 1 expand pass (2 candidates), 4 audit findings fixed (memoir order, docs wording, map copy, FREE chip, combat ledger, map legend)
10-07nightly browser breadth leg (hazard, combat encounter, encounter-routing, exploration/combat roundtrip, 10 full combat rounds across sandbox and live modes)all pass, no crashes
10-07deploy state checkclean — no gated workflow verdict yet for the latest commit (normal grace window)
10-07public-site publish decisionpublished — a major release (the Act 1 checkpoint tag) landed in this window
What is still unfinished
  • Act 1 — all four regions, with a Doorwarden guarding each region's exit,

a common Float-Eye and a rarer Brine Hag to fight, one blacksmith per region, and the Suppliant's Ring as the only relic — is now the tagged, released checkpoint (v0.1.0-checkpoint). This is the version the game returns to if new work needs to pause.

  • The old relic shelf (ten placeholder shields) is gone for good; the

Suppliant's Ring is the only relic until a later guided session grows it back.

  • Levelling up no longer offers a card to learn — only stat points. Every

tutorial coach and hint screen is gone from the game entirely.

  • A map performance fix shipped (roads draw in small pieces instead of one

giant image), but it's only been checked by math and the browser build, not on an actual phone yet.

  • Four small UI reading bugs are fixed since the checkpoint: the map

legend is readable again, a phone-width combat screen's turn tracker reads as one row, a card's percent chip shows its unit, and the map's "no path chosen" message says paths stay open (they do).

  • The run history (Chronicle) now reads its own events in the right order,

though it still forgets everything on a page reload — that's a known, separately-tracked gap, not new.

  • Still no numeric balance measurement — that returns with a later reset

step once the remaining work lands.

The measure — did the fighting change?

No numeric balance signal exists to re-run (the deck-matrix tool stays retired until the measurement step returns). The one mistuned thing this window's pulse surfaces isn't a gate or cadence inside this game's rules — it's the ~30-hour GitHub authentication outage that silently cost two digests and about fifteen march ticks (10-03 through 10-06, see While you were out). That's infrastructure outside this repository's control and outside this skill's proposal rails (it governs gates, cadences and ceilings the loop itself sets, not third-party auth), so no plan/PHASE_CANDIDATES.md row is filed for it — it's surfaced here, and in Needs you, so it's visible if it recurs. No other tuning candidate filed tonight.

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.