Files

T

claude-checkpoint-tooling 8c54129bcd Update PC1 playtest instructions for the new dashboard controls

Replaces the manual multi-step shell commands (docker compose, alembic,
uvicorn with env vars, manual teardown) with the one-click dashboard
flow at /checkpoint/PC1 in ~/agp (commit 261c45f): Start Backend / Stop
& Clean Up, and Build / Download a pre-configured Windows .exe. No
terminal commands needed on either machine.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-20 12:51:27 +00:00

3.0 KiB

Raw Blame History

Package Checkpoint 1 (PC1)

Validated 2026-08-20 against main commit 927f9bd, from a genuinely fresh clone (not a reused agent workspace).

Automated validation

Run with scripts/run_checkpoint_tests.py — see docs/testing/test_inventory.md for exactly what each suite covers.

Check	Result
Alembic migrations, fresh DB	PASS
Backend pytest	68/68 PASS
Godot smoke tests (4 files)	ALL PASS
Linux export (`agp-game.x86_64`)	Builds, verified as a real ELF64 binary
Windows export (`agp-game.exe`)	Builds, verified as a real PE32+ binary

Problems found during this checkpoint (fixed, tracked as tasks)

Roadmap showed the Godot Engine Scaffold feature amber despite 6/6 tasks done — a historical data gap (a review-feedback follow-up task's supersession link was never recorded, predating when that field started being tracked). Backfilled in the PM database; confirmed green.
docs/testing/test_inventory.md was stale (said 38 backend tests, actually 68; said no integration tests existed, 4 real ones had landed). Fixed via task 398bf1a22a2d / PR #40.

What's actually testable right now

Login/register/browse-worlds only — there's no joinable gameplay yet. That's the real scope of PC1; don't expect more when playtesting.

Register a new account (18+ only, rejected otherwise)
Log out, log back in with the same credentials
Play → Browse Worlds — loads a (currently empty) world list with no errors

Manual playtest: backend on cloudbison, client on pinkbison

As of 2026-08-20 this is dashboard-controlled — no terminal commands, no env vars, no editing files. Foolproof enough to hand to someone else.

1. On cloudbison — the AGP dashboard

Open the dashboard (http://cloudbison:7070, or its Tailscale address) and go to PC1 in the nav bar (/checkpoint/PC1). Click Start Backend — it pulls the latest main, stands up Postgres, runs migrations, and starts the API server, all in one step. The page shows the LAN address it's reachable at once it's up (under a minute).

When you're done playtesting, click Stop & Clean Up on the same page — it tears down everything that step started (API server, Postgres container, its volume and network). Nothing is left running or lying around afterward, even if the dashboard itself gets restarted in between.

2. On pinkbison — download and run the .exe

Same dashboard page: click Build .exe the first time (or Rebuild to pick up newer changes) — this pulls the latest main and exports a Windows binary with cloudbison's backend address already baked in. Click Download agp-game.exe, copy it to pinkbison, and just run it. No environment variable, no config file, no build step on pinkbison at all.

3. Tear down when done

Stop & Clean Up on the dashboard page. That's it.

Status

config/checkpoint_focus_feature_ids in the AGP framework (~/agp) still restricts agent claiming to the 5 PC1-scope features. Agents will not move on to post-PC1 work until that's widened.

3.0 KiB Raw Blame History