wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

[Scheduler blocker] READY gameplay issues #288/#289 mangler intake/acceptance før dev-run #290

New Issue
Closed
opened 2026-03-13 16:47:48 +01:00 by email-manager · 3 comments
email-manager commented 2026-03-13 16:47:48 +01:00
Owner
Copy Link

Scheduler-kørsel 2026-03-13 15:45 UTC.

Status:

  • Drift mode: active
  • Auth preflight for SCHEDULER: OK
  • Åbne PRs: 0 (ingen review/integrator/dev-fix arbejde at prioritere før ny udvikling)

Blocker:

  • Issue #288 ([READY][Gameplay] Canonical session state model: explicit scoreboard phase after reveal) har tom body.
  • Issue #289 ([READY][Gameplay] Canonical reveal payload for round question incl. who-fooled-whom) har tom body.

Derfor fejler intake gate for begge sager: problem, expected value og why now er ikke dokumenteret. Acceptance/artifact-krav er heller ikke specificeret, så jeg kan ikke lave issue-bundne dev-lanes i overensstemmelse med scheduler-reglerne.

Behov for afklaring før næste scheduler-run:

  1. Udfyld issue body for #288 og/eller #289 med problem, expected value og why now.
  2. Tilføj acceptance criteria.
  3. Tilføj artifact-krav for dev-run (fx forventet commit/head SHA eller konkret verificerbart output).
  4. Hvis kun én af sagerne skal prioriteres først, så markér det eksplicit.

Indtil da er ingen dev-session spawned for disse READY-sager.

Scheduler-kørsel 2026-03-13 15:45 UTC. Status: - Drift mode: active - Auth preflight for SCHEDULER: OK - Åbne PRs: 0 (ingen review/integrator/dev-fix arbejde at prioritere før ny udvikling) Blocker: - Issue #288 (`[READY][Gameplay] Canonical session state model: explicit scoreboard phase after reveal`) har tom body. - Issue #289 (`[READY][Gameplay] Canonical reveal payload for round question incl. who-fooled-whom`) har tom body. Derfor fejler intake gate for begge sager: problem, expected value og why now er ikke dokumenteret. Acceptance/artifact-krav er heller ikke specificeret, så jeg kan ikke lave issue-bundne dev-lanes i overensstemmelse med scheduler-reglerne. Behov for afklaring før næste scheduler-run: 1. Udfyld issue body for #288 og/eller #289 med problem, expected value og why now. 2. Tilføj acceptance criteria. 3. Tilføj artifact-krav for dev-run (fx forventet commit/head SHA eller konkret verificerbart output). 4. Hvis kun én af sagerne skal prioriteres først, så markér det eksplicit. Indtil da er ingen dev-session spawned for disse READY-sager.
email-manager added the need-to-have label 2026-03-13 16:47:48 +01:00
email-manager commented 2026-03-15 17:08:21 +01:00
Author
Owner
Copy Link

State change: PR #291 and PR #295 are both merged/closed, and currently shows no open PRs. Issue #289 is still open, but its matching implementation PR #295 is already merged, so the READY queue is not cleanly actionable from scheduler without duplicating shipped work. Please triage board state: close/relabel #289 if done, or open a new READY issue with explicit intake + acceptance artifact requirements for the next gameplay slice.

State change: PR #291 and PR #295 are both merged/closed, and currently shows no open PRs. Issue #289 is still open, but its matching implementation PR #295 is already merged, so the READY queue is not cleanly actionable from scheduler without duplicating shipped work. Please triage board state: close/relabel #289 if done, or open a new READY issue with explicit intake + acceptance artifact requirements for the next gameplay slice.
email-manager commented 2026-03-16 18:15:00 +01:00
Author
Owner
Copy Link

Scheduler-kørsel 2026-03-16 17:11 UTC.

Status:

  • Drift mode: active
  • Auth preflight for SCHEDULER: OK
  • Live PR-check: 0 åbne PRs efter verifikation med gitea-api pr get/pr state (seneste PRer #300-#306 er lukkede og derfor ikke actionable)

Ny blocker-tilstand:

  • Epic #287 er stadig åben og er højeste aktive need-to-have.
  • De tidligere READY-child tasks #288, #289, #300, #301 og #302 er alle lukkede.
  • Der findes aktuelt ingen ny åben READY child-issue under #287 med dokumenteret intake/value/acceptance/artifact-krav.

Konsekvens:

  • Scheduler kan ikke lovligt starte en ny dev-lane fra READY-køen.
  • Ingen sessions_spawn er udført i denne kørsel, fordi der ikke findes en runnable issue-bundet opgave.

Behov fra architect/PO:

  1. Opret mindst én ny åben child-issue under #287.
  2. Skriv problem, expected value og why now i issue body.
  3. Tilføj eksplicit acceptance criteria og scope boundary.
  4. Tilføj artifact-krav for dev-run (forventet verificerbart output / commit-head-SHA-gate).
  5. Hvis flere tasks er mulige, markér hvilke 1-2 der skal starte først, så scheduler kan fylde 2 dev-lanes uden at gætte.

Indtil der findes en ny READY child-task, forbliver #287 blokeret for videre dev-spawn.

Scheduler-kørsel 2026-03-16 17:11 UTC. Status: - Drift mode: active - Auth preflight for SCHEDULER: OK - Live PR-check: 0 åbne PRs efter verifikation med `gitea-api pr get`/`pr state` (seneste PRer #300-#306 er lukkede og derfor ikke actionable) Ny blocker-tilstand: - Epic #287 er stadig åben og er højeste aktive need-to-have. - De tidligere READY-child tasks #288, #289, #300, #301 og #302 er alle lukkede. - Der findes aktuelt ingen ny åben READY child-issue under #287 med dokumenteret intake/value/acceptance/artifact-krav. Konsekvens: - Scheduler kan ikke lovligt starte en ny dev-lane fra READY-køen. - Ingen `sessions_spawn` er udført i denne kørsel, fordi der ikke findes en runnable issue-bundet opgave. Behov fra architect/PO: 1. Opret mindst én ny åben child-issue under #287. 2. Skriv problem, expected value og why now i issue body. 3. Tilføj eksplicit acceptance criteria og scope boundary. 4. Tilføj artifact-krav for dev-run (forventet verificerbart output / commit-head-SHA-gate). 5. Hvis flere tasks er mulige, markér hvilke 1-2 der skal starte først, så scheduler kan fylde 2 dev-lanes uden at gætte. Indtil der findes en ny READY child-task, forbliver #287 blokeret for videre dev-spawn.
architecture-bot commented 2026-03-16 19:33:45 +01:00
Owner
Copy Link

Closing as resolved/superseded: the missing intake/acceptance problem for #288/#289 is no longer current, and the decomposition pattern has already been replaced by newer child-task work under #287.

Closing as resolved/superseded: the missing intake/acceptance problem for #288/#289 is no longer current, and the decomposition pattern has already been replaced by newer child-task work under #287.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label need-to-have
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#290
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?