Skip to content

chore: back-merge the history hotfix into develop - #22

Open
tkgstrator wants to merge 3 commits into
developfrom
chore/backmerge-hotfix
Open

chore: back-merge the history hotfix into develop#22
tkgstrator wants to merge 3 commits into
developfrom
chore/backmerge-hotfix

Conversation

@tkgstrator

Copy link
Copy Markdown
Contributor

Brings #21 back so the next release does not undo it.

The hotfix branched off master because develop was holding unreviewed work at the time.
Without this, develop → master would ship a tree where the fix has been reverted.

Fast-forward: master already contained everything on develop (the v0.4.0 release merge),
so this is the hotfix commit and the release merge, nothing else.

Test plan

  • bun run typecheck — clean
  • bun run test — 725 pass / 0 fail

tkgstrator and others added 3 commits September 3, 2026 06:52
The board stops asserting a death estimate the player has not earned, places
become a third kind of subject beside people and the body, and the interrogation
takes topics rather than literal questions. Plus a month of previously unpushed
work and every screen matched against its mock.
Opening a case with investigable places threw "the response is not the shape we
expected" before the player could ask anything. The interrogation screen reads
the history the moment it mounts, and the history's characterId only allowed a
uuid or the literal victim — places carry an author-written local id, so every
case holding one failed to parse and took the screen down with it.

That is 17 of the 43 cases now in production.

The comment above that union already warned about exactly this, having been
written when the body was added as a second kind of subject. Adding a third did
not reach it.

Found on 十七回忌の客: two sessions, no messages, no model calls — it never got
past the first read.

Co-Authored-By: Claude <noreply@anthropic.com>
The interrogation screen reads the history as it mounts, and the characterId
union allowed only a uuid or the literal victim. Places carry an author-written
local id, so all 17 cases holding one failed to parse and took the screen down
before the player could ask anything.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant