Bot handoff: pull Ken's bot data daily; send route model updates to the bot by PR #12

Merged
kathleen merged 1 commits from bot-handoff into main 2026-11-19 02:21:39 +00:00
Owner

Bot runs into the Atlas. The daily source check now downloads DragonKind/DragonKind and imports it as the bot source, using the importer that was already here (it strips game text and hashes account names). Ken's bot doesn't need to push anything. This needs the DK_ACCOUNT_SALT secret; without it, the bot source is skipped as before.

  • All bot attempts are kept in one file, data/bot/trajectories-bot.jsonl, merged by attempt id. The bot's repo holds each account's full history, so every import contains everything earlier ones did: the old one-file-per-import approach would have duplicated every attempt each day, and build-graph.js would have counted them twice.
  • Attempts that are no longer in the bot's repo stay in the file.

Route model to the bot. A new workflow, push-policy, runs whenever policy.json, solver.js or graph.js changes on main. It opens or updates one pull request on DragonKind/DragonKind (branch atlas/route-model) that replaces vendor/threshing-atlas/ with the new files. Ken reviews and merges it.

forge open-pr can now target another repo with --repo/--base, and reuses an already open pull request for the same branch.

🤖 Generated with Claude Code

**Bot runs into the Atlas.** The daily source check now downloads `DragonKind/DragonKind` and imports it as the `bot` source, using the importer that was already here (it strips game text and hashes account names). Ken's bot doesn't need to push anything. This needs the `DK_ACCOUNT_SALT` secret; without it, the bot source is skipped as before. - All bot attempts are kept in one file, `data/bot/trajectories-bot.jsonl`, merged by attempt id. The bot's repo holds each account's full history, so every import contains everything earlier ones did: the old one-file-per-import approach would have duplicated every attempt each day, and `build-graph.js` would have counted them twice. - Attempts that are no longer in the bot's repo stay in the file. **Route model to the bot.** A new workflow, `push-policy`, runs whenever `policy.json`, `solver.js` or `graph.js` changes on main. It opens or updates one pull request on `DragonKind/DragonKind` (branch `atlas/route-model`) that replaces `vendor/threshing-atlas/` with the new files. Ken reviews and merges it. `forge open-pr` can now target another repo with `--repo`/`--base`, and reuses an already open pull request for the same branch. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
kathleen added 1 commit 2026-11-19 02:20:52 +00:00
- update-sources: download DragonKind/DragonKind (read with ATLAS_BOT_TOKEN, or DRAGONKIND_TOKEN if set) and
  import it as the bot source. Needs DK_ACCOUNT_SALT (the same salt as earlier imports, so accounts keep their keys);
  without it the bot source is skipped as before.
- The bot load keeps one file, data/bot/trajectories-bot.jsonl: the bot's repo holds every account's full history,
  so each import is merged by attempt id (attempts already published stay; older per-import files are folded in).
  One copy of each attempt also keeps build-graph.js from counting an attempt twice.
- New workflow push-policy: when policy.json, solver.js or graph.js change on main, open (or update) a pull request
  on DragonKind/DragonKind that replaces vendor/threshing-atlas/ with them. Ken merges it.
- forge open-pr: --repo/--base for another repository, and reuse the open pull request for the same branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
kathleen merged commit 30aabdf084 into main 2026-11-19 02:21:39 +00:00
kathleen deleted branch bot-handoff 2026-11-19 02:21:39 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DragonKind/threshing-atlas#12