docs: add Mirrors section to README (canonical + GitHub) #2

Open
igor wants to merge 1 commit from agent/1-docs-add-mirrors-section-to-readme-canonical into master
Collaborator

What this PR does

  • docs: add Mirrors section to README (canonical + GitHub)
  • Inserted after the intro paragraph, before the first existing ## section, exactly as specified in the issue

Test plan

  • make test passes (bin/test-still.sh: 14 passed, 0 failed)
  • git diff shows exactly one hunk in README.md

Closes #1

## What this PR does - [x] docs: add Mirrors section to README (canonical + GitHub) - [x] Inserted after the intro paragraph, before the first existing `##` section, exactly as specified in the issue ## Test plan - [x] `make test` passes (`bin/test-still.sh`: 14 passed, 0 failed) - [x] `git diff` shows exactly one hunk in README.md Closes #1
docs: add Mirrors section to README (canonical + GitHub)
All checks were successful
Validate / validate (pull_request) Successful in 10s
9a14331e64
Author
Collaborator

🤖 Review — APPROVE (automated)

CI for 9a14331e: success

Docs-only PR adding a ## Mirrors section to README.md. Approving — it matches the issue spec verbatim and contains nothing else.

Checks performed

  • Spec conformance: the inserted block is character-for-character the markdown given in issue #1 (canonical bold line, "Mirrored for your convenience:", single GitHub bullet, italic disclaimer). No extra mirrors added, no wording drift.
  • Placement: single hunk at README.md L11-20, after the intro paragraph and before the first existing ## ("How it works") — as required.
  • Scope / minimal touch: one hunk, one file, zero unrelated edits or reflowing of surrounding lines. Nothing out-of-scope (no mirror config, as the issue explicitly excluded).
  • Comment contract: N/A (markdown prose only).
  • Checklist honesty: both "What this PR does" boxes correspond to what's actually in the diff. The "git diff shows exactly one hunk in README.md" claim is directly verifiable from the diff and is true.
  • CI: success on 9a14331.

Notes (non-blocking)

  • I can't verify the "bin/test-still.sh: 14 passed, 0 failed" count from the diff; CI green is my only signal there. Irrelevant to risk for a docs-only change with no test-affecting content.
  • No tests added, which is correct here — there's no behavior to cover.
  • The issue text carries a stale Blocked (2026-08-09 15:25Z) note about a missing CLAUDE.md. Not this PR's problem (adding one would be out of scope), but the human may want to clear that block note / add the file so future ticks aren't gated.

Independent review by the harness on claude-opus-5 (effort: high). The human reviewer is requested once Igor has reviewed; a human still merges.

### 🤖 Review — `APPROVE` _(automated)_ CI for `9a14331e`: **success** Docs-only PR adding a `## Mirrors` section to `README.md`. Approving — it matches the issue spec verbatim and contains nothing else. **Checks performed** - **Spec conformance:** the inserted block is character-for-character the markdown given in issue #1 (canonical bold line, "Mirrored for _your_ convenience:", single GitHub bullet, italic disclaimer). No extra mirrors added, no wording drift. - **Placement:** single hunk at README.md L11-20, after the intro paragraph and before the first existing `##` ("How it works") — as required. - **Scope / minimal touch:** one hunk, one file, zero unrelated edits or reflowing of surrounding lines. Nothing out-of-scope (no mirror config, as the issue explicitly excluded). - **Comment contract:** N/A (markdown prose only). - **Checklist honesty:** both "What this PR does" boxes correspond to what's actually in the diff. The "`git diff` shows exactly one hunk in README.md" claim is directly verifiable from the diff and is true. - **CI:** `success` on 9a14331. **Notes (non-blocking)** - I can't verify the "`bin/test-still.sh`: 14 passed, 0 failed" count from the diff; CI green is my only signal there. Irrelevant to risk for a docs-only change with no test-affecting content. - No tests added, which is correct here — there's no behavior to cover. - The issue text carries a stale `Blocked (2026-08-09 15:25Z)` note about a missing `CLAUDE.md`. Not this PR's problem (adding one would be out of scope), but the human may want to clear that block note / add the file so future ticks aren't gated. --- <sub>Independent review by the harness on `claude-opus-5` (effort: high). The human reviewer is requested once Igor has reviewed; a human still merges.</sub> <!-- review sha=9a14331e64ed8241226517d2400091dd17ec578c verdict=APPROVE ci=success -->
igor added spent time 2026-08-09 22:08:44 +00:00
15 seconds
All checks were successful
Validate / validate (pull_request) Successful in 10s
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin agent/1-docs-add-mirrors-section-to-readme-canonical:agent/1-docs-add-mirrors-section-to-readme-canonical
git switch agent/1-docs-add-mirrors-section-to-readme-canonical

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff agent/1-docs-add-mirrors-section-to-readme-canonical
git switch agent/1-docs-add-mirrors-section-to-readme-canonical
git rebase master
git switch master
git merge --ff-only agent/1-docs-add-mirrors-section-to-readme-canonical
git switch agent/1-docs-add-mirrors-section-to-readme-canonical
git rebase master
git switch master
git merge --no-ff agent/1-docs-add-mirrors-section-to-readme-canonical
git switch master
git merge --squash agent/1-docs-add-mirrors-section-to-readme-canonical
git switch master
git merge --ff-only agent/1-docs-add-mirrors-section-to-readme-canonical
git switch master
git merge agent/1-docs-add-mirrors-section-to-readme-canonical
git push origin master
Sign in to join this conversation.
No reviewers
No milestone
No assignees
1 participant
Notifications
Total time spent: 15 seconds
igor
15 seconds
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
joshtronic/distillery!2
No description provided.