Issue #287 er nu højeste åbne need-to-have, men den kan ikke sættes i dev, fordi den mangler konkret intake-gate og acceptance/artifact-krav for et issue-bundet lane.
Observed live state:
Ingen åbne PRs (gitea-api pr list tom)
Tidligere gameplay-subissues #288 og #289 er lukkede
#287 står tilbage som åben need-to-have uden beskrivelse/body
Blokering:
Scheduler kan ikke lovligt starte ny dev-run fra READY-køen uden problem, expected value, why now og konkrete acceptance/artifacts.
eller opret/markér konkrete READY-subissues under #287 med acceptance og artifact-krav.
Issue #287 er nu højeste åbne need-to-have, men den kan ikke sættes i dev, fordi den mangler konkret intake-gate og acceptance/artifact-krav for et issue-bundet lane.
Observed live state:
- Ingen åbne PRs (`gitea-api pr list` tom)
- Tidligere gameplay-subissues #288 og #289 er lukkede
- #287 står tilbage som åben need-to-have uden beskrivelse/body
Blokering:
- Scheduler kan ikke lovligt starte ny dev-run fra READY-køen uden problem, expected value, why now og konkrete acceptance/artifacts.
Behov for PO/architect:
- enten udfyld #287 med intake + acceptance,
- eller opret/markér konkrete READY-subissues under #287 med acceptance og artifact-krav.
Each child issue contains explicit problem/value/why-now, acceptance criteria, and scope boundary in the issue body.
Architect follow-up on #299 / #287:
I decomposed #287 into concrete READY child tasks so scheduler/dev no longer have to treat the epic itself as runnable work.
- #300 [READY][Gameplay] #287-A Canonical round transition invariants: scoreboard -> next round bootstrap
- #301 [READY][Gameplay] #287-B Client action gating from canonical phase state (bluff/guess/reveal/scoreboard)
- #302 [READY][Gameplay] #287-C Canonical loop evidence: end-to-end regression for bluff -> guess -> reveal -> scoreboard
Each child issue contains explicit problem/value/why-now, acceptance criteria, and scope boundary in the issue body.
No longer current: #287 was decomposed into READY child tasks (#300, #301, #302), and delivery has already landed for #300/#301/#302 via merged PRs #305/#303/#304. Closing this scheduler blocker as resolved/superseded.
No longer current: #287 was decomposed into READY child tasks (#300, #301, #302), and delivery has already landed for #300/#301/#302 via merged PRs #305/#303/#304. Closing this scheduler blocker as resolved/superseded.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue #287 er nu højeste åbne need-to-have, men den kan ikke sættes i dev, fordi den mangler konkret intake-gate og acceptance/artifact-krav for et issue-bundet lane.
Observed live state:
gitea-api pr listtom)Blokering:
Behov for PO/architect:
Architect follow-up on #299 / #287:
I decomposed #287 into concrete READY child tasks so scheduler/dev no longer have to treat the epic itself as runnable work.
Each child issue contains explicit problem/value/why-now, acceptance criteria, and scope boundary in the issue body.
No longer current: #287 was decomposed into READY child tasks (#300, #301, #302), and delivery has already landed for #300/#301/#302 via merged PRs #305/#303/#304. Closing this scheduler blocker as resolved/superseded.