Media sync slice 12: the hardware verification checklist - #2314
Merged
ericgriffin merged 2 commits intoSep 24, 2026
Merged
Conversation
The verification matrix of the media sync program (spec section 8): three device pairs, each item citing the two-device harness scenario it proves on real hardware, with capture instructions for a failure, a verification status to fill in, and the reporter follow-ups that close #425 and #1625 and then the tracking issue.
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Multiple unresolved checklist correctness, traceability, and closure-criteria issues remain.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 7
Open (8)
What changed in this PR
Adds a documentation-only hardware verification checklist for the media sync program.
Changes:
- Defines device-pair and store test scenarios.
- Documents diagnostics, verification status, and exit criteria.
- Adds reporter follow-ups for issues #425 and #1625.
| File | Summary |
|---|---|
docs/superpowers/specs/2026-09-18-media-sync-manual-test-checklist.md |
Manual hardware test matrix and follow-up procedures |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Every item now carries its scenario tag or 'no scenario'. Item 1.8 is a controlled lost-stamp run that cannot be satisfied by a normal upload. Items 2.3 to 2.8 name their dependency on slice 9. Item 2.7 states what a moved file should do under slice 9's library search. #1625 closes on the hardware pass or the reporter's confirmation, and the tracking issue needs every pair on every listed store.
ericgriffin
deleted the
ericgriffin/media-sync-s12-verification-matrix
branch
September 24, 2026 05:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #2132
Part of #2090
Slice 12 of the media sync program (spec section 8): the manual device checklist for the hardware pass, committed as
docs/superpowers/specs/2026-09-18-media-sync-manual-test-checklist.md, in the style of the Google Drive checklist.Docs only. This PR closes nothing: #2132 and the tracking issue close when the checklist passes on hardware, and #425 and #1625 when their reporters confirm (spec 10).
What it covers
Every item cites the two-device harness scenario (S0 to S10) it proves on real devices, real photo libraries and real stores:
It also records what to capture when an item fails (Copy diagnostics and Export media report), a verification status to fill in per pair and store, and the reporter follow-ups for #425 and #1625. Every screen name and label it cites was checked against the English strings.