Evidence
registry/repos.json's PhotoCleaner entry carries this driftNotes entry:
Private for now by maintainer decision, going public once the conformance work settles, since
public serves prospective users and lowers the GitHub bill. Until that flip the declared
github-release channel is not consumer-pullable and shields.io cannot read the repo, so the
GitHub-sourced shields render broken.
Live check, just run:
$ gh repo view ptr727/PhotoCleaner --json isPrivate,visibility
{"isPrivate":false,"visibility":"PUBLIC"}
The repo is public now. Confirmed independently by spec/audit.py PhotoCleaner's own
has_discussions finding during a resync of that repo (DEFECT settings: has_discussions live=False expected=True — the audit's own settings check derives the expected value from
visibility, and it expected true, meaning the audit already reads this repo as public).
Why this is worth fixing rather than leaving
- The note's own stated consequence ("the GitHub-sourced shields render broken") is exactly the
kind of thing that stops being true silently once the repo flips, and nothing re-checks it.
- A stale
driftNotes entry asserting outstanding work ("private for now", "going public once...")
is the shape RESYNC.md section 3 calls out by name: "A driftNote asserting outstanding work
in prose ('pending', 'not yet', 'behind') contradicts a clean audit outright" — and a resync is
supposed to reconcile it, but a registry change is a hub-side edit outside what a downstream
repo's own resync PR touches, so it needs its own fix here.
Expected
Drop the "Private for now..." sentence from PhotoCleaner's driftNotes (the multi-arch Docker /
GitHub release sentence beside it stays, that one's still accurate). Worth a quick check whether
the shields.io badges on the README now render correctly given the flip, since that was the
noted symptom.
Repo, ref
ptr727/ProjectTemplate at main (as of this filing), registry/repos.json's PhotoCleaner
entry.
Evidence
registry/repos.json'sPhotoCleanerentry carries thisdriftNotesentry:Live check, just run:
The repo is public now. Confirmed independently by
spec/audit.py PhotoCleaner's ownhas_discussionsfinding during a resync of that repo (DEFECT settings: has_discussions live=False expected=True— the audit's own settings check derives the expected value fromvisibility, and it expected
true, meaning the audit already reads this repo as public).Why this is worth fixing rather than leaving
kind of thing that stops being true silently once the repo flips, and nothing re-checks it.
driftNotesentry asserting outstanding work ("private for now", "going public once...")is the shape
RESYNC.mdsection 3 calls out by name: "AdriftNoteasserting outstanding workin prose ('pending', 'not yet', 'behind') contradicts a clean audit outright" — and a resync is
supposed to reconcile it, but a registry change is a hub-side edit outside what a downstream
repo's own resync PR touches, so it needs its own fix here.
Expected
Drop the "Private for now..." sentence from PhotoCleaner's
driftNotes(the multi-arch Docker /GitHub release sentence beside it stays, that one's still accurate). Worth a quick check whether
the shields.io badges on the README now render correctly given the flip, since that was the
noted symptom.
Repo, ref
ptr727/ProjectTemplateatmain(as of this filing),registry/repos.json'sPhotoCleanerentry.