Add the owner-reviewed, tightly cropped Reviewer Skills screenshot to the public README. Pair it with the exact reviewer-inspection YAML set entry and explain how an available set becomes the saved and effective manual selection. Link the existing third-party notices near the example.
Before: The README listed packages but did not show how a named set appears for a role in Settings.
After: The README shows the Reviewer card with Reviewer inspection on request saved and effective. The screenshot's manual members, Code review then Component diff, match members: [code-review, c4-diff] in the copyable YAML. The exact PNG is 928 × 303 pixels, contains no metadata chunks or visible private task details, and matches the owner-provided image byte for byte.
Focused local check — image path and NOTICE link exist, and the README's YAML set entry matches the installed owner configuration.
Documentation disposition
updated: README now explains the named-set-to-role relationship with current UI evidence and a corresponding YAML excerpt. No product behavior changed.
Ablation decision
not_required: documentation and screenshot only; no experimental workflow mechanism changed.
Merge Danger
Door: two-way; the README section and PNG can be reverted.
Blast Radius: public documentation and a static image only. No package, owner configuration, or runtime behavior changes.
Rollback: revert the single PR commit if the explanation or image proves inaccurate.
Reviewer prerequisites
A browser that can load the public Gitea source branch. No running RelayView owner or provider credentials are needed.
Manual Test Plan
Action: Open https://tea.kyle-merritt.com/anodyine/relayview-skills/src/branch/ISSUE-6/README.md and read “A named set in RelayView.”
Expected: The screenshot renders legibly. The adjacent YAML names reviewer-inspection, role reviewer, step review, mode manual, and ordered members [code-review, c4-diff].
Action: Open the screenshot at https://tea.kyle-merritt.com/anodyine/relayview-skills/src/branch/ISSUE-6/docs/images/reviewer-manual-skill-set.png.
Expected: It shows only the Reviewer card, with no task sidebar, private paths, credentials, or package digests. Stop review if the image differs from the owner-provided crop.
Action: Check the README's third-party notices link.
Expected: It opens NOTICE.md on the same branch. GitHub mirror rendering is a separate check in #5 after that mirror exists.
Failure and recovery
If a Gitea image or link fails to render, record the page URL and browser observation on this PR and keep the issue in review. Correct the branch and recheck before merging. Do not claim GitHub mirror rendering until #5 verifies it.
Post-Merge Cleanup
After owner review and merge, use the repository's Gitea issue cleanup workflow for #6, then proceed to #5.
## Summary
Add the owner-reviewed, tightly cropped Reviewer Skills screenshot to the public README. Pair it with the exact `reviewer-inspection` YAML set entry and explain how an available set becomes the saved and effective manual selection. Link the existing third-party notices near the example.
Closes #6.
## Evidence
- **Before:** The README listed packages but did not show how a named set appears for a role in Settings.
- **After:** The README shows the Reviewer card with `Reviewer inspection on request` saved and effective. The screenshot's manual members, Code review then Component diff, match `members: [code-review, c4-diff]` in the copyable YAML. The exact PNG is 928 × 303 pixels, contains no metadata chunks or visible private task details, and matches the owner-provided image byte for byte.
### Checks run
At `b2ad71ea1de3af6fca86a66ba5ef81234b1411f6`:
- `python3 -m unittest discover -s tests -v` — 12 passed.
- `git diff --check` — no output, exit 0.
- Focused local check — image path and NOTICE link exist, and the README's YAML set entry matches the installed owner configuration.
## Documentation disposition
`updated`: README now explains the named-set-to-role relationship with current UI evidence and a corresponding YAML excerpt. No product behavior changed.
## Ablation decision
`not_required`: documentation and screenshot only; no experimental workflow mechanism changed.
## Merge Danger
**Door:** two-way; the README section and PNG can be reverted.
**Blast Radius:** public documentation and a static image only. No package, owner configuration, or runtime behavior changes.
**Rollback:** revert the single PR commit if the explanation or image proves inaccurate.
## Reviewer prerequisites
A browser that can load the public Gitea source branch. No running RelayView owner or provider credentials are needed.
## Manual Test Plan
1. [ ] **Action:** Open `https://tea.kyle-merritt.com/anodyine/relayview-skills/src/branch/ISSUE-6/README.md` and read “A named set in RelayView.”
**Expected:** The screenshot renders legibly. The adjacent YAML names `reviewer-inspection`, role `reviewer`, step `review`, mode `manual`, and ordered members `[code-review, c4-diff]`.
2. [ ] **Action:** Open the screenshot at `https://tea.kyle-merritt.com/anodyine/relayview-skills/src/branch/ISSUE-6/docs/images/reviewer-manual-skill-set.png`.
**Expected:** It shows only the Reviewer card, with no task sidebar, private paths, credentials, or package digests. Stop review if the image differs from the owner-provided crop.
3. [ ] **Action:** Check the README's third-party notices link.
**Expected:** It opens `NOTICE.md` on the same branch. GitHub mirror rendering is a separate check in #5 after that mirror exists.
## Failure and recovery
If a Gitea image or link fails to render, record the page URL and browser observation on this PR and keep the issue in review. Correct the branch and recheck before merging. Do not claim GitHub mirror rendering until #5 verifies it.
## Post-Merge Cleanup
After owner review and merge, use the repository's Gitea issue cleanup workflow for #6, then proceed to #5.
Visual check at b2ad71ea1de3af6fca86a66ba5ef81234b1411f6: I opened the branch README on the Gitea source host. The Reviewer screenshot rendered legibly above the formatted YAML excerpt, and the NOTICE link resolved to this branch. The image is the exact owner-provided crop; no task sidebar or private configuration detail appears in it. GitHub mirror rendering remains for #5 after that mirror exists.
Visual check at `b2ad71ea1de3af6fca86a66ba5ef81234b1411f6`: I opened the branch README on the Gitea source host. The Reviewer screenshot rendered legibly above the formatted YAML excerpt, and the NOTICE link resolved to this branch. The image is the exact owner-provided crop; no task sidebar or private configuration detail appears in it. GitHub mirror rendering remains for #5 after that mirror exists.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Add the owner-reviewed, tightly cropped Reviewer Skills screenshot to the public README. Pair it with the exact
reviewer-inspectionYAML set entry and explain how an available set becomes the saved and effective manual selection. Link the existing third-party notices near the example.Closes #6.
Evidence
Reviewer inspection on requestsaved and effective. The screenshot's manual members, Code review then Component diff, matchmembers: [code-review, c4-diff]in the copyable YAML. The exact PNG is 928 × 303 pixels, contains no metadata chunks or visible private task details, and matches the owner-provided image byte for byte.Checks run
At
b2ad71ea1de3af6fca86a66ba5ef81234b1411f6:python3 -m unittest discover -s tests -v— 12 passed.git diff --check— no output, exit 0.Documentation disposition
updated: README now explains the named-set-to-role relationship with current UI evidence and a corresponding YAML excerpt. No product behavior changed.Ablation decision
not_required: documentation and screenshot only; no experimental workflow mechanism changed.Merge Danger
Door: two-way; the README section and PNG can be reverted.
Blast Radius: public documentation and a static image only. No package, owner configuration, or runtime behavior changes.
Rollback: revert the single PR commit if the explanation or image proves inaccurate.
Reviewer prerequisites
A browser that can load the public Gitea source branch. No running RelayView owner or provider credentials are needed.
Manual Test Plan
Action: Open
https://tea.kyle-merritt.com/anodyine/relayview-skills/src/branch/ISSUE-6/README.mdand read “A named set in RelayView.”Expected: The screenshot renders legibly. The adjacent YAML names
reviewer-inspection, rolereviewer, stepreview, modemanual, and ordered members[code-review, c4-diff].Action: Open the screenshot at
https://tea.kyle-merritt.com/anodyine/relayview-skills/src/branch/ISSUE-6/docs/images/reviewer-manual-skill-set.png.Expected: It shows only the Reviewer card, with no task sidebar, private paths, credentials, or package digests. Stop review if the image differs from the owner-provided crop.
Action: Check the README's third-party notices link.
Expected: It opens
NOTICE.mdon the same branch. GitHub mirror rendering is a separate check in #5 after that mirror exists.Failure and recovery
If a Gitea image or link fails to render, record the page URL and browser observation on this PR and keep the issue in review. Correct the branch and recheck before merging. Do not claim GitHub mirror rendering until #5 verifies it.
Post-Merge Cleanup
After owner review and merge, use the repository's Gitea issue cleanup workflow for #6, then proceed to #5.
Visual check at
b2ad71ea1de3af6fca86a66ba5ef81234b1411f6: I opened the branch README on the Gitea source host. The Reviewer screenshot rendered legibly above the formatted YAML excerpt, and the NOTICE link resolved to this branch. The image is the exact owner-provided crop; no task sidebar or private configuration detail appears in it. GitHub mirror rendering remains for #5 after that mirror exists.