Skip to content

Apply PhotoCleaner round-2 feedback: rationale wording, MD033 clarity, CPM property owner - #408

Merged
ptr727 merged 3 commits into
developfrom
round2-feedback
Jul 23, 2026
Merged

Apply PhotoCleaner round-2 feedback: rationale wording, MD033 clarity, CPM property owner#408
ptr727 merged 3 commits into
developfrom
round2-feedback

Conversation

@ptr727

Copy link
Copy Markdown
Owner

Three actionable items from the PhotoCleaner round-2 convergence (ptr727/PhotoCleaner#14 round-2 comment), adopting the downstream wording where offered.

  1. configure.sh rationale — reworded so it no longer reads as a run-on (two sentences, the shell option backticked), still terse.
  2. MD033 clarity — the explicit form (PhotoCleaner PR Update README and improve setup instructions #18): "HTML comments are permitted (markdownlint does not flag them), HTML elements are flagged, and anything with a native markdown equivalent uses the markdown". The earlier "allowed in comments only" could read as "elements allowed inside comments".
  3. CPM property owner — CODESTYLE now says Directory.Packages.props owns ManagePackageVersionsCentrally explicitly (in that file, not Directory.Build.props), and a README TODO records the fleet sweep: PlexCleaner sets it in Directory.Build.props, off canonical.

No hub change for the other two: item 2 (stale round-2 snapshot at pickup) — the AUDIT.md re-verify-before-acting rule caught it downstream, as designed; item 3 (CPM section reads as present-state mid-convergence) — inherent to carrying a standard before adopting it, the block is already prescriptive.

Verification

validate.py green, shellcheck clean, markdownlint clean, CRLF/LF preserved, no em-dash.

🤖 Generated with Claude Code

…, CPM property owner
Three items from the round-2 convergence (PhotoCleaner#14), adopting the downstream wording:
1. configure.sh cmd_apply rationale reworded so it no longer reads as a run-on - two sentences
with the shell option in backticks, still terse.
4. MD033 note made explicit (PhotoCleaner's PR #18 form): HTML comments are permitted
(markdownlint does not flag them), HTML elements are flagged, and anything with a native
markdown equivalent uses the markdown - the earlier "allowed in comments only" could read as
"elements allowed inside comments".
5. CODESTYLE now states Directory.Packages.props owns ManagePackageVersionsCentrally
explicitly (in this file, not Directory.Build.props), and a README TODO records the
fleet-consistency sweep - PlexCleaner sets the property in Directory.Build.props, off canonical.
Item 2 (stale round-2 snapshot at pickup) needs no hub change - the AUDIT.md re-verify-before-
acting rule caught it downstream, exactly as designed. Item 3 (CPM section reads as present-
state mid-convergence) is inherent to carrying a standard before adopting it; the block is
already prescriptive and the transient clears once the repo adopts CPM.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR incorporates round-2 PhotoCleaner feedback by tightening rationale wording in configure.sh, clarifying the intent of markdownlint MD033 guidance, and making CPM ownership explicit in the .NET style section.

Changes:

  • Reworded repo-config/configure.sh apply-path rationale comment for clarity.
  • Clarified MD033 expectations in CODESTYLE.md (HTML comments vs HTML elements, prefer native Markdown).
  • Documented CPM ownership more explicitly in CODESTYLE.md and added a fleet sweep TODO in README.md.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

FileDescription
repo-config/configure.shAdjusts explanatory comment around write behavior and validation flow.
README.mdAdds a TODO item tracking a fleet-wide CPM-property placement sweep.
CODESTYLE.mdClarifies Markdown linting guidance (MD033) and CPM property ownership in .NET conventions.

Comment threadrepo-config/configure.sh Outdated
…rites
The probe reads run inside `if` conditions and are exempt from set -e, so "aborts on any
non-zero exit" overstated it. The rationale now says a failed write aborts the script because
these writes run unguarded, which is the property that actually holds.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
CopilotAI review requested due to automatic review settings July 23, 2026 17:35

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

repo-config/configure.sh:125

  • Comment grammar: "fail loud" should be "fail loudly".
 # The writes below silence stdout only (the success-response JSON is noise). They still fail loud -
# gh errors go to stderr and a failed write aborts the script (these writes run unguarded under `set -e`).

The programmatic insertion left the new backlog bullet ending in LF while README.md is CRLF,
which editorconfig-checker rejects. Restore CRLF on that line.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
CopilotAI review requested due to automatic review settings July 23, 2026 17:40

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

repo-config/configure.sh:125

  • Comment grammar: "fail loud" reads ungrammatical here (and earlier review asked for "fail loudly"). Consider switching to the adverb form for clarity.
 # The writes below silence stdout only (the success-response JSON is noise). They still fail loud -
# gh errors go to stderr and a failed write aborts the script (these writes run unguarded under `set -e`).

@ptr727
ptr727 merged commit 6f21ce9 into developJul 23, 2026
7 checks passed
@ptr727
ptr727 deleted the round2-feedback branch July 23, 2026 17:45
ptr727 added a commit that referenced this pull request Jul 23, 2026
…fixes (#410)
Carries #408 (PhotoCleaner round-2), #409 (finmod rounds 1-2 write-safety carve-out + configure.sh guards), #411 (check-mode ruleset_id guard), #412 (DSC verbatim semicolon sweep). Merge commit, no release.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ptr727