refactor(board): replace epics+milestone with scope field

Simplify story frontmatter schema by replacing the `epics` array and
`milestone` field with a single `scope` field that uses the format
`epic/milestone` or just `epic` for stories without a milestone.

This change:
- Migrates all 207 stories to use the new scope field
- Updates CONVENTIONS.md with the new schema
- Updates the story template
- Adds Phase 2 design to artifact pipeline for story-scoped verification

The scope field provides a cleaner hierarchy that matches the board
structure (Epic > Milestone > Story) and enables story-specific
verification reports organized by scope.

Author: rupurt

docs/board/CONVENTIONS.md

@@ -105,31 +105,37 @@ Stories use YAML frontmatter for metadata:
 
 ```yaml
 ---
-id: m26-feat-01-eventlog
-title: EventLog Assessment Storage
+id: FEAT0109
+title: Board generator grouped layout
 type: feat
 status: in-progress
 priority: high
-epics: [core]
+scope: coherence-verification/01-artifact-pipeline
 depends: []
 estimate: 2h
-created: 2025-01-07
-updated: 2025-01-07
+created: 2026-01-17
 ---
 ```
 
 | Field | Required | Description |
 |-------|----------|-------------|
-| `id` | Yes | Unique identifier (prefix with milestone: `m26-feat-01`) |
+| `id` | Yes | Unique identifier (`TYPE` + 4-digit number: `FEAT0109`, `BUG0001`) |
 | `title` | Yes | Human-readable title |
 | `type` | Yes | `feat`, `bug`, `chore`, `refactor` |
 | `status` | Yes | `backlog`, `in-progress`, `done`, `icebox` |
 | `priority` | No | `low`, `medium`, `high`, `critical` |
-| `epics` | No | List of epic IDs this story belongs to |
+| `scope` | No | Epic and milestone path: `epic-name/milestone-id` or just `epic-name` |
 | `depends` | No | List of story IDs that must complete first |
 | `estimate` | No | Time estimate (e.g., `2h`, `1d`) |
 | `created` | Yes | Creation date |
-| `updated` | Yes | Last update date |
+
+**Scope values:**
+
+| Value | Meaning |
+|-------|---------|
+| `epic/milestone` | Story belongs to epic and milestone (e.g., `coherence-verification/01-artifact-pipeline`) |
+| `epic` | Story belongs to epic only, no milestone (e.g., `core`) |
+| (empty) | Ad-hoc story, not associated with any epic |
 
 ### Story Naming
 
@@ -493,16 +499,15 @@ The `implementation.md` serves as the entry point and index for the milestone's
 
 ```markdown
 ---
-id: m26-feat-01-types
+id: FEAT0042
 title: Core Type Definitions
 type: feat
 status: backlog
 priority: high
-epics: [core]
+scope: core/01-event-sourcing
 depends: []
 estimate: 2h
-created: 2024-01-15
-updated: 2024-01-15
+created: 2026-01-15
 ---
 
 # Core Type Definitions

docs/board/epics/coherence-verification/milestones/01-verification-artifact-pipeline/README.md

@@ -16,19 +16,28 @@ Developers can run `just verify all` to capture screenshots, interaction sequenc
 
 ## Done Criteria
 
+### Phase 1: Artifact Capture
 - [x] `just verify snapshots` captures key screen PNGs
 - [x] `just verify checkpoints` captures interaction sequence PNGs
 - [x] `just verify videos` records CLI (VHS) + Web (Playwright) and stitches with ffmpeg
 - [x] `just verify report` generates `verification/report.md`
-- [ ] Report links artifacts to story acceptance criteria (planned for phase 2)
+
+### Phase 2: Story-Scoped Verification
+- [x] Story frontmatter uses `scope` field (replaces `epics` + `milestone`)
+- [x] All stories migrated to new schema
+- [x] CONVENTIONS.md documents new schema
+- [ ] Verification annotations in acceptance criteria (`<!-- verify: type:name -->`)
+- [ ] `just verify story <ID>` captures artifacts for a story
+- [ ] `just verify story-report <ID>` generates story-specific report
+- [ ] Reports committed at `verification/reports/<scope>/<id>.md`
 
 ## Design
 
 See [design.md](design.md) for architecture and implementation details.
 
 ## Work Items
 
-> Work tracked inline during implementation (no separate story files).
+### Phase 1 (Complete)
 
 | Item | Status |
 |------|--------|
@@ -37,3 +46,15 @@ See [design.md](design.md) for architecture and implementation details.
 | Implement checkpoints.spec.ts | done |
 | Implement videos.spec.ts with CLI+Web stitching | done |
 | Document verification commands in CLAUDE.md | done |
+
+### Phase 2 (In Progress)
+
+| Item | Status |
+|------|--------|
+| Design story-scoped verification | done |
+| Update story frontmatter schema (scope field) | done |
+| Migrate all stories to new schema | done |
+| Update CONVENTIONS.md | done |
+| Implement verification annotation parsing | pending |
+| Implement `just verify story` command | pending |
+| Update .gitignore for reports directory | pending |

docs/board/epics/coherence-verification/milestones/01-verification-artifact-pipeline/design.md

@@ -292,3 +292,158 @@ See [verification/report.md](verification/report.md) for full details.
 - [x] `verification/checkpoints.json` definition file
 - [x] Report generation script
 - [x] Documentation in CLAUDE.md
+
+---
+
+# Phase 2: Story-Scoped Verification
+
+> Link artifacts to story acceptance criteria to complete the coherence loop.
+
+## Overview
+
+Phase 1 captures artifacts globally. Phase 2 adds story-scoped verification where each story's acceptance criteria can reference specific artifacts, and the report shows coverage.
+
+### Key Decisions
+
+| Decision | Choice | Rationale |
+|----------|--------|-----------|
+| **Verification location** | Story file (inline) | Single source of truth; criteria and verification together |
+| **Scope field** | Single `scope` replacing `epics` + `milestone` | Simpler hierarchy; one field for report path |
+| **Report per story** | `reports/<scope>/<id>.md` | Organized by epic/milestone; matches board hierarchy |
+
+---
+
+## Story Frontmatter Schema
+
+Replace `epics` array and `milestone` field with single `scope` field:
+
+```yaml
+---
+id: FEAT0109
+title: Board generator grouped layout
+type: feat
+status: done
+priority: high
+scope: coherence-verification/01-artifact-pipeline  # epic/milestone or just epic
+depends: []
+estimate: 2h
+created: 2026-01-17
+---
+```
+
+**Scope values:**
+| Value | Meaning |
+|-------|---------|
+| `epic/milestone` | Story belongs to epic and milestone |
+| `epic` | Story belongs to epic (no milestone) |
+| (empty) | Ad-hoc story |
+
+---
+
+## Verification Annotations
+
+Add HTML comments to acceptance criteria referencing artifacts:
+
+```markdown
+## Acceptance Criteria
+
+- [ ] Sessions page displays list <!-- verify: snapshot:sessions -->
+- [ ] Clicking row opens detail <!-- verify: checkpoint:view-session-detail -->
+- [ ] CLI help shows commands <!-- verify: video:cli/help -->
+```
+
+**Annotation format:** `<!-- verify: <type>:<name> -->`
+
+| Type | Lookup |
+|------|--------|
+| `snapshot:<name>` | `snapshots.json` by name |
+| `checkpoint:<name>` | `checkpoints.json` by name |
+| `video:<path>` | Video file at path |
+
+---
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `just verify story <ID>` | Capture artifacts for story, generate report |
+| `just verify story-report <ID>` | Generate report only (artifacts exist) |
+
+**Story command flow:**
+1. Find story file by ID
+2. Parse `scope` from frontmatter
+3. Extract criteria with `<!-- verify: -->` annotations
+4. Capture only referenced artifacts
+5. Generate report at `verification/reports/<scope>/<id>.md`
+
+---
+
+## Directory Structure (Updated)
+
+```
+verification/
+├── snapshots.json
+├── checkpoints.json
+├── report.md                           # Global report
+├── reports/                            # Story-specific reports (COMMITTED)
+│   ├── coherence-verification/
+│   │   └── 01-artifact-pipeline/
+│   │       └── FEAT0109.md
+│   └── core/
+│       └── BUG0001.md
+├── snapshots/
+├── checkpoints/
+└── videos/
+```
+
+---
+
+## Story Report Format
+
+`verification/reports/<scope>/<id>.md`:
+
+```markdown
+# Verification: FEAT0109
+
+**Story:** Board generator grouped layout
+**Scope:** coherence-verification/01-artifact-pipeline
+**Generated:** 2026-01-18T10:30:00Z
+**Branch:** feat/0109-board-generator
+
+## Coverage
+
+| Criterion | Artifact | Status |
+|-----------|----------|--------|
+| Sessions page displays list | sessions.png | ✅ |
+| Clicking row opens detail | view-session-detail/ | ✅ |
+| CLI help shows commands | cli/help.webm | ✅ |
+
+**Coverage: 3/3 (100%)**
+
+## Uncovered Criteria
+
+(none)
+```
+
+---
+
+## Error Handling
+
+| Scenario | Behavior |
+|----------|----------|
+| Artifact not in definitions | Report shows `❌ (not defined)` |
+| Artifact capture fails | Report shows `❌ (capture failed)` |
+| No verify annotations | Report shows "No verification annotations found" |
+| Story file not found | Command fails with clear error |
+
+---
+
+## Deliverables (Phase 2)
+
+- [ ] Update story frontmatter schema (`scope` replaces `epics` + `milestone`)
+- [ ] Migrate all existing stories to new schema
+- [ ] Add verification annotation parsing
+- [ ] Implement `just verify story <ID>` command
+- [ ] Implement `just verify story-report <ID>` command
+- [ ] Update `.gitignore` to commit `reports/**/*.md`
+- [ ] Update CONVENTIONS.md with new schema

docs/board/stages/backlog/stories/[FEAT][0115]-eval-web-ui.md

@@ -4,10 +4,9 @@ title: Eval Web UI
 type: feat
 status: backlog
 priority: medium
-epics: [evals]
+scope: evals/39-performance-evaluation
 depends: [m39-feat-05]
 estimate: 4h
-milestone: 39
 ---
 
 # Eval Web UI

docs/board/stages/backlog/stories/[FEAT][0116]-pty-server-core.md

@@ -4,12 +4,10 @@ title: PTY server core
 type: feat
 status: backlog
 priority: medium
-epics: [tui]
+scope: tui/46-terminal-server
 depends: []
 estimate:
 created: 2026-01-14
-updated: 2026-01-14
-milestone: 46
 ---
 
 # PTY server core

docs/board/stages/backlog/stories/[FEAT][0117]-session-management.md

@@ -4,12 +4,10 @@ title: Session management
 type: feat
 status: backlog
 priority: medium
-epics: [tui]
+scope: tui/46-terminal-server
 depends: []
 estimate:
 created: 2026-01-14
-updated: 2026-01-14
-milestone: 46
 ---
 
 # Session management

docs/board/stages/backlog/stories/[FEAT][0118]-websocket-pty-endpoint.md

@@ -4,12 +4,10 @@ title: WebSocket PTY endpoint
 type: feat
 status: backlog
 priority: medium
-epics: [tui]
+scope: tui/46-terminal-server
 depends: []
 estimate:
 created: 2026-01-14
-updated: 2026-01-14
-milestone: 46
 ---
 
 # WebSocket PTY endpoint

docs/board/stages/backlog/stories/[FEAT][0119]-xtermjs-web-integration.md

@@ -4,12 +4,10 @@ title: xterm.js web integration
 type: feat
 status: backlog
 priority: medium
-epics: [tui]
+scope: tui/46-terminal-server
 depends: []
 estimate:
 created: 2026-01-14
-updated: 2026-01-14
-milestone: 46
 ---
 
 # xterm.js web integration

docs/board/stages/done/stories/[BUG][0001]-cwd-propagation.md

@@ -4,12 +4,10 @@ title: Fix CWD Propagation Implementation Plan
 type: bug
 status: done
 priority: medium
-epics: [core]
+scope: core
 depends: []
 estimate:
 created: 2026-01-07
-updated: 2026-01-07
-milestone: 
 ---
 # Fix CWD Propagation Implementation Plan
 

docs/board/stages/done/stories/[BUG][0002]-firehose-not-loading-historical-events.md

@@ -4,12 +4,10 @@ title: "bug-0002: Firehose Not Loading Historical Events"
 type: bug
 status: done
 priority: medium
-epics: [core]
+scope: core
 depends: []
 estimate:
 created: 2026-01-01
-updated: 2026-01-07
-milestone: 
 ---
 
 # bug-0002: Firehose Not Loading Historical Events