@geraldmaron/construct 1.0.7 → 1.0.9

package/specialists/policy-inventory.json

@@ -0,0 +1,160 @@
+{
+  "version": 1,
+  "description": "Single source of truth for Construct policy gates. Each entry maps a rule source file to its enforcement mechanism, enforcement mode, and a one-line description. Consumed by `construct policy show` and the CI inventory-coverage test.",
+  "policies": [
+    {
+      "id": "file-path-fence",
+      "source": "specialists/role-manifests.json",
+      "enforcement": "lib/roles/fence.mjs#checkAction",
+      "mode": "deterministic",
+      "description": "Prevents specialists from touching files outside their declared path scope."
+    },
+    {
+      "id": "action-approval",
+      "source": "specialists/role-manifests.json",
+      "enforcement": "lib/roles/fence.mjs#checkAction",
+      "mode": "deterministic",
+      "description": "Blocks specialists from taking actions not listed in their approved action set."
+    },
+    {
+      "id": "no-fabrication",
+      "source": "rules/common/no-fabrication.md",
+      "enforcement": "lib/comment-lint.mjs",
+      "mode": "deterministic-85",
+      "description": "Detects fabrication-risk patterns (manufactured confidence, uncited claims, hand-wave percentages) in artifact prose."
+    },
+    {
+      "id": "release-gates",
+      "source": "rules/common/release-gates.md",
+      "enforcement": "lib/hooks/pre-push-gate.mjs",
+      "mode": "deterministic",
+      "description": "Enforces test + build + lint gates before any push reaches the remote."
+    },
+    {
+      "id": "contract-preconditions",
+      "source": "specialists/contracts.json",
+      "enforcement": "lib/contracts/validate.mjs#validateHandoff",
+      "mode": "deterministic",
+      "description": "Validates that specialist handoffs conform to declared pre/postconditions in contracts.json."
+    },
+    {
+      "id": "bash-safety",
+      "source": "built-in",
+      "enforcement": "lib/hooks/guard-bash.mjs",
+      "mode": "deterministic",
+      "description": "Blocks destructive bash commands (rm -rf /, git reset --hard HEAD, etc.) from running."
+    },
+    {
+      "id": "bootstrap-state",
+      "source": "built-in",
+      "enforcement": "lib/hooks/policy-engine.mjs",
+      "mode": "deterministic",
+      "description": "State machine enforces valid session bootstrap sequence before any agent work begins."
+    },
+    {
+      "id": "secret-scan",
+      "source": "built-in",
+      "enforcement": "lib/hooks/scan-secrets.mjs",
+      "mode": "deterministic",
+      "description": "Scans added lines for credential patterns before any file is written."
+    },
+    {
+      "id": "beads-hygiene",
+      "source": "rules/common/beads-hygiene.md",
+      "enforcement": "lib/contracts/validate.mjs#validateBeadsCloseReason",
+      "mode": "deterministic",
+      "description": "Validates beads close-reason quality: requires PR reference or file:line evidence."
+    },
+    {
+      "id": "commit-approval",
+      "source": "rules/common/commit-approval.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Requires explicit user confirmation before any git commit or push. Enforced at the conversation level."
+    },
+    {
+      "id": "framing",
+      "source": "rules/common/framing.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Requires that execution artifacts cite their source; prevents specialists from treating their own output as ground truth."
+    },
+    {
+      "id": "research-evidence",
+      "source": "rules/common/research.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Enforces evidence hierarchy and citation discipline in research and analysis artifacts."
+    },
+    {
+      "id": "doc-ownership",
+      "source": "rules/common/doc-ownership.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Routes artifacts to the correct specialist owner before writing (PRD to PM, ADR to Architect)."
+    },
+    {
+      "id": "code-review",
+      "source": "rules/common/code-review.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Review standards applied by cx-reviewer and cx-qa before any change is marked done."
+    },
+    {
+      "id": "testing",
+      "source": "rules/common/testing.md",
+      "enforcement": "lib/hooks/pre-push-gate.mjs",
+      "mode": "deterministic",
+      "description": "Tests must pass before push; multi-component features require a functional test in tests/functional/."
+    },
+    {
+      "id": "comments",
+      "source": "rules/common/comments.md",
+      "enforcement": "lib/comment-lint.mjs",
+      "mode": "deterministic",
+      "description": "Enforces the two-form comment policy (file header + section context block). Blocks inline narration."
+    },
+    {
+      "id": "security",
+      "source": "rules/common/security.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Security review checklist applied by cx-security and cx-reviewer on any change touching auth, credentials, or external I/O."
+    },
+    {
+      "id": "agents-routing",
+      "source": "rules/common/cx-agent-routing.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Routing discipline: construct routes to specialists, specialists do not self-route except to adjacent roles."
+    },
+    {
+      "id": "skill-routing",
+      "source": "rules/common/cx-skill-routing.md",
+      "enforcement": "(persona prompt + lib/mcp/tools/skills.mjs)",
+      "mode": "honor-system",
+      "description": "Specialists load skills explicitly via get_skill rather than relying on ambient knowledge."
+    },
+    {
+      "id": "git-workflow",
+      "source": "rules/common/git-workflow.md",
+      "enforcement": "lib/hooks/pre-push-gate.mjs",
+      "mode": "deterministic",
+      "description": "Enforces branch naming, commit message style, and push guard (no direct-to-main pushes)."
+    },
+    {
+      "id": "coding-style",
+      "source": "rules/common/coding-style.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Style standards applied at authoring time; not mechanically enforced beyond lint:comments."
+    },
+    {
+      "id": "patterns",
+      "source": "rules/common/patterns.md",
+      "enforcement": "(persona prompt)",
+      "mode": "honor-system",
+      "description": "Architectural pattern guidance (module boundaries, error handling, async contracts) applied at authoring time."
+    }
+  ]
+}

package/{agents → specialists}/prompts/cx-accessibility.md

@@ -34,6 +34,6 @@ For each finding: WCAG criterion violated, user impact, specific element (file:l
 
 Construct may dispatch you in response to a `handoff.received` or `a11y.violation` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (agents/role-manifests.json → accessibility): allowed paths `docs/accessibility/**`, `docs/a11y/**`; allowed bd labels `accessibility`, `a11y`; approval required for every edit. You are read-only against production code by design.
+**Fence** (specialists/role-manifests.json → accessibility): allowed paths `docs/accessibility/**`, `docs/a11y/**`; allowed bd labels `accessibility`, `a11y`; approval required for every edit. You are read-only against production code by design.
 
 You file findings to bd notes and write a11y reports inside the fence. **Must not** edit code: hand fixes to engineer via `next:cx-engineer`, or design changes to `next:cx-designer`.

package/{agents → specialists}/prompts/cx-ai-engineer.md

@@ -102,4 +102,4 @@ Treat prompts as code with full version control:
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → ai-engineer`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → ai-engineer`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.

package/{agents → specialists}/prompts/cx-architect.md

@@ -46,6 +46,6 @@ When producing an implementation plan, use the canonical task format:
 
 Construct may dispatch you in response to a `handoff.received`, `adr.requested`, or `arch.boundary.violated` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (declared in agents/role-manifests.json → architect): allowed paths `docs/adr/**`, `docs/rfc/**`, `docs/concepts/architecture.md`, `docs/system-design/**`; allowed bd labels `architecture`, `adr`, `rfc`, `design`; approval required for any commit/push or code edit.
+**Fence** (declared in specialists/role-manifests.json → architect): allowed paths `docs/adr/**`, `docs/rfc/**`, `docs/concepts/architecture.md`, `docs/system-design/**`; allowed bd labels `architecture`, `adr`, `rfc`, `design`; approval required for any commit/push or code edit.
 
 You produce ADRs, RFCs, system-design documents, and architecture-overview updates inside the fence. You **must not** edit code without user approval per `rules/common/commit-approval.md`. **Handoff syntax**: append `next:cx-<role>` as a bd label. Typical: `next:cx-engineer` (build it), `next:cx-platform-engineer` (infra impact), `next:cx-reviewer` (design review).

package/{agents → specialists}/prompts/cx-business-strategist.md

@@ -30,7 +30,7 @@ DECISION DEADLINE: when this must be decided and why
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → business-strategist`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → business-strategist`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
 
 ## Automatic activation
 

package/{agents → specialists}/prompts/cx-data-analyst.md

@@ -89,4 +89,4 @@ If you receive work that was misclassified (e.g., assigned to you but actually r
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → data-analyst`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → data-analyst`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.

package/{agents → specialists}/prompts/cx-data-engineer.md

@@ -35,4 +35,4 @@ When given a task:
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → data-engineer`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → data-engineer`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.

package/{agents → specialists}/prompts/cx-debugger.md

@@ -32,6 +32,6 @@ After 2 passes without clear root cause: WebSearch with the exact error message.
 
 Construct may dispatch you in response to a `handoff.received`, `regression.detected`, or `hang.detected` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (declared in agents/role-manifests.json → debugger): allowed paths `docs/debug/**`, `tests/**` (read); allowed bd labels `bug`, `regression`, `investigation`; approval required for any commit/push or production code edit.
+**Fence** (declared in specialists/role-manifests.json → debugger): allowed paths `docs/debug/**`, `tests/**` (read); allowed bd labels `bug`, `regression`, `investigation`; approval required for any commit/push or production code edit.
 
 You investigate, write reproduction steps in bd notes, write debugging memos inside the fence. You **must not** edit production code without user approval: hand off to cx-engineer with `next:cx-engineer` once root cause is confirmed.

package/{agents → specialists}/prompts/cx-designer.md

@@ -49,6 +49,6 @@ Stay involved during implementation: flag experience drift. Incorporate cx-devil
 
 Construct may dispatch you in response to a `handoff.received` or `design.requested` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (agents/role-manifests.json → designer): allowed paths `docs/design/**`, `docs/wireframes/**`, `design/**`; allowed bd labels `design`, `ux`, `ui`, `wireframe`; approval required for any code or commit/push.
+**Fence** (specialists/role-manifests.json → designer): allowed paths `docs/design/**`, `docs/wireframes/**`, `design/**`; allowed bd labels `design`, `ux`, `ui`, `wireframe`; approval required for any code or commit/push.
 
 You produce wireframes, design briefs, and visual decision docs inside the fence. **Must not** edit production code without user approval. **Handoff syntax**: `next:cx-accessibility` (a11y review), `next:cx-engineer` (build), `next:cx-product-manager` (scope discussion).

package/{agents → specialists}/prompts/cx-devil-advocate.md

@@ -39,4 +39,4 @@ For each challenge: state the specific risk, what triggers it, and what resolves
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → devil-advocate`. You are read-only by design; **must not** commit or edit any code. Hand findings off via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → devil-advocate`. You are read-only by design; **must not** commit or edit any code. Hand findings off via `next:cx-<role>` bd label.

package/{agents → specialists}/prompts/cx-docs-keeper.md

@@ -140,10 +140,10 @@ Keep `.cx/context.md` under 100 lines:
 
 Construct may dispatch you in response to a `pr.merged.no-docs`, `changelog.missing`, or `readme.stale` event. A doc-drift bd issue already exists with the event payload: read it first via `bd show <id>`.
 
-**Fence (declared in agents/role-manifests.json → docs-keeper):**
+**Fence (declared in specialists/role-manifests.json → docs-keeper):**
 - Allowed paths: `docs/**`, `**/README.md`, `CHANGELOG.md`
 - Allowed bd labels: `docs`, `doc-drift`, `changelog`
-- Approval required: any commit, any push, any edit to `lib/**`, `bin/**`, or `agents/**`
+- Approval required: any commit, any push, any edit to `lib/**`, `bin/**`, or `specialists/**`
 
 You may **edit docs autonomously within your fence** (the in-fence write is the whole point of the role). You **must not commit** without user approval per `rules/common/commit-approval.md`. Stage edits and stop; let the user review and commit.
 

package/{agents → specialists}/prompts/cx-engineer.md

@@ -41,10 +41,10 @@ If cx-devil-advocate flagged a CRITICAL issue, resolve it before shipping.
 
 Construct may dispatch you in response to a `handoff.received`, `incident.handoff`, `bug.assigned`, or `feature.assigned` event. A bd issue already exists with the event payload: read it first via `bd show <id>`. Most invocations come as handoffs from cx-sre (incident → fix), cx-qa (failed test → fix), cx-security (vulnerability → patch), or cx-docs-keeper (drift → code clarification).
 
-**Fence (declared in agents/role-manifests.json → engineer):**
+**Fence (declared in specialists/role-manifests.json → engineer):**
 - Allowed paths: `lib/**`, `bin/**`, `src/**`, `app/**`, `tests/**`, `docs/**`
 - Allowed bd labels: `bug`, `feature`, `task`, `engineering`, `fix`
-- Approval required: any commit, any push, any edit to protected files (`agents/registry.json`, `install.sh`, `claude/settings.template.json`)
+- Approval required: any commit, any push, any edit to protected files (`specialists/registry.json`, `install.sh`, `claude/settings.template.json`)
 
 You may edit production code, write tests, and run verification freely inside your fence. You **must not commit or push** without explicit user approval per `rules/common/commit-approval.md`. Stage edits, run verification, and stop.
 

package/{agents → specialists}/prompts/cx-evaluator.md

@@ -29,4 +29,4 @@ For AI/prompt evaluation: define input/output pairs before changing prompts. Run
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` or `eval.regression` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → evaluator`. **Must not** commit, push, or edit production code without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` or `eval.regression` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → evaluator`. **Must not** commit, push, or edit production code without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.

package/{agents → specialists}/prompts/cx-explorer.md

@@ -42,7 +42,7 @@ Do not propose solutions unless asked.
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → explorer`. You are read-only by design; **must not** commit or edit any code. Hand findings off via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → explorer`. You are read-only by design; **must not** commit or edit any code. Hand findings off via `next:cx-<role>` bd label.
 
 ## Automatic activation
 

package/{agents → specialists}/prompts/cx-legal-compliance.md

@@ -28,7 +28,7 @@ Output: risk list with severity (must-fix / should-fix / monitor). You do not pr
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → legal-compliance`. You are advisory-only by design; **must not** commit or edit any code. Hand findings off via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → legal-compliance`. You are advisory-only by design; **must not** commit or edit any code. Hand findings off via `next:cx-<role>` bd label.
 
 ## Automatic activation
 

package/{agents → specialists}/prompts/cx-operations.md

@@ -31,7 +31,7 @@ Track throughout: compare active work against the accepted plan. Flag drift, blo
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → operations`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → operations`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
 
 ## Automatic activation
 

package/{agents → specialists}/prompts/cx-orchestrator.md

@@ -28,7 +28,7 @@ You are cx-orchestrator: invoked when a dispatch requires multi-specialist coord
 
 ## Routing substrate
 
-Read `agents/contracts.json` as the authoritative source for producer→consumer contracts: it defines what artifact each handoff must carry, what preconditions must hold, and what postconditions define DONE for each specialist pair. Before dispatching a specialist, check whether a contract exists for the producer→consumer pair you're wiring up.
+Read `specialists/contracts.json` as the authoritative source for producer→consumer contracts: it defines what artifact each handoff must carry, what preconditions must hold, and what postconditions define DONE for each specialist pair. Before dispatching a specialist, check whether a contract exists for the producer→consumer pair you're wiring up.
 
 ## Routing rules
 
@@ -60,4 +60,4 @@ Each handoff must name:
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → orchestrator`. Must not commit, push, or edit code without user approval per `rules/common/commit-approval.md`.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → orchestrator`. Must not commit, push, or edit code without user approval per `rules/common/commit-approval.md`.

package/{agents → specialists}/prompts/cx-platform-engineer.md

@@ -77,6 +77,6 @@ After:
 
 Construct may dispatch you in response to a `handoff.received`, `infra.change.requested`, or `service.scale.event` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (declared in agents/role-manifests.json → platform-engineer): allowed paths `docs/platform/**`, `docs/infra/**`, `infra/**`, `terraform/**`, `k8s/**`; allowed bd labels `platform`, `infrastructure`, `infra`; approval required for any commit/push or edit to `lib/**`/`bin/**`.
+**Fence** (declared in specialists/role-manifests.json → platform-engineer): allowed paths `docs/platform/**`, `docs/infra/**`, `infra/**`, `terraform/**`, `k8s/**`; allowed bd labels `platform`, `infrastructure`, `infra`; approval required for any commit/push or edit to `lib/**`/`bin/**`.
 
 You propose CI/CD changes, infra updates, build improvements via docs inside the fence. You **must not** apply infra changes via direct commit: hand off with `next:cx-sre` (reliability review), `next:cx-engineer` (code-side wiring), `next:cx-reviewer` (second-look on platform change).

package/{agents → specialists}/prompts/cx-product-manager.md

@@ -36,6 +36,6 @@ OPEN QUESTIONS: a small set of questions (typically 3-7) that would change scope
 
 Construct may dispatch you in response to a `handoff.received`, `backlog.stale`, or `prd.requested` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (declared in agents/role-manifests.json → product-manager): allowed paths `docs/prd/**`, `docs/meta-prd/**`, `docs/prfaq/**`, `docs/one-pager/**`, `.cx/knowledge/**`; allowed bd labels `product`, `prd`, `backlog`, `feature`; approval required for any commit/push or code edit.
+**Fence** (declared in specialists/role-manifests.json → product-manager): allowed paths `docs/prd/**`, `docs/meta-prd/**`, `docs/prfaq/**`, `docs/one-pager/**`, `.cx/knowledge/**`; allowed bd labels `product`, `prd`, `backlog`, `feature`; approval required for any commit/push or code edit.
 
 You author PRDs, PRFAQs, one-pagers, backlog proposals; you may adjust bd priorities (`bd priority`) inside the fence. You **must not** edit code without user approval. **Handoff syntax**: typical `next:cx-architect` (design needed), `next:cx-engineer` (build), `next:cx-researcher` (evidence gap), `next:cx-designer` (UX).

package/{agents → specialists}/prompts/cx-qa.md

@@ -114,7 +114,7 @@ Every test MUST be:
 
 Construct may dispatch you in response to a `test.fail`, `test.flake`, or `coverage.drop` event. A bug bd issue already exists with the event payload: read it first via `bd show <id>`.
 
-**Fence (declared in agents/role-manifests.json → qa):**
+**Fence (declared in specialists/role-manifests.json → qa):**
 - Allowed paths: `docs/qa/**`, `docs/test-plans/**`
 - Allowed bd labels: `bug`, `qa`, `test`, `flake`
 - Approval required: any commit, any push, any edit to `tests/**`, `lib/**`, or `bin/**`

package/{agents → specialists}/prompts/cx-rd-lead.md

@@ -30,7 +30,7 @@ WHAT NOT TO PRODUCTIONIZE YET: explicit list of components that must not harden
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → rd-lead`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → rd-lead`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
 
 ## Automatic activation
 

package/{agents → specialists}/prompts/cx-release-manager.md

@@ -36,6 +36,6 @@ Rollback trigger: any CRITICAL finding post-deploy OR SLO breach → immediate r
 
 Construct may dispatch you in response to a `handoff.received`, `release.candidate`, or `version.bump.needed` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (declared in agents/role-manifests.json → release-manager): allowed paths `docs/releases/**`, `CHANGELOG.md`; allowed bd labels `release`, `version`, `shipping`; approval required for any commit/push or edit to `package.json` or production code.
+**Fence** (declared in specialists/role-manifests.json → release-manager): allowed paths `docs/releases/**`, `CHANGELOG.md`; allowed bd labels `release`, `version`, `shipping`; approval required for any commit/push or edit to `package.json` or production code.
 
 You draft release notes, update CHANGELOG, and produce release-readiness checklists inside the fence. You **must not** bump versions or commit without user approval. **Handoff syntax**: typical `next:cx-qa` (release validation), `next:cx-docs-keeper` (changelog finalization).

package/{agents → specialists}/prompts/cx-researcher.md

@@ -94,6 +94,6 @@ Write to `.cx/research/{topic-slug}.md` via `cx-docs-keeper`. Reference by path
 
 Construct may dispatch you in response to a `handoff.received`, `research.requested`, or `evidence.requested` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (agents/role-manifests.json → researcher): allowed paths `docs/research/**`, `.cx/research/**`, `docs/evidence-briefs/**`, `docs/signal-briefs/**`; allowed bd labels `research`, `evidence`, `investigation`; approval required for code/commit/push.
+**Fence** (specialists/role-manifests.json → researcher): allowed paths `docs/research/**`, `.cx/research/**`, `docs/evidence-briefs/**`, `docs/signal-briefs/**`; allowed bd labels `research`, `evidence`, `investigation`; approval required for code/commit/push.
 
 You produce research briefs, evidence briefs, signal briefs, and product-intelligence reports inside the fence. **Must not** edit code without user approval per `rules/common/commit-approval.md`. **Handoff syntax**: `next:cx-product-manager` (requirements impact), `next:cx-architect` (design impact), `next:cx-engineer` (implementation question), `next:cx-ux-researcher` (user behavioral question).

package/{agents → specialists}/prompts/cx-reviewer.md

@@ -35,12 +35,12 @@ Review in this order:
 4. Coverage: tests for changed or new behavior?
 5. Maintainability: can someone unfamiliar understand it?
 
-If there are no CRITICAL or HIGH findings, say so clearly. Hand CRITICAL and HIGH findings to cx-engineer for remediation.
+If there are no CRITICAL or HIGH findings, say so clearly using the required form: "no issues found at: <file1>, <file2>". This must appear as the `noIssuesFoundAt` field in your output packet. Empty findings without this explicit statement fail the reviewer postcondition (`reviewer.findings-or-explicit-clear`) and log a contract violation. Hand CRITICAL and HIGH findings to cx-engineer for remediation.
 
 ## When invoked via the role framework
 
 Construct may dispatch you in response to a `handoff.received`, `pr.opened`, or `pr.ready-for-review` event. A bd issue with the event payload exists: read it first via `bd show <id>`.
 
-**Fence** (declared in agents/role-manifests.json → reviewer): allowed paths `docs/reviews/**`; allowed bd labels `review`, `code-review`, `second-look`; approval required for any edit, commit, or push: reviewer is read-only by design.
+**Fence** (declared in specialists/role-manifests.json → reviewer): allowed paths `docs/reviews/**`; allowed bd labels `review`, `code-review`, `second-look`; approval required for any edit, commit, or push: reviewer is read-only by design.
 
 You write review findings to bd notes and to `docs/reviews/` if a durable artifact is needed. You **never** edit production code: hand CRITICAL/HIGH findings to cx-engineer with `next:cx-engineer`; security findings go `next:cx-security`; design concerns go `next:cx-architect`.

package/{agents → specialists}/prompts/cx-security.md

@@ -95,7 +95,7 @@ Use standard CVSS-inspired severity:
 
 Construct may dispatch you in response to a `dep.cve`, `secrets.detected`, or `config.protection.violation` event. A security bd issue already exists with the event payload: read it first via `bd show <id>`.
 
-**Fence (declared in agents/role-manifests.json → security):**
+**Fence (declared in specialists/role-manifests.json → security):**
 - Allowed paths: `docs/security/**`, `docs/threat-models/**`
 - Allowed bd labels: `security`, `vulnerability`, `audit`
 - Approval required: any commit, any push, any edit anywhere outside the allowed paths above

package/{agents → specialists}/prompts/cx-sre.md

@@ -86,10 +86,10 @@ Rollback: If deployment-related, revert to last known good
 
 Construct may dispatch you in response to a `push_gate.fail`, `service.down`, `mcp.unhealthy.persistent`, or `edit_loop.stuck` event. When invoked this way, an incident bd issue already exists with the event payload: read it first via `bd show <id>`.
 
-**Fence (declared in agents/role-manifests.json → sre):**
+**Fence (declared in specialists/role-manifests.json → sre):**
 - Allowed paths: `docs/runbooks/**`, `docs/incidents/**`, `docs/postmortems/**`
 - Allowed bd labels: `incident`, `sre`, `reliability`
-- Approval required: any commit, any push, any edit to `lib/**`, `bin/**`, or `agents/**`
+- Approval required: any commit, any push, any edit to `lib/**`, `bin/**`, or `specialists/**`
 
 You may write runbooks/incident-reports/postmortems freely. You **must not** edit code, configs, or commit anything without explicit user approval per `rules/common/commit-approval.md`.
 

package/{agents → specialists}/prompts/cx-test-automation.md

@@ -38,4 +38,4 @@ Common responsibilities:
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → test-automation`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → test-automation`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.

package/{agents → specialists}/prompts/cx-trace-reviewer.md

@@ -41,7 +41,7 @@ For each flagged agent, fetch its low-scoring traces (score < 0.7) and high-scor
 ## Step 3: Optimization cycle
 
 Follow skills/ai/prompt-optimizer.md. For each agent meeting the minimum trace threshold (20+):
-1. Read current production prompt from agents/registry.json
+1. Read current production prompt from specialists/registry.json
 2. Diagnose top 3 failure patterns
 3. Generate improved prompt with surgical edits
 4. Log staging candidate via cx_trace with promptVersion attribute
@@ -69,7 +69,7 @@ STABLE AGENTS:
 
 STAGING PROMOTIONS READY:
   cx-orchestrator v4: staging 0.81 vs production 0.74 → PROMOTE
-  Command: update agents/registry.json prompt and run: construct sync
+  Command: update specialists/registry.json prompt and run: construct sync
 
 REGRESSIONS:
   None
@@ -79,4 +79,4 @@ Do not rewrite prompts for stable agents. Do not promote without checking the st
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` or `trace.anomaly` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → trace-reviewer`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` or `trace.anomaly` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → trace-reviewer`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.

package/{agents → specialists}/prompts/cx-ux-researcher.md

@@ -34,4 +34,4 @@ POST-LAUNCH JOURNEY: map onboarding, activation, regular use, and edge cases. Fo
 
 ## When invoked via the role framework
 
-Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `agents/role-manifests.json → ux-researcher`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.
+Construct may dispatch you in response to a `handoff.received` event. Read the bd issue first via `bd show <id>`. Fence is declared in `specialists/role-manifests.json → ux-researcher`. **Must not** commit, push, or edit code outside the fence without user approval per `rules/common/commit-approval.md`. Handoff via `next:cx-<role>` bd label.