Skip to content

fix(blog): render the inline markup instead of showing it - #864

Merged
gHashTag merged 1 commit into
mainfrom
fix/inline-markup-rendered
Aug 22, 2026
Merged

fix(blog): render the inline markup instead of showing it#864
gHashTag merged 1 commit into
mainfrom
fix/inline-markup-rendered

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Readers were seeing the source. **Executed** and `zig build` reached production with their delimiters intact — the renderer emitted the raw string for paragraphs, list items, table cells, blockquotes and the open-questions list. Live on t27.ai across 13 pages before this.

The bodies were measured before choosing a fix: 31 bold spans, 123 code spans, and zero markdown links. Two forms cover the corpus, so this is a 20-line inline renderer rather than a markdown dependency.

A code block is deliberately untouched. One post quotes tool output that literally contains - **NOTE** purely combinational; inside a code span those asterisks are the data, and the alternation keeps them there.

Verification

Browser-checked against all 31 published posts: zero literal delimiters outside code, with a control confirming the check was not vacuous (6 rendered <strong> on the newest post).

An earlier version of that same check scraped links from a post page instead of the index, examined zero posts, and reported clean. That is precisely the vacuous pass this project keeps auditing other gates for, so it is named here rather than quietly fixed.

🤖 Generated with Claude Code

Readers were seeing the source. `**Executed**` and `` `zig build` ``
reached production with their delimiters intact -- the renderer emitted
the raw string for paragraphs, list items, table cells, blockquotes and
the open-questions list. Live on t27.ai across 13 pages before this.

The bodies were measured before choosing a fix: 31 bold spans, 123 code
spans, and ZERO markdown links. Two forms cover the corpus, so this is a
20-line inline renderer and not a markdown dependency.

A `code` BLOCK is deliberately untouched. One post quotes tool output
that literally contains `- **NOTE** purely combinational`; inside a code
span those asterisks are the data, and the alternation keeps them.

Verified in a browser against ALL 31 published posts: zero literal
delimiters outside code, with a control confirming the check was not
vacuous (6 rendered <strong> on the newest post). An earlier version of
that same check scraped links from a post page instead of the index,
examined zero posts, and reported clean -- which is the vacuous pass this
repository keeps auditing other gates for, so it is named here.
@gHashTag
gHashTag merged commit 2b0c49f into main Aug 22, 2026
27 of 33 checks passed
@gHashTag
gHashTag deleted the fix/inline-markup-rendered branch August 22, 2026 16:49
github-actions Bot added a commit that referenced this pull request Aug 22, 2026
fix(blog): render the inline markup instead of showing it (#864)

Readers were seeing the source. `**Executed**` and `` `zig build` ``
reached production with their delimiters intact -- the renderer emitted
the raw string for paragraphs, list items, table cells, blockquotes and
the open-questions list. Live on t27.ai across 13 pages before this.

The bodies were measured before choosing a fix: 31 bold spans, 123 code
spans, and ZERO markdown links. Two forms cover the corpus, so this is a
20-line inline renderer and not a markdown dependency.

A `code` BLOCK is deliberately untouched. One post quotes tool output
that literally contains `- **NOTE** purely combinational`; inside a code
span those asterisks are the data, and the alternation keeps them.

Verified in a browser against ALL 31 published posts: zero literal
delimiters outside code, with a control confirming the check was not
vacuous (6 rendered <strong> on the newest post). An earlier version of
that same check scraped links from a post page instead of the index,
examined zero posts, and reported clean -- which is the vacuous pass this
repository keeps auditing other gates for, so it is named here.
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.

1 participant