Development record
an indented code block in a committed issue record turns the site-render preflight gate red, and nothing on the capture path refuses one
an indented code block in a committed issue record turns the site-render preflight gate red, and nothing on the capture path refuses one
make preflight exits 2 on site-render for every checkout of build/itd-189
since 070e1bd0, which committed a record whose body indents a two-line sample of
gate output by four spaces. The site renderer reads a fixed subset of markdown
and refuses an indented code block, naming the fence as the remedy.
The record is the only one of the 928 in the ledger that carries the shape, so the immediate fix is one fence. The gap it exposes — that no gate reads a record body as markdown before the site render — is iss-2608301350287219.
Found while remediating the itd-189 round-2 findings; the record it sits in is unrelated to that work (it is the record-stores containment finding), and the fence lands without touching what the record says.
Frontmatter
| id | iss-2608301349335095 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608301349335095-an-indented-code-block-in-a-committed.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2608301350287219no gate reads a record body as markdown before the site render, so a construct the renderer refuses reaches the branch and turns preflight red at the far end
- itd-189What the widening reading proposes is admitted or declined on the record — grounds on admission, dispositions on declines, and surprises as their own entries