Nothing checks an adapter's capabilities: manifest against its own bin/ directory #355
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#355
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-47-3-1on issue #47 during decision D-PO-47-3-1.Original scope note: AC-14's drift check covers only the shared-tier copy of the required-vs-gated classification, not manifest-vs-disk parity. Out of scope for #47: new lint capability against a surface the feature does not otherwise touch.
Disposition rationale: Recommended disposition. A manifest-vs-disk parity check is cheap (list bin/*.sh, diff against the operations: keys declared non-unsupported) and would have caught both the contract's own §4 example omission (close_issue/reopen_issue, standing since 2026-06-19) and the tea-cli/gh-cli omissions #47 fixed by hand. Resolved autonomously under the operator's standing instruction to resolve PO-47-3 as recommended.
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.