2 Commits

Include renames

Author	SHA1	Message	Date
HomerandClaude Opus 5	a16510aba8	The interface speaks Slovak ... 969 strings, an instance default and a per-person choice, and no half-done corner: the admin prose is translated too. Design and reasoning: LLeMbas.wiki/Translations. KEYED BY THE ENGLISH SENTENCE A missing entry renders the key, which is the English -- so an untranslated string looks as it always did, an English instance is byte-for-byte 1.6.0, and a half-finished catalogue is a half-translated page rather than a page of dotted key names. The cost is that editing an English sentence orphans its translation silently, which is what tests/test_translations.py asserts in both directions. No gettext: .po -> .mo is a build step and this project does not have one. A JINJA GLOBAL, AND THEREFORE A CONTEXTVAR `t()` is a global for the reason `brand` already documents -- render() is bypassed by 25 TemplateResponse calls and 8 get_template().render() calls, the latter being the SSE frames, which have no Request at all. A global is bound once at import and the language is per person, so the active language is a ContextVar set per request. 🚨 `get_current_user` had to become `async def`. FastAPI runs a sync dependency in a threadpool, and anyio copies the context in and discards it on the way out -- so the language was set where nothing could see it and every page rendered in the instance's language whatever anybody had chosen, with no error anywhere. NOT TRANSLATED, ON PURPOSE Everything a model reads: the 60 prompt fragments, and the dates in harness.py, schedule/runner.py and schedule/compile.py. Only `i18n.stamp` is localised, and only where a person reads it -- with the *format* translatable as well as the words, because "26. septembra 2026" is a different pattern rather than the same one with different words in it. A process locale is not an option: global, not thread-safe, two people's pages at once. A second fragment telling models to answer in the reader's language was written during this work and removed: `core.style` has said it since long before, and test_an_empty_override_turns_a_fragment_off caught the duplicate. THE BULK PASS 1213 sites wrapped by a one-off script that only touched patterns it could not misread. It got three wrong in a way that mattered -- `t('…')` inside `attr="…"` where the sentence held an apostrophe, closing the Jinja string and 500ing two pages whose partials no test renders. tests/test_translations.py now compiles all 110 templates. It also wrapped the product's own name, an SSH key header, a keystroke hint and an example URL, all taken back out: a string is not translatable just because it is a string. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-26 14:46:33 +00:00
Jaroslav BenešandClaude Opus 5	1906919ee2	Every injected prompt becomes editable, and several get written ... The instructions LLeMbas puts in front of a model were hard-coded: six strings in a GUIDANCE dict, two headings, and the title request inline in chat.py. An operator could not see what was being sent, let alone change it, and there was nowhere for a custom tool to contribute its own guidance when custom tools land. services/prompts.py now holds each piece as a Fragment, and /admin/prompts edits them with a preview of the whole assembled system message including unsaved edits. harness.py keeps only the decisions -- which fragments apply to this request, and what their variables resolve to. The design turns on one choice: a fragment carries its gate as data (families, requires, when_tools) rather than as a callable, because a database row can carry the same three fields. Custom tools will therefore register a fragment source and change nothing else -- there is a test that says exactly that, and it is the reason the rest of the shape is what it is. Consequences worth knowing: - Defaults live in code, overrides in the database, and text equal to its default is never stored. Otherwise pressing Save once would freeze today's wording forever and no later release could improve it. - An empty override means off. A fragment that was not submitted at all keeps what it had, because it may be missing from the page only because whatever contributes it is currently switched off. - requires= replaced the hand-written pair of memory guidance variants. The sentence that refers to a section now lives inside that section, so it cannot outlive it. That was the general problem the pair was a special case of. - {{name}}, with anything unrecognised passing through verbatim. The name grammar is the guard: {"total": 1} and ${PATH} are not candidates. Substitution is one pass and never recursive, because {{memories}} carries text a model wrote. The wording is also overhauled, and a model now gets the core fragments even with no tools -- the date above all. "An empty harness is worse than none" was about tokens that say nothing; a model with no clock being asked about the present is not that. Clearing those boxes restores the old silence exactly. New: today's date, who it is talking to, the three-round tool budget, that tool results are not replayed, that anything a tool returns is data rather than instruction, and what the <document> wrapper around an attachment is. Extended: memory_forget, notes_edit/delete, skill_create/edit, and reading a knowledge document in full rather than answering from an extract. Tool descriptions stay in code and are listed read-only. They are schema and they state facts about what a runner does; an edit would make the text a lie with nothing to catch it. No schema change -- one JSON row in the settings table. 488 tests. Version 0.2.0, which also invalidates the service worker cache so the green artwork appears without a hard reload. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-07-31 23:47:49 +02:00