Cogeto/cogeto

Cogeto is a self-hosted verified-memory system; its contributor docs cover the full check suite well, but they never document the fast loops a contributor actually lives in. Three gaps, all documentation-only: Running one test file. The only documented command is npm run test, which fans out over three workspaces; the backend workspace alone has ~194 spec files, runs with fileParallelism: false and 180-second timeouts, and many suites start real containers (see project/src/vitest.config.ts). Nothing anywhere says the escape hatch: cd project/src && npx vitest run path/to/thing.spec.ts. docs/running-locally.md even warns against running bare vitest from the repo root without saying what to run instead. Grep confirms no doc mentions npx vitest. The frontend test convention. project/web has no vitest config; browser-flavoured specs work only because each starts with a // @vitest-environment jsdom docblock (first line of project/web/src/components/nav.spec.tsx). A newcomer adding a compon

Ce ticket s'adresse aux francophones. Cogeto is a self-hosted verified-memory system whose interface ships fully translated French; this issue is one terminology fix in the fr locale, best done by a native speaker. The per-locale glossary in docs/features/i18n.md (terminology section) fixes the translation of "scope" as portee, and most of the interface follows it (fr/memories.json:81, fr/sources.json:24,311). But one cluster says perimetre instead: project/web/src/locales/fr/reports.json:6 (run.scopeLabel = "Perimetre") and fr/reports.json:37 project/web/src/locales/fr/connections.json:89,95 project/web/src/locales/fr/serverErrors.json keys at lines 38, 43, 44, 157, 163, 164 (including "sous-perimetre") So the same concept is named differently on the reports surface and in server error messages than everywhere else a user meets it. Done looks like: Every listed value uses the glossary term (portee / sous-portee), with each sentence adjusted so it still reads naturally. A quick gr

Dieses Issue ist fuer Deutschsprachige. Cogeto is a self-hosted verified-memory system whose interface ships fully translated German; this issue is terminology consistency in the de locale, best done by a native speaker. Locale files: project/web/src/locales/de/*.json and project/src/infrastructure/locales/de/*.json. The binding per-locale glossary is in docs/features/i18n.md (terminology section). Three core terms are each translated two ways: receipt: Beleg vs Quittung. The glossary says Beleg, and de/forgotten.json uses it consistently (Beleg, Belege, Loeschbeleg), but de/users.json:51-52,60 says "signierte Quittung" / "Die Quittungen ... ansehen". A deletion receipt is a legal-ish artifact here; the user should meet one word for it everywhere. sensitive: vertraulich vs sensibel. The glossary says vertraulich. de/sources.json:300,330 and the server-side project/src/infrastructure/locales/de/report.json:92 use it correctly, but de/sources.json:25, de/common.json:44 (the badge itself

Ovaj je issue za govornike hrvatskoga. Cogeto is a self-hosted verified-memory system whose interface ships fully translated Croatian; this issue is terminology and grammar cleanup in the hr locale, best done by a native speaker. Locale files: project/web/src/locales/hr/*.json and project/src/infrastructure/locales/hr/*.json. The binding per-locale glossary is in docs/features/i18n.md (terminology section). "scope" is translated two ways. The glossary mandates doseg, but opseg appears 19 times against 13 for doseg. Examples: hr/reports.json:6 ("Opseg"), hr/memories.json:81, hr/sources.json:14 ("opseg: {{scope}}") versus the glossary-correct hr/sources.json:311 ("Doseg sjecanja za ovaj uvoz"). Converge every occurrence on the glossary term, adjusting case endings to fit each sentence. Declension error. hr/users.json:67: "Pogledajte potvrde u Zaboravljeno" drops the nominative nav label into a sentence needing the locative: "u Zaboravljenom". The correct construction already exists at h

In Cogeto's chat view, the component that renders an answer's citation chips rebuilds its lookups by linear scan for every chip, on every render, and the render runs per streaming token: project/web/src/pages/Chat.tsx:152-183 (MessageBody citation grouping): factFor does facts?.find(...) per lookup, documentOf layers citedIds.indexOf(id) on top, and numberOf runs documents.findIndex(...) per rendered chip, re-running documentOf (and therefore factFor) each time. A code comment in that area records a real answer citing 52 facts from one source, so the quadratic-to-cubic cost is not hypothetical, and it is paid repeatedly while an answer streams in. Why it matters: answer streaming is the hottest render path in the product. Replacing the scans with maps built once per input change makes the per-chip work O(1) without touching what is rendered. Done looks like: Lookups by memory id, cited-id order and document number come from Maps (built once per change of facts / citedIds / resolved