Conversation
…files Fixed non-standard closing fences where ```text (or similar) was used to close ```go, ```yaml, and other language code blocks. CommonMark spec requires closing fences to have no info string. Files fixed: code-organization.md (2), validation-architecture.md (18), actions.md (11), safe-output-messages.md (33), github-actions-security-best-practices.md (34), and 15 others. Total: 175 closing fence fixes across 20 scratchpad spec files. Updated dev.md to v3.1 with change history entry. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Author
|
Commit pushed:
|
pelikhan
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Comprehensive formatting fix for non-standard code fence closing markers found across 20 specification files in
scratchpad/.Problem
The [CommonMark spec]((spec.commonmark.org/redacted) requires that closing code fences have no info string. A line like
```textused as a closing fence is technically invalid becausetextis an info string. While GitHub's renderer may tolerate this, it creates inconsistency and may cause rendering issues in other markdown tools.Example of the problem found throughout spec files:
Should be:
Changes Made
Fixed 175 non-standard closing fences across 20 spec files:
scratchpad/github-actions-security-best-practices.mdscratchpad/safe-output-messages.mdscratchpad/string-sanitization-normalization.mdscratchpad/mcp_logs_guardrails.mdscratchpad/actions.mdscratchpad/security_review.mdscratchpad/go-type-patterns.mdscratchpad/end-to-end-feature-testing.mdscratchpad/firewall-log-parsing.mdscratchpad/template-injection-prevention.mdscratchpad/mods/jsonschema-go.mdscratchpad/validation-architecture.mdscratchpad/schema-validation.mdscratchpad/breaking-cli-rules.mdscratchpad/changesets.mdscratchpad/testing.mdscratchpad/safe-output-environment-variables.mdscratchpad/gosec.mdscratchpad/code-organization.mdscratchpad/capitalization.mdAlso updated
scratchpad/dev.mdto version 3.1 with a change history entry.Validation
```textclosing fences that were closing blocks opened with non-text language tags```markdowndocumentation examplesReview Notes
Each changed line was exactly
```text→```(or the appropriate bare closing fence). No code content was modified. The fix is purely syntactic conformance to the CommonMark specification.References: §22421430881
✨ PR Review Safe Output Test - Run 22422877284