feat(agent): load disposable checkpoints and label test captures #89

Merged
HumanBean merged 1 commit from futondestroyer/Beanstalk-contributions:codex/agent-test-hud into main 2026-11-18 18:47:08 +00:00
Member

Gameplay plans that already have a suitable checkpoint should be able to start there, and local captures should say which job and machine produced them.

  • The default gameplay scenario copies the repository's Kokiri checkpoint into a fresh run profile and continues into play. The explicit title-screen scenario still covers start-up.
  • The runner passes a public agent pseudonym, PR number, and scenario label to Longshot's test HUD. Local annotated screenshots show the build, CPU and GPU, and Dev metrics. Screenshot comparison and report attachment selection use the matching clean frame. Builds without the test HUD keep their existing capture behavior.

Testing

  • 185 coordinator plan checks and 371 agent plan and scenario-isolation checks passed.
  • The related Longshot change loaded the checkpoint and captured the test HUD on Windows 11 with an RTX 4070 in both a visible window and an offscreen run.
  • The full coordinator suite needs Docker/Postgres here. The full agent suite stopped at a Windows symlink privilege check. A live volunteer sandbox job remains unverified.

Companion Longshot change: MagicBeanDev/Longshot#1539

Screenshot

Local offscreen smoke capture in Kokiri Forest using the Longshot test HUD.

Headless gameplay test HUD in Kokiri Forest

Gameplay plans that already have a suitable checkpoint should be able to start there, and local captures should say which job and machine produced them. - The default gameplay scenario copies the repository's Kokiri checkpoint into a fresh run profile and continues into play. The explicit title-screen scenario still covers start-up. - The runner passes a public agent pseudonym, PR number, and scenario label to Longshot's test HUD. Local annotated screenshots show the build, CPU and GPU, and Dev metrics. Screenshot comparison and report attachment selection use the matching clean frame. Builds without the test HUD keep their existing capture behavior. ## Testing - 185 coordinator plan checks and 371 agent plan and scenario-isolation checks passed. - The related Longshot change loaded the checkpoint and captured the test HUD on Windows 11 with an RTX 4070 in both a visible window and an offscreen run. - The full coordinator suite needs Docker/Postgres here. The full agent suite stopped at a Windows symlink privilege check. A live volunteer sandbox job remains unverified. Companion Longshot change: https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/1539 ## Screenshot Local offscreen smoke capture in Kokiri Forest using the Longshot test HUD. ![Headless gameplay test HUD in Kokiri Forest](https://git.magicbean.dev/attachments/e322c405-dbb1-4cb6-803b-3ef09d989ff7)
feat(agent): load disposable checkpoints and label test captures
Some checks failed
CI / Conventional Commit title (pull_request) Successful in 4s
CI / Workflow lint (actionlint) (pull_request) Successful in 4s
CI / Coordinator image (pull_request) Has been cancelled
CI / Coordinator tests (pull_request) Has been cancelled
CI / Agent build and checks (pull_request) Has been cancelled
e8322bf781
Assisted-by: OpenAI Codex
Member

For context, from #91: that PR makes a save: start set Longshot's HOS_OOT_BOOT_SAVE=slot_00 (MagicBeanDev/Longshot#1577) and press only while the game's status.boot_save does not carry the start, so this PR's default kokiri-start scenario would reach play with no title screen and no presses on builds that have it, and as now on builds that don't. The overlap is textual (RunSessionAsync's own environment, ScenarioIsolationChecks' per-start loop); I'll rebase #91 onto this one if it merges first.

For context, from https://git.magicbean.dev/MagicBeanDev/Beanstalk/pulls/91: that PR makes a save:<name> start set Longshot's HOS_OOT_BOOT_SAVE=slot_00 (MagicBeanDev/Longshot#1577) and press only while the game's status.boot_save does not carry the start, so this PR's default kokiri-start scenario would reach play with no title screen and no presses on builds that have it, and as now on builds that don't. The overlap is textual (RunSessionAsync's own environment, ScenarioIsolationChecks' per-start loop); I'll rebase #91 onto this one if it merges first.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Beanstalk!89
No description provided.