docs(phase-13): record human verification completion

- mark phase 13 human verification complete in UAT and verification artifacts
- update project, state, and roadmap to reflect completed milestone behavior

Author: seasonyuu

.planning/PROJECT.md

@@ -20,11 +20,12 @@ Users can reliably capture logic-analyzer data from `DSLogic Plus` via CLI and p
 - [x] User can validate DSLogic Plus option combinations before capture so the shipped `v1.0` capture/export path remains stable. Validated in Phase 11.
 - [x] User can expose and choose DSView-style `DSLogic Plus` device options from the CLI, including operation mode, stop option, channel mode, enabled channels, threshold voltage, and filter selection. Validated in Phase 12.
 - [x] User can use a discoverable non-interactive CLI surface to inspect supported device-option values before a run. Validated across Phases 10 and 12.
+- [x] User can apply the selected DSView-compatible device options before acquisition begins. Validated in Phase 13.
+- [x] User can report the effective option values used for the run in CLI output and metadata. Validated in Phase 13.
 
 ### Active
 
-- [ ] Apply the selected DSView-compatible device options before acquisition begins.
-- [ ] Report the effective option values used for the run in CLI output and metadata.
+None - milestone `v1.1` requirements are now fully validated.
 
 ### Out of Scope
 
@@ -47,6 +48,7 @@ Milestone `v1.1` is grounded in direct DSView source inspection rather than gree
 - The validated DSLogic Plus capture/export path is the baseline that `v1.1` must preserve.
 - Phase 11 validation modeling completed on `2026-04-13`, including selected-device capability loading, pure validation, and stable CLI validation codes.
 - Phase 12 CLI device-option surface completed on `2026-04-13`, including friendly capture flags, tokenized inspection output, and spawned CLI contract regressions.
+- Phase 13 option-aware capture reporting completed on `2026-04-13`, including deterministic runtime option application, requested/effective reporting, and successful hardware verification.
 - The next milestone is now defined around device-option parity for the existing `DSLogic Plus` target rather than broader hardware support or decode work.
 
 ## Current Milestone: v1.1 DSLogic Plus device options
@@ -96,4 +98,4 @@ This document evolves at phase transitions and milestone boundaries.
 4. Update Context with current state
 
 ---
-*Last updated: 2026-04-13 after completing Phase 12 CLI device option surface*
+*Last updated: 2026-04-13 after completing Phase 13 option-aware capture reporting*

.planning/ROADMAP.md

@@ -77,7 +77,7 @@ Plans:
 Plans:
 - [x] `13-01-PLAN.md` - Apply the full validated device-option request through the sys/core/cli capture path before acquisition starts.
 - [ ] `13-02-PLAN.md` - Persist requested/effective DSLogic Plus option facts in metadata and CLI success output.
-- [ ] `13-03-PLAN.md` - Lock final option-aware capture regressions and refresh the Phase 13 validation contract.
+- [x] `13-03-PLAN.md` - Lock final option-aware capture regressions and refresh the Phase 13 validation contract. (completed 2026-04-13)
 
 ## Progress
 
@@ -89,7 +89,7 @@ Phases execute in numeric order: 10 -> 11 -> 12 -> 13
 | 10. Device Option Bridge and Discovery | 3/3 | Complete    | 2026-04-10 |
 | 11. Device Option Validation Model | 3/3 | Complete    | 2026-04-13 |
 | 12. CLI Device Option Surface | 3/3 | Complete    | 2026-04-13 |
-| 13. Option-Aware Capture Reporting | 3/3 | Complete   | 2026-04-13 |
+| 13. Option-Aware Capture Reporting | 3/3 | Complete    | 2026-04-13 |
 
 ## Archived Milestones
 
@@ -107,4 +107,5 @@ Phases execute in numeric order: 10 -> 11 -> 12 -> 13
 
 - Active milestone: `v1.1 DSLogic Plus device options`
 - Phase 10 completed and live-verified on: `2026-04-10`
-- Next action: Execute `13-02-PLAN.md` to report requested and effective device-option facts in CLI output and metadata.
+- Phase 13 completed with live hardware verification on: `2026-04-13`
+- Next action: Review milestone completion and begin the next milestone when ready.

.planning/STATE.md

@@ -4,11 +4,11 @@ milestone: v1.1
 milestone_name: milestone
 current_phase: 13
 current_phase_name: option aware capture reporting
-current_plan: 3
-status: verifying
-stopped_at: Completed 13-03-PLAN.md
-last_updated: "2026-04-13T11:37:14.764Z"
-last_activity: 2026-04-13
+current_plan: Not started
+status: completed
+stopped_at: Completed Phase 13 with human verification
+last_updated: "2026-04-13T12:35:52Z"
+last_activity: 2026-04-13 -- Phase 13 human verification passed
 progress:
   total_phases: 4
   completed_phases: 4
@@ -24,18 +24,18 @@ progress:
 See: `.planning/PROJECT.md` (updated 2026-04-10)
 
 **Core value:** Users can reliably capture logic-analyzer data from `DSLogic Plus` via CLI and produce waveform output files that are easy for automation and AI agents to analyze.
-**Current focus:** Phase 13 — option-aware-capture-reporting
+**Current focus:** Milestone v1.1 complete
 
 ## Current Position
 
 Current Phase: 13
 Current Phase Name: option aware capture reporting
-Current Plan: 3
+Current Plan: Not started
 Total Plans in Phase: 3
-Phase: 13 (option-aware-capture-reporting) — READY
+Phase: 13 (option-aware-capture-reporting) — COMPLETE
 Plan: 3 of 3
-Status: Phase complete — ready for verification
-Last activity: 2026-04-13
+Status: Phase complete and human-verified
+Last activity: 2026-04-13 -- Phase 13 human verification passed
 
 ## Accumulated Context
 
@@ -96,14 +96,14 @@ Last activity: 2026-04-13
 
 ## Session Continuity
 
-Last session: 2026-04-13T11:37:14.755Z
+Last session: 2026-04-13T12:35:52Z
 
-Stopped At: Completed 13-03-PLAN.md
+Stopped At: Completed Phase 13 with human verification
 
 Resume File: None
 
 ## Immediate Next Steps
 
-- Execute `13-02-PLAN.md` to surface requested and effective option facts in CLI output and metadata.
-- Preserve the completed option-aware apply path while Phase 13-02 builds reporting on top of `EffectiveDeviceOptionState`.
-- Keep the shipped `v1.0` capture/export baseline stable while Phase 13-02 adds reporting behavior.
+- Milestone `v1.1` is functionally complete.
+- Review the final milestone state and archive/transition with the next milestone workflow when ready.
+- Preserve the validated `v1.0` baseline plus Phases 10-13 option workflow as the reference for future milestone planning.

.planning/phases/13-option-aware-capture-reporting/13-HUMAN-UAT.md

@@ -1,38 +1,38 @@
 ---
-status: partial
+status: resolved
 phase: 13-option-aware-capture-reporting
 source: [13-VERIFICATION.md]
 started: 2026-04-13T12:04:52Z
-updated: 2026-04-13T12:04:52Z
+updated: 2026-04-13T12:35:52Z
 ---
 
 ## Current Test
 
-awaiting human testing
+hardware verification completed
 
 ## Tests
 
 ### 1. Real successful capture reporting
 expected: A real DSLogic Plus run succeeds, JSON and metadata both include `device_options.requested` and `device_options.effective`, and text shows only `effective options:` before artifact paths.
-result: pending
+result: passed — real device run completed successfully with JSON requested/effective blocks and text-only `effective options:` output.
 
 ### 2. Real partial-apply failure honesty
 expected: A safe pre-acquisition setter failure still reports both `applied_steps` and `failed_step` in the JSON error.
-result: pending
+result: passed — real hardware apply failure returned `device_option_apply_failed` with both `applied_steps` and `failed_step`.
 
 ### 3. Metadata sidecar on hardware
 expected: `schema_version` is `2`, `device_options` contains requested/effective snapshots, and the paths match the emitted `.vcd` and `.json` artifacts.
-result: pending
+result: passed — hardware sidecar shows `schema_version: 2`, contains `device_options.requested` / `device_options.effective`, and artifact paths match emitted files.
 
 ## Summary
 
 total: 3
-passed: 0
+passed: 3
 issues: 0
-pending: 3
+pending: 0
 skipped: 0
 blocked: 0
 
 ## Gaps
 
-None yet - awaiting hardware verification.
+None - hardware verification completed successfully.

.planning/phases/13-option-aware-capture-reporting/13-VERIFICATION.md

@@ -1,7 +1,7 @@
 ---
 phase: 13-option-aware-capture-reporting
 verified: 2026-04-13T11:55:11Z
-status: human_needed
+status: passed
 score: 7/7 must-haves verified
 overrides_applied: 0
 human_verification:
@@ -20,7 +20,7 @@ human_verification:
 
 **Phase Goal:** Apply the selected options during capture and preserve the effective option facts in the final capture artifacts.
 **Verified:** 2026-04-13T11:55:11Z
-**Status:** human_needed
+**Status:** passed
 **Re-verification:** No - initial verification
 
 ## Goal Achievement
@@ -95,29 +95,26 @@ human_verification:
 | `crates/dsview-cli/tests/capture_cli.rs` | `447` | Spawned capture contract is validated through the env-gated fixture seam instead of live hardware | ℹ️ Info | Intentional and documented; it proves shipped JSON/text/error shape, but it is why the phase remains `human_needed` for final DSLogic Plus confirmation. |
 | `crates/dsview-core/src/lib.rs` | `699` | Post-apply readback failure path is mapped through `DeviceOptionApplyFailure` without dedicated regression coverage | ⚠️ Warning | Setter rejection coverage is strong, but getter/readback failure after successful apply remains an unexercised edge path that could misattribute a late failure to `sample_rate`. |
 
-### Human Verification Required
+### Human Verification Completed
 
 ### 1. Real Successful Capture Reporting
 
-**Test:** On a machine with a working DSLogic Plus, run the option-aware capture command from `.planning/phases/13-option-aware-capture-reporting/13-VALIDATION.md:67`, then rerun in text mode with the same device-option arguments.
-**Expected:** The JSON response and metadata sidecar both include `device_options.requested` and `device_options.effective`, while text mode shows only `effective options:` lines before the artifact paths.
-**Why human:** The automated path proves the contract through mocks and the debug-only fixture seam, but this workstation still lacks trustworthy live libusb/device confirmation.
+**Result:** passed
+**Evidence:** Real hardware capture succeeded; JSON and metadata both included `device_options.requested` and `device_options.effective`, while text mode showed only `effective options:` lines before the artifact paths.
 
 ### 2. Real Partial-Apply Failure Honesty
 
-**Test:** Safely trigger a pre-acquisition device-option setter failure on a real DSLogic Plus, following `.planning/phases/13-option-aware-capture-reporting/13-VALIDATION.md:68`.
-**Expected:** The capture fails before acquisition starts and the JSON error still includes both `applied_steps` and `failed_step`.
-**Why human:** The shipped failure shape is automated through fixtures, but only hardware can confirm a real runtime rejection reports the same facts.
+**Result:** passed
+**Evidence:** A real pre-acquisition setter failure returned `device_option_apply_failed` with both `applied_steps` and `failed_step`.
 
 ### 3. Metadata Sidecar On Hardware
 
-**Test:** Inspect the metadata sidecar from the successful hardware run described at `.planning/phases/13-option-aware-capture-reporting/13-VALIDATION.md:69`.
-**Expected:** `schema_version` is `2`, `device_options` contains requested/effective snapshots, and the artifact paths match the emitted `.vcd` and `.json` files.
-**Why human:** The schema is fully tested in-process, but real capture/export still needs a hardware-backed final pass.
+**Result:** passed
+**Evidence:** The real sidecar reported `schema_version: 2`, included the `device_options` block, and the artifact paths matched the emitted `.vcd` / `.json` files.
 
 ### Gaps Summary
 
-No code or wiring gaps were found in the Phase 13 implementation. The phase goal is achieved in the codebase and in automated regression coverage; the remaining work is the explicitly documented live-hardware verification that cannot be completed on this machine.
+No code or wiring gaps were found in the Phase 13 implementation. The phase goal is achieved in the codebase, in automated regression coverage, and in the completed live-hardware verification.
 
 ---