Scan a markdown copy wrapper wherever it sits - #4
Merged
Conversation
The outer-fence unwrap only fired when the ```markdown block was the entire draft, so a handoff message in real chat (a lead-in sentence, then the copy block) read the whole block as a code sample and skipped its prose. A fresh-context grader caught it against the acceptance bar that names that exact surface. extractProseLines now walks a fence stack following CommonMark's length nesting: a markdown/md fence opens a prose "wrapper" wherever it appears, any other fence opens a "code" region, and a bare fence of matching length closes. A real code fence inside a wrapper (handoffs use four backticks so three-backtick code nests) is still skipped. The old first-line/last-line whole-draft heuristic and its helper are gone; one code path, no drift. To skip a genuine markdown sample, fence it as plain code, not ```markdown.
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
1 participant
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.
Summary
```markdownfence is now scanned as prose wherever it appears, not only when it is the whole draft, so a handoff message with a lead-in sentence has its prose checked (the acceptance bar's named surface; a fresh-context grader disproved the old narrow behavior).Test plan
npm run checkgreen (matcher fixtures rewritten for the generalized semantics; the blocking jargon gate re-scanned all committed prose with no new hits)