---
phase: 10-real-world-runtime-validation
plan: 03
type: execute
wave: 3
depends_on:
- 10-01
- 10-02
files_modified:
- .planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md
- .planning/REQUIREMENTS.md
- .planning/ROADMAP.md
autonomous: false
requirements:
- RTVAL-05
must_haves:
truths:
- "A reviewer can open RUNTIME-VALIDATION.md and read a complete signed-off report with tenant, device, OS build, driver vendor, screenshots/logs, and any issues"
- "Every RTVAL-01..04 result is PASS/FAIL with cited evidence (no PENDING)"
- "Any FAIL has either a v1.1 defect ticket or a written deferral rationale"
- "REQUIREMENTS.md and ROADMAP.md mark Phase 10 complete"
artifacts:
- path: ".planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md"
provides: "Final signed-off runtime validation report"
contains: "Signed off by:"
key_links:
- from: "RUNTIME-VALIDATION.md Sign-off checklist"
to: "evidence/*.png and evidence/*.txt files from plan 10-02"
via: "markdown relative links"
pattern: "\\]\\(evidence/.*\\)"
---
Convert the draft RUNTIME-VALIDATION.md into a signed-off, reviewable report and update tracking docs so Phase 10 can be marked complete.
Purpose: RTVAL-05 requires a reviewer-grade report, not just scattered evidence files. This plan closes the loop.
Output: A final RUNTIME-VALIDATION.md committed to the repo plus REQUIREMENTS.md/ROADMAP.md ticks.
@C:/Users/SebastienQUEROL/.claude/get-shit-done/workflows/execute-plan.md
@C:/Users/SebastienQUEROL/.claude/get-shit-done/templates/summary.md
@.planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md
@.planning/REQUIREMENTS.md
@.planning/ROADMAP.md
Task 1: Finalize RUNTIME-VALIDATION.md report body
.planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md
Read the current RUNTIME-VALIDATION.md (populated by plans 10-01 and 10-02). Then:
1. For each RTVAL-01..04 section, ensure:
- Status line is PASS or FAIL (not PENDING).
- Evidence paths use markdown relative links like `[screenshot](evidence/rtval-01-tenant-upload.png)`.
- Notes field has at least one sentence (either "no anomalies" or description of issues).
2. For each FAIL, confirm there is a corresponding entry under "## Issues Found" formatted as:
```
- **[RTVAL-0X]** — ">
```
If a FAIL has no Issues Found entry yet, add one noting "TODO: triage — see Task 2 checkpoint".
3. Update the "Status" field at the top from `DRAFT (in progress)` to `READY FOR SIGN-OFF`.
Do NOT fabricate results. If any section is still PENDING because plan 10-02 did not actually run, STOP and return an error to the executor — 10-03 must not be run before 10-02 is complete.
! grep -q "Status: PENDING" .planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md && grep -q "READY FOR SIGN-OFF\|SIGNED OFF" .planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md
Report has zero PENDING status lines, all evidence links are markdown-valid, Issues Found is consistent with FAILs, and top-level status is READY FOR SIGN-OFF.
Task 2: Human review and sign-off
.planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md
PAUSE for human reviewer. The reviewer (user acting as technician/owner) MUST:
1. Open `.planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md`.
2. Walk every RTVAL-01..04 section and click every evidence link. Confirm screenshots open and log excerpts are readable.
3. For every FAIL, confirm the "Issues Found" entry is present AND has either:
- a v1.1 defect ticket ID (open a ticket if needed), OR
- an explicit deferral to v1.2 with written rationale.
4. If satisfied, edit the report's Sign-off block:
- Change `Signed off by:` to the reviewer's name.
- Change `Signed off date:` to today's date.
- Tick the three sign-off checkboxes.
- Change the top-level Status from `READY FOR SIGN-OFF` to `SIGNED OFF`.
5. If NOT satisfied, describe exactly which section is lacking and which additional evidence is required. The plan loops back to plan 10-02 (or a gap-closure plan).
Resume signal: reply "signed off" (after editing the file) or describe missing evidence.
grep -q "^\*\*Status:\*\* SIGNED OFF" .planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md
Report top-level status = SIGNED OFF; Signed off by/date populated; all three sign-off checkboxes ticked.
Task 3: Tick RTVAL requirements and mark Phase 10 complete in tracking docs
.planning/REQUIREMENTS.md, .planning/ROADMAP.md
Only run after Task 2 signals "signed off". Verify by grepping the report for `Status: SIGNED OFF` — if absent, STOP.
Then:
1. In `.planning/REQUIREMENTS.md`:
- Change `- [ ] **RTVAL-01**` through `- [ ] **RTVAL-05**` to `- [x]`.
- In the Traceability table, change status for RTVAL-01..05 from `Pending` to `Complete`. If any RTVAL ended FAIL and was deferred, mark it `Deferred (v1.2)` instead and add a footnote link to the report's Issues Found entry.
2. In `.planning/ROADMAP.md`:
- Change `- [ ] **Phase 10: Real-World Runtime Validation**` to `- [x]` and append `(completed )`.
- In the Progress table row for Phase 10, set `Plans Complete` to `3/3`, `Status` to `Complete`, and `Completed` to today's date.
Do not touch unrelated rows. Preserve existing formatting exactly.
grep -q "\[x\] \*\*RTVAL-05\*\*" .planning/REQUIREMENTS.md && grep -q "\[x\] \*\*Phase 10" .planning/ROADMAP.md
REQUIREMENTS.md has RTVAL-01..05 ticked (or explicitly deferred); ROADMAP.md Phase 10 ticked with completion date and 3/3 plans.
- RUNTIME-VALIDATION.md top-level status = SIGNED OFF
- Sign-off name + date populated
- Zero PENDING status lines
- REQUIREMENTS.md RTVAL-01..05 ticked
- ROADMAP.md Phase 10 ticked
A fresh reviewer can clone the repo, open RUNTIME-VALIDATION.md, follow every evidence link, and reach the same PASS/FAIL verdicts. Tracking docs reflect phase completion.