Skip to content

Sweep clause-splicing semicolons from the verbatim AGENTS sections - #412

Merged
ptr727 merged 1 commit into
developfrom
dsc-verbatim-semicolon-sweep
Jul 23, 2026
Merged

Sweep clause-splicing semicolons from the verbatim AGENTS sections#412
ptr727 merged 1 commit into
developfrom
dsc-verbatim-semicolon-sweep

Conversation

@ptr727

@ptr727 ptr727 commented Jul 23, 2026

Copy link
Copy Markdown
Owner

From finmod's round-3 promotion-review feedback: Copilot keeps surfacing DSC style violations one instance per review, a different verbatim section each time. Per the fleet's own flag-an-instance-fix-the-class rule, sweep all three verbatim sections at once.

  • Five clause-splicing semicolons recast across Git and Commit Rules and Verification Discipline (two were in Verification Discipline, which round-2 fixed only at the flagged line - the class-miss this rule exists to catch). No non-ASCII remained; Repository Boundaries and Write Safety had none.
  • Colon declined as a false positive. The DSC bans the semicolon splice, not colons; there is no colon rule in the repo. The round-3-flagged colon introduces an explanation of the preceding clause (standard usage). Clarified in the DSC (non-verbatim) that a colon introducing an explanation, list, or elaboration is not a splice, so downstream can dismiss the recurring Copilot colon flag.

Re-vendors Git and Commit Rules and Verification Discipline; folds into the in-flight develop->main promotion so the verbatim sections re-vendor once.

Copilot has been surfacing DSC style violations one instance per review, a
different verbatim section each time (round-2 caught one Verification Discipline
semicolon, this promotion caught another). Per the fleet's own flag-an-instance-
fix-the-class rule, sweep all three verbatim sections at once instead: five
clause-splicing semicolons recast across Git and Commit Rules and Verification
Discipline (two of them the round-2 instance-fix had missed). No non-ASCII
remained.

Also clarify in the Documentation Style Conventions (non-verbatim) that the ban
is on the semicolon splice only - a colon introducing an explanation, list, or
elaboration keeps its standard use - so a colon-for-explanation is not mistaken
for a splice.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 23, 2026 20:29

Copilot AI 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

Sweeps clause-splicing semicolons from vendored/verbatim sections of AGENTS.md to align with the repo's documented prose rule, and clarifies that colons introducing explanations/lists are not part of the semicolon-splice ban.

Changes:

  • Recasts clause-splicing semicolons in Git and Commit Rules into period/comma/conjunction forms.
  • Recasts clause-splicing semicolons in Verification Discipline to avoid semicolon splices while preserving meaning.
  • Extends the semicolon-splice rule text to explicitly allow colons used for explanations/elaboration/lists.

@ptr727
ptr727 merged commit 7828a78 into develop Jul 23, 2026
7 checks passed
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.
@ptr727
ptr727 deleted the dsc-verbatim-semicolon-sweep branch July 23, 2026 21:36
Sign up for free to 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