docs(app): the ready message's game flag and the M7 performance stages in the roadmap

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
javis-bot
2026-11-14 10:58:34 +09:00
parent 3d58cf8ab1
commit ebf264d54b
2 changed files with 4 additions and 2 deletions

View File

@@ -356,7 +356,9 @@ between the normal placement and the game placement as games come and go (not wi
answers in progress (at most 2 minutes; the switch is numbered, so an idle report for an earlier
switch that came late does not count), restarts the LLM in the new stage and tells the brain it
is ready (or paused). The worker client keeps that latest state and sends it again first on
every connection; keeping, sending and a connection becoming ready share one lock, so a state set
every connection (`ready` says whether the game stage runs, so the worker holds partial
transcription while an answer is written in a game); keeping, sending and a connection becoming
ready share one lock, so a state set
while a worker connects is never lost. A restart that fails brings back the stage that ran
before and tells the brain ready; the failed stage is tried again 60 s after that is over, three
times at most, and the count starts over whenever another stage is wanted (also when the game

File diff suppressed because one or more lines are too long