Files
accounted/app/llms-full.txt/route.ts
T
Jakob WennbergandClaude Sonnet 5 ec27228a8e style: remove em/en dashes repo-wide, add CLAUDE.md rule against them (#890)
Em dashes (—) and en dashes (–) had spread across comments, docs, tests,
and a few UI strings, reading as AI-generated boilerplate rather than
house style. Replaced each with punctuation matching its context: colon
for explanatory clauses, comma for asides, plain hyphen for numeric/legal
ranges (e.g. "21-23§"), "to"/"till" for date ranges, parentheses for
paired-dash asides. messages/en.json and messages/sv.json were fixed by
hand together to keep sv/en in sync.

Left untouched where the dash is the functional subject rather than
decorative punctuation: date-range-parser.ts's separator regex,
charset-repair.ts's CP1252 byte-mapping table (and its test), the SIE
encoding mojibake docs, generic-csv.ts's minus-sign normalizer, the
agent system-prompt files that already instruct against em dashes, and
a golden iXBRL test fixture compared byte-for-byte.

Also fixes two bugs surfaced along the way: an off-by-one in
ApiKeysPanel's scope-label split (a leftover from an earlier partial
pass), and a charset-repair test that had lost the literal en-dash it
exists to verify.

Regenerated the agent atom seed migration (skills:generate) since 27
SKILL.md files changed. Added a CLAUDE.md rule against em/en dashes,
with an explicit carve-out for the functional-dash cases above.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-04 15:58:06 +02:00

60 lines
1.9 KiB
TypeScript

/**
* /llms-full.txt: full docs concatenated for LLM ingestion.
*
* Sibling to /llms.txt (which is the concise discovery index). This is the
* "ingest the whole thing in one HTTP call" surface: agents that need
* deep context can fetch this once and parse instead of crawling every
* /docs/api/*.md page individually.
*
* Concatenates: landing → versioning → webhooks concept → errors →
* reference overview → every per-resource reference → quickstart cookbook
* → webhooks cookbook → changelog. Section separators are `---` so a
* downstream Markdown parser sees them as horizontal rules.
*/
import { NextResponse } from 'next/server'
import { LANDING_MD } from '@/lib/docs/content/landing'
import { VERSIONING_MD } from '@/lib/docs/content/versioning'
import { WEBHOOKS_MD } from '@/lib/docs/content/webhooks'
import { CHANGELOG_MD } from '@/lib/docs/content/changelog'
import { buildErrorReferenceMd } from '@/lib/docs/content/errors'
import { buildReferenceOverviewMd, buildResourcePages } from '@/lib/docs/content/reference'
import { COOKBOOK } from '@/lib/docs/content/cookbook'
import { withPublicSecurityHeaders } from '@/lib/api/v1/security-headers'
function joinSections(sections: string[]): string {
return sections.map((s) => s.trim()).join('\n\n---\n\n')
}
function build(): string {
const sections: string[] = [
LANDING_MD,
VERSIONING_MD,
WEBHOOKS_MD,
buildErrorReferenceMd(),
buildReferenceOverviewMd(),
]
for (const page of buildResourcePages()) {
sections.push(page.markdown)
}
for (const recipe of COOKBOOK) {
if (recipe.markdown) sections.push(recipe.markdown)
}
sections.push(CHANGELOG_MD)
return joinSections(sections)
}
export async function GET() {
return new NextResponse(build(), {
status: 200,
headers: withPublicSecurityHeaders({
'Content-Type': 'text/markdown; charset=utf-8',
'Cache-Control': 'public, max-age=300, s-maxage=300',
}),
})
}