fix(seo): escape backslashes in llms-full.txt comparison table cells

[waleedlatif1]

Summary

• Escape backslashes before pipes in factCell so a fact value containing \ can't turn an escaped \| back into a column break in the /llms-full.txt comparison tables
• Resolves CodeQL js/incomplete-sanitization alert on apps/sim/app/llms-full.txt/route.ts

Type of Change

• Bug fix

Testing

bun run lint, bun run check:audits (53 audits), docs-manifest:check, type-check all pass; spot-checked the escaping in node (a\|b | c → a\\\|b \| c)

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 1, 2026 6:11pm UTC

[greptile-apps]

Confidence Score: 4/5

[Low risk] Fixes text escaping in a data export file.

The PR appears safe to merge, with a non-blocking regression-test gap for the escaping fix.

Findings

1.  Escaping Fix Lacks Test ▶

Summary

The PR escapes existing backslashes before pipes when formatting comparison facts for /llms-full.txt.

• This preserves pipe escaping when a fact contains both characters.
• The new escape case lacks a regression test.

_{Reviews (1) · Last reviewed commit: "fix(seo): escape backslashes in llms-ful..."}

[greptile-apps]

Escaping Fix Lacks Test The new backslash-escaping case has no regression test, and the current comparison facts do not exercise it. A test with a literal backslash immediately before a pipe should check that the output remains a three-column Markdown row; without one, a later change to the escape order could silently bring back the table break this PR fixes.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!