Skip to content

REC-F06: Separate selection from gameplay success - #12

Merged
mattebad merged 1 commit into
mainfrom
recovery/rec-f06
Sep 13, 2026
Merged

mattebad merged 1 commit into
mainfrom
recovery/rec-f06

Conversation

@mattebad

Copy link
Copy Markdown
Owner

Scope

REC-F06: separate descriptive scheduler selection from gameplay success.

  • World, Nova, Recruitment, Campaign, and disabled handlers return the sole non-consuming SelectionPlan contract.
  • Explicit selector paths never claim or terminalize an occurrence; arbitrary real-runner planning remains behind RUNNING/dispatch fences.
  • Zero-input completion requires exact verified=True, ALREADY_COMPLETE, and an explicitly permitting matching handler FlowSpec.
  • Migrate CLI and scheduler consumers to selected-candidate/result-null behavior; preserve ordinary versus milestone action identities and AP eligibility.

Verification

  • Independent full reviewer: ACCEPT, all five acceptance criteria.
  • 76 focused and caller tests passed.
  • Selected offline check: 310 tests passed; directly affected suite: 117 passed; compileall passed.
  • Actual CLI smoke used temporary SQLite: two eligible pulses selected the same occurrence with result null, zero runs/actions, and zero transport.
  • Committed whitespace check passed. Windows/Linux CI required before merge.

Offline only: no native/device calls, production enablement, registration/policy promotion, or retained-evidence changes. Live registry consumption/caller cutovers remain held for F09/F13.

@mattebad
mattebad merged commit cc5f9f5 into main Sep 13, 2026
2 checks 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