contract-driven-delivery 2.0.0 → 2.0.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## [2.0.1] - 2026-04-30
+
+### Fixed
+
+- Clarified the agent ownership model in the public docs so read-only reviewers
+  and write-capable implementation agents have explicit, non-conflicting file
+  ownership rules.
+- Aligned bundled prompts so read-only agents emit an `Agent Log` YAML block
+  for main Claude to persist, while write-capable agents continue writing their
+  own artifacts and `agent-log/*.yml` files.
+- Synchronized package version metadata for the post-`2.0.0` publish path.
+
 ## [2.0.0] - 2026-04-30
 
 ### BREAKING: structured YAML for tasks and agent-log

package/README.md

@@ -99,6 +99,19 @@ or
 8. `cdd-kit gate <change-id>` runs automatically to confirm all artifacts are complete
 9. Claude reports a summary and the suggested git commit
 
+### Agent Ownership Model
+
+CDD uses two agent classes on purpose:
+
+- `change-classifier`, `contract-reviewer`, `qa-reviewer`, `visual-reviewer`, `dependency-security-reviewer`, `ui-ux-reviewer`, `repo-context-scanner`, and `spec-drift-auditor` are read-only. They return analysis, verdicts, or an `Agent Log` YAML block; main Claude writes the corresponding files.
+- `backend-engineer`, `frontend-engineer`, `e2e-resilience-engineer`, `monkey-test-engineer`, `stress-soak-engineer`, `ci-cd-gatekeeper`, `test-strategist`, and `spec-architect` are write-capable. They write their own implementation artifacts and their own `agent-log/*.yml`.
+
+This split is deliberate:
+
+- Review and audit agents stay read-only so they do not silently change the thing they are supposed to assess.
+- Implementation and planning agents write directly so large artifacts and code edits do not have to be relayed back through the main orchestrator, which reduces token waste and preserves clearer ownership.
+- `tasks.yml` remains owned by main Claude so task state changes stay centralized even when multiple agents contribute files.
+
 **You stay in control by:**
 - Reviewing the `change-classification.md` before implementation starts
 - Checking the `test-plan.md` to confirm the right test families are planned

package/assets/CODEX.template.md

@@ -18,12 +18,12 @@ Read `specs/changes/<change-id>/context-manifest.md` before using file-reading o
 - Read only paths allowed by the manifest or approved expansions.
 - Do not use broad repository search unless the manifest authorizes it.
 - If more context is needed, stop and write a Context Expansion Request in the manifest.
-- Record every file read through tools in the relevant `agent-log/*.md` under `- files-read:`.
+- Record every file read through tools in the relevant `agent-log/*.yml` under `files-read:`.
 
-Required `agent-log/*.md` format:
+Required `agent-log/*.yml` format:
 
-```md
-- files-read:
+```yaml
+files-read:
   - contracts/api/api-contract.md
   - src/server/routes/users.ts
 ```

package/assets/agents/change-classifier.md

@@ -225,7 +225,8 @@ Note: `archive.md` is created during change close-out, not at classification tim
 
 ## Machine-Verifiable Evidence
 
-After completing your task, write or append to
+After completing your task, end your response with an `Agent Log` YAML block
+for main Claude to write to
 `specs/changes/<change-id>/agent-log/<your-agent-name>.yml`. Required fields,
 field rules, and gate-enforcement behavior are defined once in
 `references/agent-log-protocol.md` — do not duplicate them in this prompt.

package/assets/agents/contract-reviewer.md

@@ -63,7 +63,8 @@ approved / changes-required
 
 ## Machine-Verifiable Evidence
 
-After completing your task, write or append to
+After completing your task, end your response with an `Agent Log` YAML block
+for main Claude to write to
 `specs/changes/<change-id>/agent-log/<your-agent-name>.yml`. Required fields,
 field rules, and gate-enforcement behavior are defined once in
 `references/agent-log-protocol.md` — do not duplicate them in this prompt.

package/assets/agents/dependency-security-reviewer.md

@@ -64,7 +64,8 @@ approved / changes-required / blocked
 
 ## Machine-Verifiable Evidence
 
-After completing your task, write or append to
+After completing your task, end your response with an `Agent Log` YAML block
+for main Claude to write to
 `specs/changes/<change-id>/agent-log/<your-agent-name>.yml`. Required fields,
 field rules, and gate-enforcement behavior are defined once in
 `references/agent-log-protocol.md` — do not duplicate them in this prompt.
@@ -74,4 +75,3 @@ field rules, and gate-enforcement behavior are defined once in
 - `cve-findings`: count + severity buckets
 - `license-issues`: list or "none"
 - `lockfile-changes`: list of files
-

package/assets/agents/qa-reviewer.md

@@ -75,7 +75,8 @@ approved / blocked / approved-with-risk
 
 ## Machine-Verifiable Evidence
 
-After completing your task, write or append to
+After completing your task, end your response with an `Agent Log` YAML block
+for main Claude to write to
 `specs/changes/<change-id>/agent-log/<your-agent-name>.yml`. Required fields,
 field rules, and gate-enforcement behavior are defined once in
 `references/agent-log-protocol.md` — do not duplicate them in this prompt.

package/assets/agents/repo-context-scanner.md

@@ -84,7 +84,8 @@ frontend / backend / fullstack / monorepo / library / tool
 
 ## Machine-Verifiable Evidence
 
-After completing your task, write or append to
+After completing your task, end your response with an `Agent Log` YAML block
+for main Claude to write to
 `specs/changes/<change-id>/agent-log/<your-agent-name>.yml`. Required fields,
 field rules, and gate-enforcement behavior are defined once in
 `references/agent-log-protocol.md` — do not duplicate them in this prompt.
@@ -93,4 +94,3 @@ field rules, and gate-enforcement behavior are defined once in
 - `profile-path`: `project-profile.generated.md`
 - `stack-detected`: from cdd-kit detect-stack
 - `surfaces-flagged`: list of missing standardization surfaces
-

package/assets/agents/spec-drift-auditor.md

@@ -52,7 +52,8 @@ By default, do NOT read `specs/changes/` history. Only read historical change re
 
 ## Machine-Verifiable Evidence
 
-After completing your task, write or append to
+After completing your task, end your response with an `Agent Log` YAML block
+for main Claude to write to
 `specs/changes/<change-id>/agent-log/<your-agent-name>.yml`. Required fields,
 field rules, and gate-enforcement behavior are defined once in
 `references/agent-log-protocol.md` — do not duplicate them in this prompt.
@@ -62,4 +63,3 @@ field rules, and gate-enforcement behavior are defined once in
 - `drift-items`: count + severity
 - `drift-summary-path`: `specs/audits/<YYYY-MM-DD>-drift-audit.md`
 - `next-audit-due`: ISO date
-

package/assets/agents/ui-ux-reviewer.md

@@ -51,7 +51,8 @@ approved / changes-required
 
 ## Machine-Verifiable Evidence
 
-After completing your task, write or append to
+After completing your task, end your response with an `Agent Log` YAML block
+for main Claude to write to
 `specs/changes/<change-id>/agent-log/<your-agent-name>.yml`. Required fields,
 field rules, and gate-enforcement behavior are defined once in
 `references/agent-log-protocol.md` — do not duplicate them in this prompt.
@@ -61,4 +62,3 @@ field rules, and gate-enforcement behavior are defined once in
 - `state-coverage`: list of `<screen>: empty/loading/error/success` matrix
 - `copy-issues`: count + severity
 - `accessibility-findings`: count + severity
-

package/assets/agents/visual-reviewer.md

@@ -53,7 +53,8 @@ approved / changes-required
 
 ## Machine-Verifiable Evidence
 
-After completing your task, write or append to
+After completing your task, end your response with an `Agent Log` YAML block
+for main Claude to write to
 `specs/changes/<change-id>/agent-log/<your-agent-name>.yml`. Required fields,
 field rules, and gate-enforcement behavior are defined once in
 `references/agent-log-protocol.md` — do not duplicate them in this prompt.
@@ -63,4 +64,3 @@ field rules, and gate-enforcement behavior are defined once in
 - `diff-percentage`: per-screen
 - `state-coverage`: matrix
 - `tokens-violated`: list of CSS contract violations or "none"
-

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "contract-driven-delivery",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "Contract-driven delivery kit for AI coding agents with deterministic context indexes, manifest-backed read-scope governance, and orchestrated contracts-first delivery.",
   "keywords": [
     "contract-driven",