Mark PhotoCleaner Operational After the Promotion of the b09078e Resync - #739
Conversation
The deterministic audit is clean at main (f56178a) and develop with the hub at b09078e, so the report drops the promotion-in-flight framing, moves readme-structure and agent-instruction-set to pass, records the dead-path block and its hub fix, and closes the two escalations.
There was a problem hiding this comment.
Pull request overview
Updates the PhotoCleaner audit report to reflect that develop has been promoted to main and the repository now audits as operational/clean under hub b09078e.
Changes:
- Refreshes the audited branch SHA, verdict, and run stamp for the latest audit run.
- Updates drift/convergence/escalation sections to reflect that promotion-related blockers are resolved and the audit is now clean.
Suppressed comments (2)
reports/photocleaner/audit.md:15
- This line adds an inline Markdown link (
[text](url)), but inline links are disallowed here per the repo's reference-style link rule (allowed inline-link exceptions are AGENTS.md, GOVERNANCE.md, OPERATIONS.md, and .github/copilot-instructions.md). Prefer a reference-style link or plain text reference (see.agents/skills/comment-and-doc-style/references/markdown-links.md:9-15,57-65).
The promotion was blocked for one round by the prose gate's `dead-path` rule flagging verbatim mentions of the retired `repo-config/configure.sh`, filed as [#721](https://github.com/ptr727/ProjectTemplate/issues/721) and fixed by #731. The gate fetches its rules from hub `develop` on a `develop`-targeted run, so a re-run cleared it with no repo change. Copilot read 18 of 19 changed files on the promotion in both rounds and raised no thread. Its one suppressed finding, a Mermaid edge in the hub-carried `WORKFLOW.md` diagram, was answered on the pull request as declined, since the diagram is hub content and the D1 text beside it already states the rule.
reports/photocleaner/audit.md:57
- These list items use inline Markdown links (
[text](url)), which violates the repo's reference-style link rule for Markdown files outside the four allowed exceptions. Use reference-style links (with definitions at the bottom) or plain text references instead (see.agents/skills/comment-and-doc-style/references/markdown-links.md:9-15,57-65).
1. [#721](https://github.com/ptr727/ProjectTemplate/issues/721): `prose_lint.py dead-path` could not recognize a hub-hosted path in a repo that retired the file, so verbatim text naming `repo-config/configure.sh` failed a downstream promotion gate. Fixed by #731.
2. [#722](https://github.com/ptr727/ProjectTemplate/issues/722): the hub's `.github/copilot-instructions.md` linked `GOVERNANCE.md#every-finding-ends-in-an-action`, an anchor that left `GOVERNANCE.md` when PR Review Etiquette was packaged as a Skill. PhotoCleaner re-pointed its copy in #50 after Copilot raised it, and #52 carried the canonical wording #730 landed.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Inline links are reserved for the four named files, and the sibling reports already use the owner/repo#N autolink form.
|
Answering the two suppressed findings ( |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (2)
reports/photocleaner/audit.md:15
- Grammar: "raised no thread" should be plural, since it refers to the absence of any review threads.
The promotion was blocked for one round by the prose gate's `dead-path` rule flagging verbatim mentions of the retired `repo-config/configure.sh`, filed as #721 and fixed by #731. The gate fetches its rules from hub `develop` on a `develop`-targeted run, so a re-run cleared it with no repo change. Copilot read 18 of 19 changed files on the promotion in both rounds and raised no thread. Its one suppressed finding, a Mermaid edge in the hub-carried `WORKFLOW.md` diagram, was answered on the pull request as declined, since the diagram is hub content and the D1 text beside it already states the rule.
reports/photocleaner/audit.md:57
- Grammar: "the canonical wording #730 landed" is missing a connector word and reads ungrammatically; add "that" (or similar) to clarify the reference.
2. #722: the hub's `.github/copilot-instructions.md` linked `GOVERNANCE.md#every-finding-ends-in-an-action`, an anchor that left `GOVERNANCE.md` when PR Review Etiquette was packaged as a Skill. PhotoCleaner re-pointed its copy in #50 after Copilot raised it, and #52 carried the canonical wording #730 landed.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
reports/photocleaner/audit.md:54
- This section says "Two hub findings from this pass" but the report above states the current audit run is clean (no findings). These escalations appear to be historical carry-forward from the earlier snapshot, so the wording is misleading.
Two hub findings from this pass, filed rather than patched per repo, both closed since:
|
Answering the suppressed finding on head cf7044d ( |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (4)
reports/photocleaner/audit.md:19
- These unqualified
#49/#50/#52references will auto-link to issues/PRs in this repository, but they appear to be PhotoCleaner PR numbers (the surrounding text is about PhotoCleaner resync/promotions). Useptr727/PhotoCleaner#…so the references resolve correctly.
Judged at `main`. Type-dimension checks are hand-judged per AUDIT.md section 4 and are unchanged from the 2026-08-01 snapshot, since #49, #50, and #52 touched governance and configuration only.
reports/photocleaner/audit.md:46
- Unqualified
#50/#52/#51will auto-link to ProjectTemplate issues/PRs, but this line is summarizing PhotoCleaner PR state. Useptr727/PhotoCleaner#…so the links point to the correct repository.
None. #50, #52 (to `develop`) and #51 (`develop -> main`) are merged.
reports/photocleaner/audit.md:57
#50and#52here will auto-link to ProjectTemplate issues/PRs, but this sentence is describing actions taken in the PhotoCleaner repository. Use explicitptr727/PhotoCleaner#…references so readers land on the right PRs.
2. #722: the hub's `.github/copilot-instructions.md` linked `GOVERNANCE.md#every-finding-ends-in-an-action`, an anchor that left `GOVERNANCE.md` when PR Review Etiquette was packaged as a Skill. PhotoCleaner re-pointed its copy in #50 after Copilot raised it, and #52 carried the canonical wording that #730 landed.
reports/photocleaner/audit.md:13
- Unqualified
#51will auto-link to ProjectTemplate issue/PR 51, but this sentence is describing a PhotoCleaner promotion PR. Use an explicitowner/repo#Nreference so the link resolves to the intended repository.
This issue also appears in the following locations of the same file:
- line 19
- line 46
- line 57
`develop` vs `main`: identical content, since #51 merged `develop` at `ab23034` and nothing has landed since. The audit at `develop` reports zero findings.
A bare #N in a hub file autolinks to the hub's own issue or pull request, so each PhotoCleaner reference now carries owner/repo.
|
Answering the four suppressed findings on head 4b1882c ( |
…leaner Report (#746) Promote `develop` to `main`, carrying two changes: - #744 Host the Merge-Bot in the Hub and Measure Fleet Workflow Reuse: the hub-hosted reusable-workflow design (`docs/reusable-workflows.md`), the fleet workflow-reuse measurement (`spec/workflow_reuse.py`, `reports/workflow-reuse.md`), the first hub task (`.github/workflows/merge-bot-task.yml`) with the hub's own caller stub, the manifest contract change for `merge-bot-pull-request.yml`, and the TODO cluster and adoption sweep. - #739 Mark PhotoCleaner Operational After the Promotion of the b09078e Resync: the PhotoCleaner audit report refresh. The release that follows this promotion is the first tag naming `merge-bot-task.yml`, which is the pin the downstream caller stubs use, so the merge-bot adoption sweep and the catalog snippet both wait on it. A Dependabot pull request against `main` after this merge is the `--merge` half of the live proof of the callee. Refs #521 (hub half shipped in #744, sweep half is the adoption). No issue closes on this promotion.
Follow-up to #723 after ptr727/PhotoCleaner#51 promoted
developtomain(f56178a), carrying ptr727/PhotoCleaner#50 and ptr727/PhotoCleaner#52.spec/audit.py PhotoCleanerat hubb09078ereports clean atmain(audit run 2026-08-15T18:43:20Z | hub b09078e) and atdevelop, including the two hub-only workflow findings that #736 settled. The report moves to operational:readme-structureandagent-instruction-setto pass, no defects, no drift, nothing in flight. It records the one-rounddead-pathblock on the promotion (#721, fixed by #731, cleared by a re-run since the gate reads rules from hubdevelop) and closes both escalations (#721, #722). The registry entry is unchanged:statusstayscataloged(the schema's only non-backlog value) and bothdriftNotesstill describe reality (publish shape, private-for-now) and assert no outstanding work.Report lints clean (markdownlint, prose_lint), and
spec/validate.pypasses.🤖 Generated with Claude Code