cc-devflow 4.3.0 → 4.5.0

package/docs/examples/local-handoff/changes/REQ-003-audit-log-export/handoff/status.md

@@ -0,0 +1,29 @@
+# Status Report
+
+## Requirement
+
+- Change ID: `REQ-003`
+- Roadmap item: `RM-020`
+- Current state: verified and ready for `local-handoff`
+
+## What Is True Now
+
+- The admin audit summary panel can export the currently visible summary rows as CSV
+- The patch stayed inside the approved `tiny-design` boundary
+- Fresh targeted test and lint evidence both passed
+- `cc-check` returned `pass`
+
+## Ship Decision
+
+- Recommended mode: `local-handoff`
+- Why now: the work is verified, but remote push / PR creation is intentionally unavailable in this environment
+- Why not others:
+  - not `create-pr`: remote access is unavailable
+  - not `update-pr`: there is no existing PR to refresh
+  - not `post-merge-closeout`: the change is not merged yet
+
+## Docs And Follow-Up
+
+- README / release docs: unchanged; this is not a public release step
+- Backlog writeback: if admins request additional export formats, open a new roadmap item
+- Next entry point: use `resume-index.md` to pick up the branch when remote access becomes available

package/docs/examples/local-handoff/changes/REQ-003-audit-log-export/planning/design.md

@@ -0,0 +1,71 @@
+# DESIGN
+
+## Document Meta
+
+- Requirement version: `REQ-003.v1`
+- Design version: `design.v1`
+- CC-Plan skill version: `3.5.4`
+- Requirement ID: `REQ-003`
+- Design mode: `tiny-design`
+- Why this stays `tiny-design`: the patch adds one export action inside the existing admin audit UI without changing data contracts
+- Approval status: `approved`
+- Source roadmap item: `RM-020`
+- Source roadmap version: `roadmap.v3`
+
+## Source Handoff
+
+- Why now: admins need a lightweight way to take weekly activity summaries out of the UI
+- Inherited success signal: admins can download the summary without manual row copying
+- Inherited kill signal: if export requires a shared reporting pipeline, reopen planning
+- Inherited non-goals: no JSON export mode, no scheduled reporting
+- Upstream evidence: repeated internal admin requests during weekly reviews
+
+## Frozen Design Card
+
+- Change: add a `Download summary` action that exports the visible audit summary rows as CSV
+- Keep out: no multi-format export and no shared reporting backend
+- Touched files:
+  - `src/admin/AuditSummaryPanel.tsx`
+  - `src/admin/AuditSummaryPanel.test.tsx`
+- Contract changes: none; reuse the existing summary rows already shown in the panel
+- Key decisions that `cc-do` must not re-decide:
+  - export only what is already visible in the panel
+  - use CSV as the single output format
+  - keep the action inside the current admin panel
+- Upgrade trigger to `full-design`: if export needs background generation or new reporting contracts
+
+## Validation
+
+- Primary check: targeted panel test proves the export action is available and uses current summary rows
+- Secondary checks:
+  - existing audit summary rendering stays green
+  - lint passes for the touched panel
+- Evidence to collect:
+  - failing test before implementation
+  - passing test and lint after implementation
+
+## Main Risk
+
+- Risk: admins may soon ask for more export formats
+- Mitigation: treat JSON or scheduled exports as later roadmap items
+
+## Review Gate
+
+- Placeholder scan: pass
+- Consistency scan: pass
+- Scope scan: pass
+- Ambiguity scan: pass
+- Feasibility scan: pass
+- Final recommendation: approved as `tiny-design`
+
+## Approval
+
+- User approval status: approved
+- Deferred questions:
+  - if admins ask for machine-readable export next, open a separate requirement
+
+## First-Read Test
+
+- 一眼能看出这次为什么够小
+- 一眼能看出什么情况会逼它升级成 `full-design`
+- `cc-do` 看完不会继续追问“导出的字段从哪里来”

package/docs/examples/local-handoff/changes/REQ-003-audit-log-export/planning/task-manifest.json

@@ -0,0 +1,98 @@
+{
+  "changeId": "REQ-003",
+  "goal": "Add a local CSV export for the existing audit summary panel without introducing new reporting contracts.",
+  "createdAt": "2026-04-16T13:00:00.000Z",
+  "updatedAt": "2026-04-16T14:20:00.000Z",
+  "requirementId": "REQ-003",
+  "requirementVersion": "REQ-003.v1",
+  "currentTaskId": null,
+  "activePhase": null,
+  "tasks": [
+    {
+      "id": "T001",
+      "title": "[TEST] Add a failing test for the missing download action",
+      "type": "TEST",
+      "phase": 1,
+      "parallel": false,
+      "dependsOn": [],
+      "touches": ["audit-summary", "tests"],
+      "files": ["src/admin/AuditSummaryPanel.test.tsx"],
+      "run": ["npm test -- src/admin/AuditSummaryPanel.test.tsx"],
+      "checks": ["test fails before implementation"],
+      "acceptance": ["the missing download action is reproduced as a failing test"],
+      "verification": ["npm test -- src/admin/AuditSummaryPanel.test.tsx"],
+      "evidence": ["failing test output"],
+      "context": {
+        "readFiles": ["design.md", "tasks.md", "src/admin/AuditSummaryPanel.tsx"],
+        "commands": ["npm test -- src/admin/AuditSummaryPanel.test.tsx"],
+        "notes": ["stay inside the current audit summary panel"]
+      },
+      "reviews": { "spec": "pass", "code": "pass" },
+      "status": "passed",
+      "attempts": 1,
+      "maxRetries": 1
+    },
+    {
+      "id": "T002",
+      "title": "[IMPL] Add the download summary action",
+      "type": "IMPL",
+      "phase": 1,
+      "parallel": false,
+      "dependsOn": ["T001"],
+      "touches": ["audit-summary"],
+      "files": ["src/admin/AuditSummaryPanel.tsx"],
+      "run": ["npm test -- src/admin/AuditSummaryPanel.test.tsx"],
+      "checks": ["panel test passes"],
+      "acceptance": ["admins can trigger a CSV download from the existing summary panel"],
+      "verification": ["npm test -- src/admin/AuditSummaryPanel.test.tsx"],
+      "evidence": ["passing test output", "checkpoint summary"],
+      "context": {
+        "readFiles": ["design.md", "tasks.md", "src/admin/AuditSummaryPanel.test.tsx"],
+        "commands": ["npm test -- src/admin/AuditSummaryPanel.test.tsx"],
+        "notes": ["reuse visible summary rows as the export source"]
+      },
+      "reviews": { "spec": "pass", "code": "pass" },
+      "status": "passed",
+      "attempts": 1,
+      "maxRetries": 1
+    },
+    {
+      "id": "T003",
+      "title": "Run targeted checks and collect handoff evidence",
+      "type": "OTHER",
+      "phase": 2,
+      "parallel": false,
+      "dependsOn": ["T002"],
+      "touches": ["quality-gates"],
+      "files": ["src/admin/AuditSummaryPanel.tsx", "src/admin/AuditSummaryPanel.test.tsx"],
+      "run": [
+        "npm test -- src/admin/AuditSummaryPanel.test.tsx",
+        "npm run lint -- src/admin/AuditSummaryPanel.tsx"
+      ],
+      "checks": ["targeted tests pass", "lint passes"],
+      "acceptance": ["fresh verification evidence exists for local handoff"],
+      "verification": [
+        "npm test -- src/admin/AuditSummaryPanel.test.tsx",
+        "npm run lint -- src/admin/AuditSummaryPanel.tsx"
+      ],
+      "evidence": ["passing test output", "clean lint output"],
+      "context": {
+        "readFiles": ["tasks.md", "task-manifest.json"],
+        "commands": [
+          "npm test -- src/admin/AuditSummaryPanel.test.tsx",
+          "npm run lint -- src/admin/AuditSummaryPanel.tsx"
+        ],
+        "notes": ["remote push is intentionally out of scope for this example"]
+      },
+      "reviews": { "spec": "pass", "code": "pass" },
+      "status": "passed",
+      "attempts": 1,
+      "maxRetries": 1
+    }
+  ],
+  "metadata": {
+    "source": "tasks.md",
+    "generatedBy": "docs-example",
+    "planVersion": 1
+  }
+}

package/docs/examples/local-handoff/changes/REQ-003-audit-log-export/planning/tasks.md

@@ -0,0 +1,59 @@
+# TASKS
+
+## Plan Meta
+
+- Requirement version: `REQ-003.v1`
+- Design version: `design.v1`
+- CC-Plan skill version: `3.5.4`
+- Source roadmap item: `RM-020`
+- Source roadmap version: `roadmap.v3`
+
+## Execution Handoff
+
+- Canonical design: `design.md`
+- Execution mode: `single-path`
+- Frozen decisions:
+  - export only the visible audit summary rows
+  - CSV is the only format in this requirement
+- Read first:
+  - `design.md`
+  - `src/admin/AuditSummaryPanel.tsx`
+  - `src/admin/AuditSummaryPanel.test.tsx`
+- Commands to trust:
+  - `npm test -- src/admin/AuditSummaryPanel.test.tsx`
+  - `npm run lint -- src/admin/AuditSummaryPanel.tsx`
+- Do not re-decide:
+  - summary row source
+  - export format
+  - panel placement
+- Parallel boundaries: none
+
+## Phase 1: Foundation
+
+- [x] T001 [TEST] Add a failing test for the missing download action (dependsOn:none) `src/admin/AuditSummaryPanel.test.tsx`
+  Goal: 证明现在还没有可下载的 summary export。
+  Files: `src/admin/AuditSummaryPanel.test.tsx`
+  Read first: `design.md`, `src/admin/AuditSummaryPanel.tsx`
+  Verification: `npm test -- src/admin/AuditSummaryPanel.test.tsx`
+  Evidence: failing output
+  Ready when: 当前 audit summary test 已可运行
+
+- [x] T002 [IMPL] Add the download summary action (dependsOn:T001) `src/admin/AuditSummaryPanel.tsx`
+  Goal: 用最小实现让 summary export 真的可用。
+  Files: `src/admin/AuditSummaryPanel.tsx`
+  Read first: `design.md`, `src/admin/AuditSummaryPanel.test.tsx`
+  Verification: `npm test -- src/admin/AuditSummaryPanel.test.tsx`
+  Evidence: passing output + checkpoint
+  Ready when: T001 已见红
+
+## Phase 2: Verify
+
+- [x] T003 Run targeted checks and collect handoff evidence (dependsOn:T002) `audit summary quality gates`
+  Goal: 为 `cc-check` 和 `cc-act` 留下这次导出改动的真实证据。
+  Files: `src/admin/AuditSummaryPanel.tsx`, `src/admin/AuditSummaryPanel.test.tsx`
+  Read first: `tasks.md`, `task-manifest.json`
+  Verification:
+  - `npm test -- src/admin/AuditSummaryPanel.test.tsx`
+  - `npm run lint -- src/admin/AuditSummaryPanel.tsx`
+  Evidence: passing output + clean lint output
+  Ready when: T002 已完成

package/docs/examples/local-handoff/changes/REQ-003-audit-log-export/review/report-card.json

@@ -0,0 +1,44 @@
+{
+  "changeId": "REQ-003",
+  "verdict": "pass",
+  "overall": "pass",
+  "summary": "verdict=pass quick=2/2 strict=0/0 review=pass",
+  "quickGates": [
+    {
+      "name": "targeted-tests",
+      "status": "pass",
+      "command": "npm test -- src/admin/AuditSummaryPanel.test.tsx",
+      "summary": "audit summary panel targeted tests passed"
+    },
+    {
+      "name": "lint",
+      "status": "pass",
+      "command": "npm run lint -- src/admin/AuditSummaryPanel.tsx",
+      "summary": "lint passed for the touched panel file"
+    }
+  ],
+  "strictGates": [],
+  "review": {
+    "status": "pass",
+    "summary": "Task review proof and requirement-level diff review both passed",
+    "details": "The diff stayed inside the approved tiny-design scope and verification evidence is fresh.",
+    "taskReviews": {
+      "status": "pass",
+      "required": true,
+      "summary": "All completed tasks carry spec/code proof",
+      "reviewers": [],
+      "findings": []
+    },
+    "diffReview": {
+      "status": "pass",
+      "required": false,
+      "summary": "No blocking requirement-level findings",
+      "reviewers": [],
+      "findings": []
+    },
+    "findings": []
+  },
+  "blockingFindings": [],
+  "reroute": "none",
+  "timestamp": "2026-04-16T14:30:00.000Z"
+}

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.2",
+    "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.2`
+- 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.2`, `cc-plan@3.5.4`, `cc-do@1.5.2`, `cc-check@1.8.2`, `cc-act@1.6.2`
+
+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.2`
+- 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