Duels record the rules revision they began under
CURRENT_RULES is stamped on the start line and the game state, and a ledger replays under the revision it recorded (1 when it has none), so a future fix that changes how a past turn resolves can keep the old path for old duels. The reports desk skill now says when to bump it: only when the deploy gate flags ledgers. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0141G6xqLeNRYEtviLWSB5Up
This commit is contained in:
co-authored by
Claude Fable 5.1
parent
8eca078043
commit
7485d50b8d
@@ -24,7 +24,9 @@ the other wizard moves. An empty seat can be given to the bot. Each turn, choose
|
||||
hand, pick which completed spell (if any) each hand casts and at whom, and reveal. The rules
|
||||
are at `/rules`, and a walk through the page with screenshots at `/guide`. A room's link opened
|
||||
without a seat is the Peanut Gallery: a read-only view showing only what every wizard could see.
|
||||
Seated wizards can talk to the table; the talk is a ledger line like any other. The Report
|
||||
Seated wizards can talk to the table; the talk is a ledger line like any other. A duel records the rules revision it began under (`CURRENT_RULES` in `state.ts`), so a fix that
|
||||
changes how a past turn resolves can keep the old path for old ledgers; the deploy gate says
|
||||
when that is needed. The Report
|
||||
button in a room's masthead files a bug report pinned to the room and the turn, kept in
|
||||
`feedback.jsonl` beside the ledgers; `deploy/pull-reports.sh` mirrors them locally and
|
||||
`deploy/report-reply.sh` answers one, and the reply appears under the report in the player's hall.
|
||||
|
||||
Reference in New Issue
Block a user