GeezerVison

The approach is right: fixing the generator and gating the result in docshtmlcheck, which already parses every page. I'm commenting rather than approving because of two issues, both inline. The rewritten port-forwarding table gives screen readers contradictory headers, and the new check misses   in Markdown cells.

What I verified:

• The new gate catches the problem. docshtmlcheck reports nothing on this branch and 1,559 empty header cells on the merge base (the body says 1,555). A test merge with current main is also clean, so no newly added CLI page breaks the gate.
• CLI pages: all 115 change by 1,444 lines added and 1,444 removed. After mapping Property | Value back to | | | and collapsing padding, every file is identical to main, so content is unchanged. The body could mention that body rows are re-padded too, not just header rows.
• scanNode refactor: I built main's checker and this one and ran both over all of docs/ plus a file of HTML errors. The non-table output is byte-identical.
• #30873 overlap: #30873 is still open, and the four shared hunks are byte-identical to it.
• Local runs: go test, go vet and golangci-lint on scripts/docshtmlcheck and scripts/clidocgen all pass.
• CI: gen and lint pass; gen regenerated the CLI docs with no diff, which covers the make gen caveat. The two failures are unrelated:
  • Storybook fails on userengagementchart--loaded, the same as the last four main runs. This PR touches no site/ files.
  • Documentation Updates timed out after 2400 s waiting for its agent.

One thing to acknowledge in the PR: every option on 115 pages now shows a visible Property | Value header row. That's a visual change on the docs site.

Generated by Coder Agents on behalf of @Jesswinters.

Re-reviewed at 2871f89. Every point from my first review is fixed, and I checked each by running it. I'd approve the code. I'm commenting rather than approving only because the branch now conflicts with main, so no ci.yaml job (gen, lint, lint-docs, Storybook) has run on this head. After a rebase, main also has a page that would fail the new check (details below).

Fixed:

• Entity decoding. |   |,  ,   and <th> +   between blocks are now reported. A code-span ` `, \  and   are correctly not reported.
• Image alt text. Alt text counts in every form: HTML, uppercase, self-closing, multi-line, pipe-cell and ![Logo](x). alt="", alt=" ", alt=" " and a missing alt are still reported as empty.
• Text between <th> blocks. An autolink or fenced code between <th> blocks counts as text. The nested-table case is documented under Limitations.
• Checker output. issueCounts reports per kind, stale-allowlist findings sort last, and the note on CLI pages now points at scripts/clidocgen/command.tpl.
• Port-forwarding table. By the HTML header algorithm, and confirmed with axe's own getHeaders, "Alice" now gets only "To user". The ✅/❌ cells get both column and row headers. <th scope="row"> in thead is valid, and it's what stops the "From" cells being treated as column headers. axe 4.13 passes empty-table-header, td-has-header, th-has-data-cells, scope-attr-valid and td-headers-attr. The caption matches the layout.
• Style guide and styleclaims. The Tables rule, footer, Tool column, Makefile and README wording are updated. The styleclaims change is needed (without it, the new footer wouldn't count as a tool citation), it mirrors how check_emdash.sh is handled, and it has tests.

Local runs: go test, go vet and golangci-lint on docshtmlcheck, clidocgen and styleclaims; go run ./scripts/docshtmlcheck (exit 0); go run ./scripts/styleclaims (exit 0); Vale, markdownlint and the table formatter on the changed docs. All clean. I also ran 32 adversarial inputs against the checker, and each matched axe or the documented limits.

Before merge (rebase):

1. README counts. #30782 changed the same lines in docs/.style/style-guide/README.md: 88 rules, the coverage table, and the line 92 sentence. I resolved the conflict in a scratch copy, and these values pass styleclaims:
   • The rules count is 88: "checks 10 of them, and 1 of those 10", "The other 78 … 79 on published pages".
   • The Formatting row is 13 | 3 | 0 | 10, and Total is 88 | 10 | 34 | 44.
   • The line 92 sentence becomes "So the 8 rows in the table above name 11 checks, because the markdownlint row bundles 4, and those 11 checks cover 10 sections".
2. New CLI page. main added docs/reference/cli/ai-gateway/keys/create.md with the old | | | header (line 21). Please re-run make docs/reference/cli/index.md after rebasing, or lint/docs-html and gen will fail.

#30873 is still open, and git merge-tree shows it merges cleanly with this branch in either order. One optional wording nit is inline.

Generated by Coder Agents on behalf of @Jesswinters.

Re-reviewed at 4a7913cb3a, the merge of main that cleared the conflict from my last review. Approving: I found no blockers.

The merge resolution is correct. The only real conflict was the style guide's coverage counts, and the resolved table adds up: 88 rules, 10 tool-checked, 34 planned and 44 documentation-only, with the prose saying 78 by reading (79 on published pages), which matches. The other overlapping files merged cleanly, and the CORS matrix fix and the four corner cells shared with #30873 are intact. The one CLI page main changed (ai-gateway/keys/create.md) carries the new Property | Value header, and the gen job confirms it matches the generator.

Every CI job passes on this head, including gen, lint, lint-docs, check-docs, offlinedocs and required. Locally, go test passes for scripts/docshtmlcheck, scripts/clidocgen and scripts/styleclaims. go run ./scripts/docshtmlcheck and go run ./scripts/styleclaims both exit 0 on the merged tree, so nothing main brought in has an empty header cell.

There is one non-blocking nit, inline.

Generated by Coder Agents on behalf of @Jesswinters.