content/auto-draft

getToc does not handle tilde (~~~) code fences

apps/web/src/app/(marketing)/blog/[slug]/page.tsx

Fence-detection regex /^\s*```/ only toggles inFence on backtick fences. GFM/MDX also allows ~~~ fences. Headings inside a ~~~ block are not suppressed: they produce spurious TOC entries anchoring to non-existent IDs. Worse, slugger.slug() is called on them advancing the counter out of step with rehypeHeadingIds — all subsequent duplicate-named headings then get different numeric suffixes in the TOC vs rendered HTML, breaking anchors. Fix: if (/^\s*(```|~~~)/.test(line)) inFence = !inFence;

Heading text stripping incomplete for paired inline-code backtick spans

apps/web/src/app/(marketing)/blog/[slug]/page.tsx

`.replace(/[*`_]/g, '')` strips individual backtick characters but rehypeHeadingIds operates on rendered text nodes where inline-code is already unwrapped. In most cases this produces the same slug, but headings with MDX expressions could diverge, producing broken anchors.

TOC uses bare <a> for in-page anchors, inconsistent with rest of file

apps/web/src/app/(marketing)/blog/[slug]/page.tsx

In-page anchor hrefs (#id) don't trigger Next.js router navigation, so bare <a> is functionally correct. But the rest of this file uses <Link>. Minor inconsistency; not a defect.

Magic number 4 in `toc.length >= 4` undocumented

apps/web/src/app/(marketing)/blog/[slug]/page.tsx

Minimum heading count to display the TOC is unexplained. Extract to a named constant or add an inline comment: /* show TOC only for longer posts */.

getToc has no unit tests despite multiple real edge cases

apps/web/src/app/(marketing)/blog/[slug]/page.tsx

getToc is a pure function with real parsing edge cases: headings inside code fences, consecutive same-text headings (GithubSlugger dedup), inline-format stripping, ATX-only (setext headings silently ignored). None tested. Function is pure + dep-free, so tests are zero-setup — add a co-located getToc.test.ts.

No visual regression coverage for TOU.punta and callout color changes

apps/web/src/components/blog/charts.tsx

TOU.punta changed HELIOTROPE→VIOLET; two callout colors changed HELIOTROPE→AMBER. No snapshot or visual-regression tests exist for chart components. Color-correctness is permanently manual without coverage.

Dead `?? ""` fallbacks after guaranteed `.exec()` match

apps/web/src/app/(marketing)/blog/[slug]/page.tsx

After successful `.exec()` with required capture groups, m[1] and m[2] are always strings. The ?? "" guards are unreachable dead code. Remove them.

`hashes` variable only used for length — inline it

apps/web/src/app/(marketing)/blog/[slug]/page.tsx

Replace `const hashes = m[1] ?? ""; if (hashes.length === 2)` with `if (m[1].length === 2)` — removes unnecessary intermediate binding.

Inline className overrides on Button variant='cancel' reduce variant encapsulation

apps/web/src/app/(marketing)/blog/[slug]/page.tsx

className="font-medium text-foreground hover:bg-muted" overrides the cancel variant's own styles at every call site. If these are the intended styles, they belong in the variant definition; otherwise add a comment explaining why they diverge.