panopticon-cli 0.5.9 → 0.5.10

package/dist/close-issue-5OMOP2FU.js

@@ -0,0 +1,9 @@
+import {
+  closeIssue
+} from "./chunk-GIW2TUWI.js";
+import "./chunk-SFX3BG6N.js";
+import "./chunk-ZHC57RCV.js";
+export {
+  closeIssue
+};
+//# sourceMappingURL=close-issue-5OMOP2FU.js.map

package/dist/compact-beads-YQDVF6FQ.js

@@ -0,0 +1,9 @@
+import {
+  compactBeads
+} from "./chunk-JZWCL5S5.js";
+import "./chunk-SFX3BG6N.js";
+import "./chunk-ZHC57RCV.js";
+export {
+  compactBeads
+};
+//# sourceMappingURL=compact-beads-YQDVF6FQ.js.map

package/dist/dashboard/prompts/merge-agent.md

@@ -135,6 +135,17 @@ Detect the project type and run the appropriate **production** build command:
 - Modify files outside the conflict resolution
 - Push to remote (the caller handles pushing)
 
+### 5. Pre-Merge AC Validation
+
+Before signaling completion, verify all vBRIEF acceptance criteria are met:
+
+1. Read `.planning/plan.vbrief.json` in the workspace (if it exists)
+2. Check all items' `subItems` where `metadata.kind === "acceptance_criterion"`
+3. If **any AC has status other than "completed" or "cancelled"**, REFUSE to merge and report what's missing
+4. If no plan or no AC exist, skip this check (legacy workspaces)
+
+This is the last line of defense — even if the verification gate was bypassed (circuit breaker), you catch incomplete AC here.
+
 ## Signal Completion (CRITICAL)
 
 When you're done, you MUST call the API to update status:

package/dist/dashboard/prompts/review-agent.md

@@ -35,6 +35,15 @@ You are a **demanding** code review specialist for the Panopticon project. Your
 - **Files Changed:**
 {{filesChanged}}
 
+{{#if acceptanceCriteria}}
+## Acceptance Criteria (from vBRIEF Plan)
+
+Verify each criterion has corresponding implementation and test coverage.
+Flag any AC that is not addressed by the code changes.
+
+{{acceptanceCriteria}}
+
+{{/if}}
 ## Your Task
 
 ### Step 0: Check for Stale Branch (MUST DO FIRST)

package/dist/dashboard/prompts/test-agent.md

@@ -24,6 +24,15 @@ You are a test execution specialist for the Panopticon project.
 - **Branch:** {{branch}}
 - **Test Command Override:** {{testCommand}}
 
+{{#if acceptanceCriteria}}
+## Acceptance Criteria (from vBRIEF Plan)
+
+After running tests, verify test coverage against each criterion below.
+If any AC has no corresponding test, report it as a finding.
+
+{{acceptanceCriteria}}
+
+{{/if}}
 ## Your Task
 
 Detect the project's test runner, execute the full test suite, analyze failures, and attempt simple fixes if needed.

package/dist/dashboard/prompts/work-agent.md

@@ -112,7 +112,7 @@ If you batch multiple beads, the inspector cannot verify them individually and y
 will be rejected.
 
 **Workflow for EVERY bead:**
-1. `bd ready` — find the next unblocked bead
+1. `bd ready -l {{ISSUE_ID_LOWER}}` — find the next unblocked bead for THIS issue
 2. `bd update <bead-id> --claim` — claim it
 3. Implement ONLY that bead's work
 4. `git add` and `git commit` — one bead = one commit
@@ -121,6 +121,10 @@ will be rejected.
 7. `INSPECTION PASSED` → proceed to step 1
 8. `INSPECTION BLOCKED` → fix, commit, `bd close` again
 
+**IMPORTANT:** Always use `-l {{ISSUE_ID_LOWER}}` with `bd ready` and `bd list` to scope
+to this issue's beads. The shared database contains beads from ALL issues — without the
+label filter you will see irrelevant beads from other workspaces.
+
 **Do NOT implement multiple beads before committing and closing.** Each bead must be
 a separate commit with a separate `bd close`. The inspection fires automatically on
 `bd close` — you do not need to call `pan inspect` manually.
@@ -192,7 +196,7 @@ If you batch multiple beads into one commit, the inspector cannot verify them in
 and your work will be rejected.
 
 **Workflow for EVERY bead:**
-1. `bd ready` — find the next unblocked bead
+1. `bd ready -l {{ISSUE_ID_LOWER}}` — find the next unblocked bead for THIS issue
 2. `bd update <bead-id> --claim` — claim it
 3. Implement ONLY that bead's work
 4. `git add` and `git commit` — one bead = one commit
@@ -201,6 +205,10 @@ and your work will be rejected.
 7. `INSPECTION PASSED` → proceed to step 1
 8. `INSPECTION BLOCKED` → fix, commit, `bd close` again
 
+**IMPORTANT:** Always use `-l {{ISSUE_ID_LOWER}}` with `bd ready` and `bd list` to scope
+to this issue's beads. The shared database contains beads from ALL issues — without the
+label filter you will see irrelevant beads from other workspaces.
+
 **Do NOT implement multiple beads before committing and closing.** Each bead must be
 a separate commit with a separate `bd close`. The inspection fires automatically on
 `bd close` — you do not need to call `pan inspect` manually.