SirStone/SirRoboGarage
1
0
Fork 0
Code Issues 28 Pull Requests Actions Projects Releases Wiki Activity

Round-end checkpoint wiring #95

New Issue
Closed
opened 2026-08-26 07:36:06 +02:00 by SirStone · 1 comment
SirStone commented 2026-08-26 07:36:06 +02:00
Owner
Copy Link
Copy Source

Parent

Spec #92 (round-end checkpointing).

What to build

The feature end to end: the round-ended event handler stores the drained champion iff it beats the stored best; exactly one code path ever saves weights (game-end saving removed); each improvement emits one stderr log line with enemy key and new fitness; load order stays per-opponent → global → init.

Acceptance criteria

  • Multi-round lifecycle driven through the real-handler seam produces gated checkpoints every round
  • Worse and tied candidates leave the stored file untouched
  • Exactly one save point exists in production wiring (game-end save removed)
  • Every replacement logs enemy key and new fitness
  • Load order remains per-opponent → global → init
  • All existing harnesses green

Blocked by

  • #93 — champion+fitness transport
  • #94 — persistence v2 format/gating/durability/location
## Parent Spec #92 (round-end checkpointing). ## What to build The feature end to end: the round-ended event handler stores the drained champion iff it beats the stored best; exactly one code path ever saves weights (game-end saving removed); each improvement emits one stderr log line with enemy key and new fitness; load order stays per-opponent → global → init. ## Acceptance criteria - [ ] Multi-round lifecycle driven through the real-handler seam produces gated checkpoints every round - [ ] Worse and tied candidates leave the stored file untouched - [ ] Exactly one save point exists in production wiring (game-end save removed) - [ ] Every replacement logs enemy key and new fitness - [ ] Load order remains per-opponent → global → init - [ ] All existing harnesses green ## Blocked by - #93 — champion+fitness transport - #94 — persistence v2 format/gating/durability/location
SirStone added the ready-for-agent label 2026-08-26 07:36:06 +02:00
SirStone commented 2026-08-28 21:13:21 +02:00
Author
Owner
Copy Link
Copy Source

Superseded — dropping per-enemy weights, pivoting to global-only weights + improved GA/network.

Superseded — dropping per-enemy weights, pivoting to global-only weights + improved GA/network.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ready-for-agent
wayfinder:grilling
Wayfinder design question to grill
 wayfinder:map
Wayfinder map issue
 wayfinder:prototype
wayfinder:research
Wayfinder research question
 wayfinder:task
Wayfinder implementation task
No Label ready-for-agent
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
SirStone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SirStone/SirRoboGarage#95
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?