A roll-call that sees live agents. The gate checks the record's shape instead, so a roll-call cannot be proved complete — a limit accepted knowingly. #420
Labels
No labels
component:adapters
component:lifecycle
component:qa
component:setup
component:shared
component:worktrees
phase/accepted
phase/backlog
phase/deployed
phase/developing
phase/integrating
phase/planning
phase/qa
phase/requirements
phase/uat
priority:critical
priority:critical
priority:high
priority:high
priority:low
priority:low
priority:medium
priority:medium
type:bug
type:chore
type:docs
type:feature
type:infra
type:tech-debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jbr870/devwork-skills#420
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Spawned from finding
F-PO-45-2-4(out-of-scope) on issue #45 during decision D-PO-45-2-4.Original scope note: Flagged as out of scope in the approved PREQ: enumerating live agents would need harness-specific knowledge in the shipped helper tier, breaching the stack-agnostic rule.
Disposition rationale: A roll-call that enumerates live agents would need harness-specific knowledge inside the shipped helper tier, which the stack-agnostic rule forbids — so enforcement is on the record's shape, and a roll-call cannot be proved complete. That limit is accepted knowingly in the PREQ and restated in the SREQ's acceptance criteria. The stub carries the limit forward as a tracked, revisitable item: if the harness ever exposes a portable way to enumerate a phase's own spawns, this is the ticket that says what it would buy. Resolved under the operator's standing instruction of 2026-08-26 ("resolve all decisions as recommended"), which is the authority for taking each producer recommendation as given.
This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run
/dev:requirements --issue={new-number}to flesh it out before planning.