Files

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

index.ts

Accounted rebrand + swarm-skill cleanup + bank-reconciliation fixes (#643 )

2026-06-03 10:52:01 +02:00

manifest.json

Add/white label (#381 )

2026-04-29 16:32:26 +02:00

README.md

style: remove em/en dashes repo-wide, add CLAUDE.md rule against them (#890 )

2026-07-04 15:58:06 +02:00

README.md

Example branding extension

Copy this folder to start a whitelabel fork:

cp -r extensions/general/_example-branding extensions/general/your-brand

Then:

Edit your-brand/manifest.json: set id, exportName, entryPoint, name, description.
Edit your-brand/index.ts: uncomment and set the branding values you want to override.
Drop your assets in your-brand/assets/ (logo.svg, favicon.ico, og.png, etc.). Wire up an extension API route to serve them, or set the asset paths in index.ts to external CDN URLs.

Enable the extension in extensions.config.json:

{ "id": "your-brand", "enabled": true }

Run npm run setup:extensions && npm run dev.

See WHITELABEL.md at the repo root for the full fork checklist (env vars, sync workflow, what NOT to change).

Why a separate extension instead of just env vars?

Both work. Env vars are simpler for scalar overrides (app name, support email). An extension lets you bundle assets (logos, icons) and override values that don't fit cleanly into env vars. You can use both: extension overrides win over env vars.