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
+3 -1
View File
@@ -22,7 +22,7 @@ python -m collection cycle --bot /path/to/DragonKind --deliver /path/to/DragonKi
2. **Refit.** When there are new runs it rebuilds the coded runs, the route model (`policy.json`) and
3. **Re-plan:** the experiment plan (`experiments.json`): progress per arm, and which experiments are still
running (`planner/experiments.yaml` is the design).
4. **Deliver.** It copies `policy.json`, `experiments.json`, `solver.js` and `graph.js` into the `--deliver` folder,
4. **Deliver.** It copies `policy.json`, `experiments.json`, `tree.json`, `solver.js` and `graph.js` into the `--deliver` folder,
each file whole, then writes `atlas-kit.json` (`policyId`, `planId`, checksums) last. The bot should load the
kit at the start of an attempt, never in the middle of one, and log both ids on the run.
@@ -57,6 +57,8 @@ const advisor = Solver.advisor(policy.samples.all, a.target, a.objective,
attempts; then the account retires, except two in ten, which keep going (one repeating a path, one varying it).
- `plan.record` lists what to log about the account on every run; `plan.scripts.shadow` is the sequence to follow
once the shadow shows (`docs/BOT_CYCLE_FOR_KEN.md`).
- `tree.json` is the screen tree (every screen, every option, where each led). `plan.screenPicks` says where the
bot picks from it with `Solver.screenPick(tree, sceneId, offeredTexts, { mode, seed })`.
- With squadmates, staying together and the direction are one screen; `recommendOption()` answers both at once
and says so in `also`.