Skip to content

Observe: record player-order pauses and their resume (#270 agent side) - #299

Merged
pjerra merged 2 commits into
devfrom
fix-ta270-player-orders
Oct 23, 2026
Merged

pjerra merged 2 commits into
devfrom
fix-ta270-player-orders

Conversation

@pjerra

@pjerra pjerra commented Oct 23, 2026

Copy link
Copy Markdown
Owner

Part of #270 (agent side).

The observe report now lists each pause the run leader makes for a player's order in report.remote.observe.player_orders (step and order); controls records player order: ... and, when the run resumes, resumed after the player order; a player_order trace event is written. A pause that ends in a stop records no resume. The agent sends nothing new to the server.

Tests: the order pause and its resume, a repeated note counted once, a pause ending in a stop with no resume; mutations turn them red. go test ./... passes.
Reviews: Opus cold review (one fix: done counted as a resume), Codex review clean after the fix.

Still open on #270: the module side (TortoiseBots PauseForPlayer): whether a cmd summon during a run should skip the pause or resume by itself is a module decision.

A paused status whose note says the module paused for a player order (the
observer's own cmd summon, a move) is now in report.remote.observe.player_orders
with the step and the order; controls also records the player order and the
resume after it. The module's own note addenda count once.
@pjerra
pjerra merged commit 21bfbe2 into dev Oct 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant