Screen tree, register rows in the master list, and bot runs coded from the picks that were played
CI / test (pull_request) Canceled after 0s

- analysis/tree/build_tree.py -> data/public/tree.json, analysis/reports/TREE.md: every screen the bot has seen,
  every option, where each led (fixed or dice, with ranges), best known picks per colour chosen cautiously, where
  any picks end, and the untested options. solver.js screenPick(): least-tried and Thompson picks from the tree.
- The bot logs a pick it then overrode as a step: 37 runs were coded with choices they never made. Importer and
  graph.js now use the played steps only.
- runs_clean.csv: the Unofficial Dragon Register's 288 bonded dragons are in the master list as outcome-only
  rows, flagged (no analysis uses them).
- Cycle, refresh and the bot kit rebuild and carry the tree; tests check every generated report is current.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014jqCC2LZ4x1WHQ1V57nTsv
This commit is contained in:
ekcSchiano
2026-11-16 15:50:12 +00:00
co-authored by Claude Fable 5.2
parent d01ec46fcc
commit f8e4f575f4
25 changed files with 3613 additions and 163 deletions
+21
View File
@@ -309,3 +309,24 @@ Branch `first-attempt-cycle` (not merged, not pushed).
- **Not known.** What differs between fresh accounts that see the shadow and those that do not on the same route;
what "twenty" counts; why holding the Black's gaze fails three times in ten.
- **To tidy.** One public `bond_note` holds a rider's handle ("Run 116 - ..."), in a row marked as a first attempt.
## 12. Update, 2026-11-16 (later): the master list, the screen tree, and a fix to the bot's rows
- **Master list.** `runs_clean.csv` now has 8,853 rows: spreadsheet 8,132 (every row of "Form Responses 1"; the
workbook's other tabs are views of it), bot 421 (every trajectory), register 288 (new: bonded dragons, outcome
only, each flagged because the same run may be in the spreadsheet), Reddit result pages 12. Not in it because
nothing has been collected: Discord run reports (the only Discord export is the developer's channel, which holds
no runs), "Report a run" (0 reports), megathread comments (needs the Reddit API keys; the 12 were read by hand on
19 October). Stale: the spreadsheet was last fetched 12 November and the bot's data 10 November.
- **Possible duplicates, left in.** 17 spreadsheet rows are identical to another including the timestamp; 204 more
are identical except for the timestamp (the same route and death repeated, or a double submission).
- **Fix.** The bot logs a pick it then overrode as a step. 37 bot runs were coded with choices they never made
(direction, fork, dagger, reaction); they are now coded from the played steps (`collection/etl/runs.py` `played`,
`core/graph.js` `playedSteps`).
- **Screen tree.** `analysis/tree/build_tree.py` -> `data/public/tree.json` and `analysis/reports/TREE.md`, from
the bot's logs: 45 screens, 116 options (69 played), which options are dice and their rates, the best known picks
per colour (chosen cautiously), where any set of picks ends, and the untested options. Blue: a Blue waits on 11.4%
of meadow visits and the bonding chain has survived 18.7%, so 2.1% per run on the answers tried so far.
`screenPick()` in `core/solver.js` picks from the tree (least-tried, or Thompson). Rebuilt every cycle; in the kit.
- **Limit.** The tree treats a screen's odds as the same whatever came before. That is right for the seeded draws
and wrong for the shadow. It holds only what the bot has played: no first attempts, no shadow, one Green bond.