[ptr727]

Summary

The prose gate's Markdown rules blanked code spans and quotations across a whole table row before any cell split. So a cell boundary inside either one was lost.

• markdown-it-py ends a cell at an unescaped pipe inside a code span. Blanking the span first merged those two cells, and a comma in the first then excused a semicolon list in the second.
• An unpaired " in one cell, such as an inch mark, paired with a quote in a later cell. Every cell between them was blanked, so no rule read them.

The semicolon rule is the one the issue names. A local review pass found the same defect class in the dash, dupword, spelling, and dead-path rules, all in the same file, so every site moves onto one helper here.

Changes

• .github/actions/prose-gate/prose_lint.py:
  • TABLE_ROW and row_cells split a row opening with a pipe, blockquoted or not, at each pipe no backslash escapes.
  • by_cell applies a blanker one cell at a time and rejoins the cells, so every pipe that ends a cell stays where it was.
  • prose_lines, unit_texts, and the dead-path code-span and link scans each go through it. rule_semicolon reads the blanked row from prose_lines as before.
• tests/test_prose_lint.py: both of the issue's cases for the semicolon rule, a quotation inside one cell still blanked, the unpaired-quote case for dash, dupword, and spelling, a code span across cells for dash, and two dead-path cases.
• scripts/README.md: states that a row opening with a pipe is blanked a cell at a time, and why.

Verification

• The issue's repro now reports four semicolon violations, two on each body row, and reported none before. The issue says five. Counting the cells it names gives four: e; f; g holds two semicolons and a; b; c holds two.
• The prose gate suite passes, 640 tests. Every new test fails against the base rule_semicolon and blanking code.
• A whole-tree prose gate run is unchanged, with no violations before or after.

Local Review

Three recorded local-strict-review passes.

• The first raised that the fix covered only the semicolon rule while the other rules shared the defect. Fixed by the shared helper.
• The second raised a second row check in rule_semicolon, a code-span token scan in dead-path still reading the whole row, and docs wider than the code for rows with no leading pipe. All three were fixed.
• The third raised one finding, that rule_semicolon still split a row itself beside row_cells. That push's edit budget was spent, so it went out listed as open and was fixed on the next push, which now calls row_cells.
• The fourth, over that push, raised nothing.

Closes on promotion: #3657

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: ptr727/ProjectTemplate
• Branch: feature/auto-3657
• File: .coderabbit.yaml
• Commit: d0f758c
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: c17e35b3-e1d5-411c-a045-b612d06e59d0

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ptr727]

A recorded local strict-review pass covers head 3c2e2ad44c653f02725f1a37237ea406be2324bf, the content this pull request carries at that commit against develop, and it recorded 1 finding.

[Copilot]

🟡 Changes recommended

A moderate active finding remains because the semicolon parsing path duplicates shared cell-boundary logic and handles edge pipes inconsistently instead of reusing row_cells.

1 open issue

• Reuse row_cells for consistent semicolon splitting · New

What changed in this PR

This pull request fixes Markdown table-cell boundary handling in the prose gate by splitting rows before blanking code spans and quotations. The correction is applied across related prose and dead-path rules, with regression tests and documentation updates.

Changes:

• Adds shared row_cells and by_cell helpers for cell-aware processing.
• Updates semicolon, dash, duplicate-word, spelling, and dead-path checks.
• Adds regression coverage for table boundaries, quotations, code spans, and deleted paths.
• Documents cell-by-cell blanking behavior.

File	Summary
tests/​test_prose_lint.py	Adds regression coverage for affected table-cell, quotation, code-span, and dead-path cases.
scripts/​README.md	Documents cell-aware processing for pipe-opening Markdown table rows.
.github/​actions/​prose-gate/​prose_lint.py	Adds shared table-cell processing and applies it across affected rules. Open findings: reuse row_cells in rule_semicolon (P2, 4 votes) and clarify the row_cells docstring (P3, 1 vote).

This pull request requires changes.

_{Review effort: Lite}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.70%. Comparing base (b38e084) to head (d0f758c).
⚠️ Report is 28 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3660      +/-   ##
===========================================
+ Coverage    81.60%   81.70%   +0.09%     
===========================================
  Files           26       26              
  Lines         9070     9119      +49     
===========================================
+ Hits          7402     7451      +49     
  Misses        1668     1668              

Flag	Coverage Δ
python-3.13	81.70% <ø> (+0.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ptr727]

A recorded local strict-review pass covers head d0f758c356d961d1c0482d2249186fc3266c98b1, the content this pull request carries at that commit against develop, and it recorded 0 findings.