cc-devflow 4.3.0 → 4.4.1

package/docs/examples/local-handoff/roadmap-tracking.json

@@ -0,0 +1,48 @@
+{
+  "version": 2,
+  "lastSyncedAt": "2026-04-19",
+  "backlogMeta": {
+    "roadmapVersion": "roadmap.v2",
+    "skillVersion": "4.3.1",
+    "currentFocusStage": "Stage 2"
+  },
+  "dependencyHandoff": {
+    "serialSpine": "RM-020",
+    "parallelReadyNextWave": "-",
+    "notesOnBlockers": "export work stays local-only until the next maintainer has remote access"
+  },
+  "items": [
+    {
+      "rmId": "RM-020",
+      "item": "Add an audit-log export summary download",
+      "stage": "Stage 2",
+      "priority": "P1",
+      "primaryCapability": "cap-audit-log-export",
+      "secondaryCapabilities": [],
+      "expectedSpecDelta": "codify local export summary truth",
+      "dependsOn": [],
+      "status": "Local handoff",
+      "req": "REQ-003",
+      "progress": "100%",
+      "backlog": {
+        "capabilityGap": "admins can export raw audit data but not a compact summary for review",
+        "evidence": "support escalations keep asking for a lightweight summary bundle",
+        "parallelWith": [],
+        "unknowns": "csv-only or csv-plus-markdown summary",
+        "nextDecision": "resume from local handoff once remote access returns",
+        "ready": true,
+        "whyNow": "the implementation and proof already exist, only the landing path is deferred",
+        "successSignal": "admins can download a concise audit summary without manual spreadsheet cleanup",
+        "entryConstraints": "stay local-only and avoid remote automation",
+        "openRisks": "handoff may age if schema changes before the next maintainer resumes",
+        "firstPlanningQuestion": "does the summary format need another review before remote landing?",
+        "requiredContextToLoad": "admin export screen, generated summary fixture, local handoff notes",
+        "whyReadyNow": "the requirement is already proven and only needs a clean resume point",
+        "parked": false,
+        "parkedReason": "",
+        "triggerToReopen": "",
+        "missingEvidence": ""
+      }
+    }
+  ]
+}

package/docs/examples/pdca-loop/BACKLOG.md

@@ -0,0 +1,46 @@
+# BACKLOG
+
+## Backlog Meta
+
+- Roadmap version: `roadmap.v1`
+- Skill version: `4.3.1`
+- Last synced: `2026-04-19`
+- Current focus stage: `Stage 1`
+- Tracking source: `roadmap-tracking.json`
+
+## Queue
+
+| RM-ID | Title | Source Stage | Priority | Primary Capability | Secondary Capabilities | Capability Gap | Expected Spec Delta | Evidence | Depends On | Parallel With | Unknowns | Next Decision | Ready |
+|------|------|------|------|------|------|------|------|------|------|------|------|------|------|
+| RM-001 | Add one-click copy action to the share dialog | Stage 1 | P1 | cap-invite-links | - | share dialog exposes invite URL but not direct copy action | tighten invite-link copy truth | repeated support friction | - | - | copied-state feedback shape | freeze tiny design and execute | Yes |
+| RM-002 | Add copied-state feedback to the share dialog | Stage 1 | P2 | cap-invite-links | - | invite links lack durable copied-state feedback after action completion | extend invite-link feedback truth | likely useful after RM-001 | RM-001 | - | toast vs inline state | decide after first patch ships | No |
+
+## Dependency Handoff
+
+- Serial spine: RM-001 -> RM-002
+- Parallel-ready next wave: none until RM-001 proves the copy action shape
+- Notes on blockers: RM-002 should reuse the final interaction contract from RM-001, not race it
+
+## Ready For Req-Plan
+
+- RM-001:
+  - Primary Capability: `cap-invite-links`
+  - Secondary Capabilities: `-`
+  - Why now: it removes the first visible collaboration friction in the beta flow
+  - Success signal: users can copy the invite link with one click
+  - Entry constraints: no backend changes, no share dialog redesign
+  - Capability gap: share dialog exposes invite URL but not direct copy action
+  - Expected spec delta: tighten invite-link copy truth
+  - Open risks: clipboard failure copy may still need follow-up UX
+  - First planning question: can this stay a tiny-design patch without changing contracts?
+  - Required context to load: current share dialog, current invite URL source, existing tests
+  - Depends On: `-`
+  - Parallel With: `-`
+  - Why this is ready now: the ask is narrow, the evidence is real, and the dependency surface is already known
+
+## Parked
+
+- RM-004:
+  - Reason parked: collaboration analytics is premature before Stage 1 and 2 prove usage
+  - Trigger to reopen: repeated invite usage after beta activation
+  - Missing evidence: stable collaboration volume

package/docs/examples/pdca-loop/README.md

@@ -0,0 +1,58 @@
+# End-to-End PDCA Example
+
+## Example Meta
+
+- Example version: `1.0.0`
+- Last reviewed: `2026-04-17`
+- Bound skills: `cc-roadmap@4.3.1`, `cc-plan@3.5.3`, `cc-do@1.5.1`, `cc-check@1.8.1`, `cc-act@1.6.1`
+
+This folder shows one minimal but complete `cc-roadmap -> cc-plan -> cc-do -> cc-check -> cc-act` loop.
+
+The example is intentionally small:
+
+- product context is fake
+- requirement scope is real enough to feel concrete
+- the chosen ship mode is `create-pr`
+- optional artifacts such as `release-note.md` are intentionally omitted when the mode does not require them
+
+## Scenario
+
+The fictional product is a small team workspace app.
+
+The immediate pain is simple: users can open the share dialog and see the invite URL, but they cannot copy it with one click.
+
+The sample requirement is:
+
+- `RM-001`: add a `Copy invite link` button to the existing share dialog
+
+## Artifact Map
+
+- `ROADMAP.md`: what `cc-roadmap` decided and why this item is first
+- `roadmap-tracking.json`: machine-readable roadmap/backlog truth that renders `ROADMAP.md` and `BACKLOG.md`
+- `BACKLOG.md`: capability-aware handoff that makes `RM-001` ready for `cc-plan`
+- `changes/REQ-001-copy-invite-link/planning/design.md`: approved tiny design
+- `changes/REQ-001-copy-invite-link/planning/tasks.md`: executable task handoff
+- `changes/REQ-001-copy-invite-link/planning/task-manifest.json`: machine-readable execution truth
+- `changes/REQ-001-copy-invite-link/review/report-card.json`: `cc-check` proof and verdict
+- `changes/REQ-001-copy-invite-link/handoff/pr-brief.md`: ship-ready PR handoff
+
+## Why There Is No `release-note.md`
+
+This sample chooses `create-pr`.
+
+That mode needs:
+
+- `pr-brief.md`
+- synced docs if behavior changed
+
+It does **not** need a public release note yet, so the example intentionally stops there.
+
+## What To Look For
+
+When reading the sample, check whether you can answer these in under a minute:
+
+1. Why is `RM-001` the next roadmap item?
+2. Why does the requirement stay `tiny-design` instead of `full-design`?
+3. Which task proved the missing behavior first?
+4. What fresh evidence let `cc-check` say `pass`?
+5. Why does `cc-act` choose `create-pr` and omit `release-note.md`?

package/docs/examples/pdca-loop/ROADMAP.md

@@ -0,0 +1,133 @@
+# ROADMAP
+
+## Roadmap Meta
+
+- Roadmap version: `roadmap.v1`
+- Skill version: `4.3.1`
+- Status: `active`
+- Last updated: `2026-04-15`
+- Owner / decider: `product-owner`
+- Current focus stage: `Stage 1`
+- Confidence: `medium`
+- Supersedes roadmap version: `none`
+
+## Context Snapshot
+
+- Product / repo: `workspace-lite`
+- Project stage: early beta for small internal teams
+- Users: team leads sharing a workspace with 2-10 collaborators
+- Pain: invite flow exists, but sharing still feels manual
+- Existing workaround: users highlight the invite URL field and copy it by hand
+- Strongest demand evidence: repeated support notes saying "copying the link feels broken"
+- Why now: sharing friction blocks the first successful invite loop
+- Distribution path: direct beta onboarding
+- Deadline / forcing function: next beta reset on `2026-04-22`
+- Team / capacity: one product-minded engineer
+- Hard constraints: no API changes, no invite permission redesign
+- Adoption / trust bottleneck: users hesitate when a basic collaboration action feels unfinished
+- Known unknowns: whether users also need a copied-state confirmation toast
+
+## Evidence Ledger
+
+| Signal | Evidence | Confidence | Source | Why it matters |
+|--------|----------|------------|--------|----------------|
+| Demand | Beta users ask how to copy the invite URL | High | support notes | Sharing is a real bottleneck |
+| Timing | Beta reset is one week away | High | launch plan | The fix must land this cycle |
+| Feasibility | Existing dialog already renders the URL and clipboard API is available | High | current UI behavior | This is a tiny patch, not a redesign |
+| Distribution | Successful sharing unlocks more beta seats | Med | product notes | A smoother invite loop increases activation |
+
+## Route Options
+
+| Shape | Why this could work | Why this may fail | Decision |
+|-------|---------------------|-------------------|----------|
+| wedge-first | Remove the sharpest sharing pain now | May leave deeper invite roles for later | Recommended |
+| platform-first | Rebuild all sharing plumbing before polish | Too large for the current window | Rejected |
+| rescue-first | Focus only on onboarding docs and support | Does not fix the broken-feeling UI | Rejected |
+
+## Recommended Route
+
+- Recommendation: `wedge-first`
+- Why this route wins now: the strongest evidence is user friction in the current share path, not missing infrastructure
+- Why the rejected routes lose now: both alternatives spend time away from the first visible activation bottleneck
+- First signal to watch: users can copy the invite link without asking support
+- Kill signal / stop condition: if the fix requires API or permission changes, reopen planning at a larger scope
+
+## Product Thesis
+
+- Users: small teams inviting collaborators during setup
+- Pain: manual copying makes the share flow feel unfinished
+- Why now: this friction sits directly on the first collaboration moment
+- Strategic wedge: polish the existing share path before adding broader collaboration features
+- Product promise: basic collaboration should feel one click away
+- What we refuse to build yet: invite roles, expiration controls, share analytics
+- 6-12 month pull: grow from frictionless invite into stronger collaboration controls
+
+## Stage Overview
+
+| Stage | Goal | Why now | Dependencies | Exit signal | Kill signal | Non-goals |
+|-------|------|---------|--------------|-------------|-------------|-----------|
+| Stage 1 | Remove first-share friction | Beta activation is blocked here | Existing share dialog | Users can copy the link in one click | Requires backend changes | Permission redesign |
+| Stage 2 | Add safer invite controls | Only after the basic share action feels complete | Stable share interaction | Invite options are trusted | Stage 1 still confuses users | Analytics |
+| Stage 3 | Measure collaboration adoption | Only after sharing is reliable | Stage 1 and 2 complete | Teams repeatedly invite collaborators | Usage remains too low to justify analytics | Growth experiments outside collaboration |
+
+## Stage Detail
+
+### Stage 1
+
+- Goal: make the first invite flow feel complete
+- Users unlocked: team leads onboarding collaborators
+- Why this stage exists: collaboration cannot feel credible while copying the invite link is awkward
+- Entry assumptions: existing invite link source remains stable
+- Deliverables: one-click copy action, user feedback, targeted verification
+- Dependencies: current share dialog and invite URL field
+- Win condition: a user can click once and get confirmation
+- Key risks: clipboard failure path may be unclear
+- Kill signal: patch expands into cross-module share redesign
+- What must stay out: new backend contract, new invite settings
+- Candidate roadmap items: `RM-001`, `RM-002`
+
+### Stage 2
+
+- Goal: make invite controls safer
+- Users unlocked: team leads managing collaborator access
+- Why this stage exists: once sharing works, control and trust become the next bottleneck
+- Entry assumptions: Stage 1 removed the basic friction
+- Deliverables: role-aware invite options
+- Dependencies: stable Stage 1 behavior
+- Win condition: users no longer need manual role guidance
+- Key risks: scope grows into auth redesign
+- Kill signal: collaboration usage stays too low
+- What must stay out: analytics dashboard
+- Candidate roadmap items: `RM-003`
+
+### Stage 3
+
+- Goal: measure and improve collaboration adoption
+- Users unlocked: operators deciding where to invest next
+- Why this stage exists: instrumentation matters only after the share loop is credible
+- Entry assumptions: Stages 1 and 2 hold steady
+- Deliverables: collaboration funnel metrics
+- Dependencies: repeated real usage
+- Win condition: roadmap decisions use measured invite data
+- Key risks: false precision with too little traffic
+- Kill signal: beta usage remains tiny
+- What must stay out: unrelated acquisition work
+- Candidate roadmap items: `RM-004`
+
+## Decision Notes
+
+- Rejected path A: rebuild sharing infrastructure first
+- Rejected path B: rely on docs and support instead of fixing the UI
+- Open assumptions to verify next: whether a copied-state message is enough or a toast is needed
+- What changed in this version: narrowed Stage 1 to the smallest visible sharing fix
+
+## Implementation Tracking
+- Tracking source: `roadmap-tracking.json`
+
+<!-- roadmap-tracking:start -->
+| RM-ID | Item | Stage | Priority | Primary Capability | Secondary Capabilities | Expected Spec Delta | Depends On | Status | REQ | Progress |
+|------|------|------|------|------|------|------|------|------|------|------|
+| RM-001 | Add one-click copy action to the share dialog | Stage 1 | P1 | cap-invite-links | - | tighten invite-link copy truth | - | In review | REQ-001 | 100% |
+| RM-002 | Add copied-state feedback to the share dialog | Stage 1 | P2 | cap-invite-links | - | extend invite-link feedback truth | RM-001 | Planned | - | 0% |
+| RM-004 | Collaboration analytics follow-up | - | - | - | - | - | - | - | - | - |
+<!-- roadmap-tracking:end -->

package/docs/examples/pdca-loop/changes/REQ-001-copy-invite-link/handoff/pr-brief.md

@@ -0,0 +1,72 @@
+# PR Brief
+
+## Decision
+
+- Recommended mode: `create-pr`
+- Why now: verified work is ready for reviewer handoff and there is no existing PR to update
+- Why not others: `update-pr` has nothing to refresh, `local-handoff` would delay an already verified change, and `post-merge-closeout` only applies after merge
+
+## Requirement
+
+- `RM-001` / `REQ-001`: add a one-click copy action to the existing share dialog
+
+## Ship Mode
+
+- `create-pr`
+
+## Branch Context
+
+- Current branch: `feature/copy-invite-link`
+- Base branch: `main`
+- PR / MR: not created yet
+
+## Summary
+
+- removes a small but visible sharing friction in the beta flow
+- keeps the patch inside the approved `tiny-design` boundary
+- ships with fresh test, lint, and review proof
+
+## What Changed
+
+- adds a `Copy invite link` action beside the existing invite URL
+- reuses the current invite link source of truth
+- adds copied-state confirmation without redesigning the dialog
+
+## Verification Evidence
+
+- `report-card.json` verdict: `pass`
+- Fresh evidence:
+  - `npm test -- src/features/share/ShareDialog.test.tsx`
+  - `npm run lint -- src/features/share/ShareDialog.tsx`
+
+## Documentation Sync
+
+- `CLAUDE.md`: unchanged
+- `README.md`: unchanged
+- `release-note.md`: intentionally omitted for this mode
+- `resume-index.md`: not needed because the change is ready for PR handoff
+
+## Minimum Landing Pack
+
+- Required for this mode:
+  - `pr-brief.md`
+  - fresh `report-card.json`
+- Intentionally omitted:
+  - `release-note.md`
+  - `resume-index.md`
+
+## How To Verify
+
+- open the share dialog
+- confirm the invite URL still matches the current source of truth
+- click `Copy invite link`
+- confirm the copied-state feedback appears
+- re-run the targeted test and lint commands above
+
+## Follow-Ups
+
+- if users still miss the feedback, lift `RM-002` into the next requirement
+
+## Risks
+
+- copied-state feedback may still be too subtle for some users, but the current patch keeps that trade-off isolated

package/docs/examples/pdca-loop/changes/REQ-001-copy-invite-link/handoff/status.md

@@ -0,0 +1,29 @@
+# Status Report
+
+## Requirement
+
+- Change ID: `REQ-001`
+- Roadmap item: `RM-001`
+- Current state: verified and ready to ship as `create-pr`
+
+## What Is True Now
+
+- The share dialog exposes a one-click copy action for the existing invite URL
+- The patch stayed inside the approved `tiny-design` boundary
+- Fresh targeted test and lint evidence both passed
+- Review proof is present, so `cc-check` returned `pass`
+
+## Ship Decision
+
+- Recommended mode: `create-pr`
+- Why now: the work is verified, the branch is assumed to be a feature branch, and no open PR exists yet
+- Why not others:
+  - not `update-pr`: there is no existing PR to refresh
+  - not `local-handoff`: the work is ready to move forward
+  - not `post-merge-closeout`: the change is not merged yet
+
+## Docs And Follow-Up
+
+- README / release docs: no public user-facing release note yet
+- Backlog writeback: keep `RM-002` parked as the next UX refinement if support friction remains
+- Next entry point: create the PR using `pr-brief.md` as the truth source

package/docs/examples/pdca-loop/changes/REQ-001-copy-invite-link/planning/design.md

@@ -0,0 +1,72 @@
+# DESIGN
+
+## Document Meta
+
+- Requirement version: `REQ-001.v1`
+- Design version: `design.v1`
+- CC-Plan skill version: `3.5.3`
+- Requirement ID: `REQ-001`
+- Design mode: `tiny-design`
+- Why this stays `tiny-design`: the patch is limited to an existing dialog and test file, with no API or data model changes
+- Approval status: `approved`
+- Source roadmap item: `RM-001`
+- Source roadmap version: `roadmap.v1`
+
+## Source Handoff
+
+- Why now: Stage 1 needs the smallest possible share-flow win
+- Inherited success signal: a user can copy the invite link with one click
+- Inherited kill signal: if the patch requires backend or permission changes, reopen planning
+- Inherited non-goals: no invite role controls, no analytics, no dialog redesign
+- Upstream evidence: repeated support notes and observed manual copying
+
+## Frozen Design Card
+
+- Change: add a `Copy invite link` button beside the existing read-only invite URL in the share dialog
+- Keep out: no new invite generation flow and no fallback redesign for unsupported browsers
+- Touched files:
+  - `src/features/share/ShareDialog.tsx`
+  - `src/features/share/ShareDialog.test.tsx`
+- Contract changes: none; reuse the existing invite link source and existing dialog props
+- Key decisions that `cc-do` must not re-decide:
+  - use `navigator.clipboard.writeText`
+  - keep the current invite URL source of truth
+  - show a lightweight copied-state confirmation inside the current dialog
+- Upgrade trigger to `full-design`: if clipboard support requires new platform fallbacks, or if the patch spills into shared share-service contracts
+
+## Validation
+
+- Primary check: targeted dialog test proves the button renders and copies the current invite URL
+- Secondary checks:
+  - existing share dialog tests remain green
+  - lint stays green for the touched files
+- Evidence to collect:
+  - failing test before implementation
+  - passing targeted test after implementation
+  - fresh gate output for `cc-check`
+
+## Main Risk
+
+- Risk: copied-state feedback may be too subtle for users
+- Mitigation: keep the first patch minimal and log a follow-up roadmap item if support friction remains
+
+## Review Gate
+
+- Placeholder scan: pass
+- Consistency scan: pass; scope, files, and validation all point to the same tiny patch
+- Scope scan: pass; no backend, no permission work
+- Ambiguity scan: pass; execution does not need to re-decide button placement or clipboard source
+- Feasibility scan: pass; existing dialog and tests already cover the target surface
+- Final recommendation: approved as `tiny-design`
+
+## Approval
+
+- User approval status: approved
+- Deferred questions:
+  - if copied-state feedback still feels weak, open a separate requirement for richer UX
+
+## First-Read Test
+
+- This is clearly small because it stays inside one UI surface and one test surface
+- The upgrade path is explicit: any contract or fallback work forces `full-design`
+- `cc-do` should not need to ask where the URL comes from or how the copy action is triggered

package/docs/examples/pdca-loop/changes/REQ-001-copy-invite-link/planning/task-manifest.json

@@ -0,0 +1,201 @@
+{
+  "changeId": "REQ-001",
+  "goal": "Add a one-click copy action to the existing share dialog without changing backend contracts.",
+  "createdAt": "2026-04-15T10:00:00.000Z",
+  "updatedAt": "2026-04-15T11:10:00.000Z",
+  "status": "verified",
+  "requirementId": "REQ-001",
+  "requirementVersion": "REQ-001.v1",
+  "sourceRoadmap": {
+    "itemId": "RM-001",
+    "roadmapVersion": "roadmap.v1",
+    "roadmapSkillVersion": "4.3.1",
+    "sourceStage": "Stage 1",
+    "successSignal": "Users can copy the invite link with one click",
+    "killSignal": "The patch requires backend or permission changes",
+    "dependencies": [
+      "Existing share dialog stays intact"
+    ],
+    "nonGoals": [
+      "No invite role redesign",
+      "No share analytics"
+    ]
+  },
+  "planningMeta": {
+    "reqPlanSkillVersion": "3.5.3",
+    "designVersion": "design.v1",
+    "approvedAt": "2026-04-15T10:05:00.000Z",
+    "approvedBy": "user",
+    "basedOnOption": "Tiny design card"
+  },
+  "currentTaskId": null,
+  "activePhase": null,
+  "tasks": [
+    {
+      "id": "T001",
+      "title": "[TEST] Add a failing dialog test for the missing copy action",
+      "type": "TEST",
+      "phase": 1,
+      "parallel": false,
+      "dependsOn": [],
+      "touches": [
+        "share-dialog",
+        "tests"
+      ],
+      "files": [
+        "src/features/share/ShareDialog.test.tsx"
+      ],
+      "run": [
+        "npm test -- src/features/share/ShareDialog.test.tsx"
+      ],
+      "checks": [
+        "test fails before implementation"
+      ],
+      "acceptance": [
+        "The missing copy action is reproduced as a failing test"
+      ],
+      "verification": [
+        "npm test -- src/features/share/ShareDialog.test.tsx"
+      ],
+      "evidence": [
+        "Failing test output"
+      ],
+      "context": {
+        "readFiles": [
+          "design.md",
+          "tasks.md",
+          "src/features/share/ShareDialog.tsx"
+        ],
+        "commands": [
+          "npm test -- src/features/share/ShareDialog.test.tsx"
+        ],
+        "notes": [
+          "Do not change share-service contracts in this task"
+        ]
+      },
+      "reviews": {
+        "spec": "pass",
+        "code": "pass"
+      },
+      "status": "passed",
+      "attempts": 1,
+      "maxRetries": 1
+    },
+    {
+      "id": "T002",
+      "title": "[IMPL] Add the copy button and copied-state confirmation",
+      "type": "IMPL",
+      "phase": 1,
+      "parallel": false,
+      "dependsOn": [
+        "T001"
+      ],
+      "touches": [
+        "share-dialog"
+      ],
+      "files": [
+        "src/features/share/ShareDialog.tsx"
+      ],
+      "run": [
+        "npm test -- src/features/share/ShareDialog.test.tsx"
+      ],
+      "checks": [
+        "dialog test passes after implementation"
+      ],
+      "acceptance": [
+        "The dialog exposes a copy button and confirms the copied state"
+      ],
+      "verification": [
+        "npm test -- src/features/share/ShareDialog.test.tsx"
+      ],
+      "evidence": [
+        "Passing targeted test output",
+        "Checkpoint summary"
+      ],
+      "context": {
+        "readFiles": [
+          "design.md",
+          "tasks.md",
+          "src/features/share/ShareDialog.test.tsx"
+        ],
+        "commands": [
+          "npm test -- src/features/share/ShareDialog.test.tsx"
+        ],
+        "notes": [
+          "Keep the patch inside the existing dialog"
+        ]
+      },
+      "reviews": {
+        "spec": "pass",
+        "code": "pass"
+      },
+      "status": "passed",
+      "attempts": 1,
+      "maxRetries": 1
+    },
+    {
+      "id": "T003",
+      "title": "Run targeted checks and collect fresh evidence",
+      "type": "OTHER",
+      "phase": 2,
+      "parallel": false,
+      "dependsOn": [
+        "T002"
+      ],
+      "touches": [
+        "quality-gates"
+      ],
+      "files": [
+        "src/features/share/ShareDialog.tsx",
+        "src/features/share/ShareDialog.test.tsx"
+      ],
+      "run": [
+        "npm test -- src/features/share/ShareDialog.test.tsx",
+        "npm run lint -- src/features/share/ShareDialog.tsx"
+      ],
+      "checks": [
+        "targeted test passes",
+        "lint passes"
+      ],
+      "acceptance": [
+        "Fresh verification evidence is ready for cc-check"
+      ],
+      "verification": [
+        "npm test -- src/features/share/ShareDialog.test.tsx",
+        "npm run lint -- src/features/share/ShareDialog.tsx"
+      ],
+      "evidence": [
+        "Passing targeted test output",
+        "Clean lint output"
+      ],
+      "context": {
+        "readFiles": [
+          "tasks.md",
+          "task-manifest.json"
+        ],
+        "commands": [
+          "npm test -- src/features/share/ShareDialog.test.tsx",
+          "npm run lint -- src/features/share/ShareDialog.tsx"
+        ],
+        "notes": [
+          "Collect only fresh evidence from this run"
+        ]
+      },
+      "reviews": {
+        "spec": "pass",
+        "code": "pass"
+      },
+      "status": "passed",
+      "attempts": 1,
+      "maxRetries": 1
+    }
+  ],
+  "metadata": {
+    "source": "tasks.md",
+    "generatedBy": "docs-example",
+    "planVersion": 1
+  },
+  "deferredQuestions": [
+    "If users still miss the copied-state confirmation, open RM-002 for richer feedback."
+  ]
+}