1802 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	55f0f96016	feat(6854): the server says which project a pending act would change, and whether this session may do it ... GET /api/plugin/write-scope answers the plugin's fence. The session's project comes from repo / project_id, as every plugin endpoint reads it. The act is either: - a directory (target_repo / target_project_id), for a file edit or a git command; or - an MCP call (tool, plus input: the call's short arguments). It returns allowed, the other projects the act would change, and the reason the operator is asked. It is a GET so a read-scoped key still fences file edits and git. services/write_scope.WRITE_TARGETS lists every write tool with the arguments that locate its write: a project id, or a task, note, milestone, System, rule, relation, trash batch, repo or family decision, each traced to its project. A write that lands in no project (install settings, user-level records, the judgments a session is asked for anywhere) has an empty entry. The one cross-project write allowed is create_task(kind="issue") as a new, unplanned, open issue. A project the caller cannot read is never named. tests/test_write_scope.py: - requires an entry for every write tool; - requires every declared argument to exist on the tool; - refuses a locating argument (project_id, task_id, milestone_id and the rest) that a write tool takes without declaring it. The integration test traces each locator from real rows. Milestone 583, step 2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 21:39:03 -05:00
bvandeusenandClaude Opus 5.5	373f5bd454	feat(6839): the decision log and the knowledge feed load as you scroll, through one ScrollSentinel ... ScrollSentinel sits at the foot of a server-paged list and asks for the next page a screen before the reader reaches it. It asks once per cursor, forgets the cursor when its element goes, and shows Try again on a failed page instead of retrying in a loop. FamilyView's decision log loses its "Older decisions" button. A failed page shows in place rather than as a toast, and rows already shown are skipped when a new decision shifts the offset. KnowledgeView drops its inline IntersectionObserver for the component. The cursor is the ids consumed, not the items rendered, so a batch that returns fewer records than it asked for still moves the feed on. A failed batch puts its ids back and offers Try again, where it used to fail silently and stop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 20:14:41 -05:00
bvandeusenandClaude Opus 5.5	846c87629f	test(6849): the restore command previews without --yes and rolls back from the tar with it ... Two integration tests in test_integration_backup_rollback.py drive grimoire.restore.run on the scheduled backup's tar, written from a full export of this instance: - without --yes it exits 4 and nothing changes; - with --yes it takes the safety backup, then puts back the edited and the deleted task and removes the new one. The file-restore test that expected a refusal "because the database has accounts" now names the reason it actually refuses: on a live instance, a backup that records no instance id can't be rolled back to. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 20:12:30 -05:00
bvandeusenandClaude Opus 5.5	37be3b0bff	feat(6849): the command-line restore uses the same rollback, and the docs say how restore works now ... python -m grimoire.restore <file> prints what the restore would change (the same preview as Settings) and stops. With --yes it runs backup_job.rollback_to_backup: the current state is saved first, then the whole instance goes back to the backup. An empty instance takes any full backup. A live one only takes a backup of its own, and otherwise exits 3 with the reason. A v1 backup keeps the copy-in path into an empty instance. docs/backups.md Restoring is rewritten: - what a restore puts back and removes; - the same-instance rule; - the safety backup; - what survives; - the web and command-line ways in. Its S3 key advice now asks for read as well as write when restoring from the bucket. README, features, architecture and the API reference follow. Milestone 582, step 5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 20:08:31 -05:00
bvandeusenandClaude Opus 5.5	1f5e963c35	feat(6848): Settings restore rolls back, from the destination or a file, after a preview ... The web restore no longer copies a backup in beside the live data. - GET /api/admin/restore/sources lists the backups at the backup destination, newest first. - POST /api/admin/restore/preview says what a restore would do, changing nothing: fresh or rollback, when the backup was taken, and counts now and after per kind. A backup that cannot apply here gets a 409 with the reason. - POST /api/admin/restore?confirm=rollback runs backup_job.rollback_to_backup: safety backup, replace, then search rebuilt in the background. Each takes ?source=<name> (a backup at the destination) or an upload. The destination path exists because uploads are held to the request-size limit, and a real instance's backup is far over it. backup_s3.get_file downloads from a bucket. backup_destination.list_backups/open_backup only accept names the scheduled backup writes, so a request cannot reach any other file. Settings -> Data -> Restore from Backup opens RestoreBackupDialog. The dialog: 1. Pick a backup at the destination or a file. 2. Read the preview. 3. Type "roll back". 4. Run it. The dialog then says where the replaced state was saved, and sends the user to sign in again. Closes #6840. Milestone 582, step 4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 20:06:07 -05:00
bvandeusenandClaude Opus 5.5	34f8d7060b	feat(6847): a rollback first backs up the state it replaces ... backup_job.rollback_to_backup: 1. Checks the backup can apply here (backup.check_replace, which shares _replace_mode with replace_from_backup), refusing before anything is written. 2. Takes the backup lock, so no scheduled backup runs during the rollback. 3. Saves the current store with save_state_before_restore. 4. Replaces the store. The safety file goes to the backup destination when backups are on and it takes it. Otherwise it goes to DATA_DIR/pre-restore, with a note when the destination refused. If neither takes it the rollback does not run. The result names where the file went. Milestone 582, step 3. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 20:02:26 -05:00
bvandeusenandClaude Opus 5.5	8806ab85b4	feat(6846): replace_from_backup rolls the store back to a full backup by id ... One transaction: - Refuse unless the backup is a full one and, on a live instance, carries this instance's id. A fresh instance (no records, at most the restoring account) takes any full backup and adopts its id. - Clear first: search vectors and the CSS consumer map (derived); every backed-up table nothing outside the backup points at, whole; the settings the backup carries; and the identity-table rows the backup lacks. A share granted by a removed user goes before the user. - Write the backup through the same _build_* helpers as the copy-in restore, now _load_v2(keep_ids=...). Identity tables (users, projects, milestones, notes, rulebooks, topics, rules, systems, design systems, code shapes, family decisions) go through _place. That keeps the backup's id and merges, so API keys, shares and forge connections of a surviving row stay. - Reset id sequences past the restored max, and sign every session out. reindex_after_restore runs the four embedding backfills afterwards. A unit guard checks that no row kept for outside references cascades from a table replaced whole. Integration tests cover edits, deletions and new rows put back, a surviving API key, sessions ending, fresh ids afterwards, foreign or id-less backups refused, a user export refused, a failure part-way changing nothing, and a fresh instance adopting the id. Milestone 582, step 2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 19:59:48 -05:00
bvandeusenandClaude Opus 5.5	6d8db0bb65	feat(6845): every instance has an id lineage, and every full backup carries it ... instance_identity is one row made by migration 0127 with a random id, so an instance has it before its first account. A full backup carries it in its header as instance_id (the tar manifest header and the JSON top level); BACKUP_VERSION is 28. The table rides in _NOT_INCLUDED: a restore decides from the header value rather than copying a row. Two stores with the same id number their rows the same way. That is what lets a later step roll a live instance back by original id, refuse a backup whose ids would land on unrelated rows, and have a fresh-instance restore adopt the backup's id (adopt_instance_id). Milestone 582, step 1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 19:53:45 -05:00
bvandeusenandClaude Opus 5.5	3c01e17559	test(6838): give the test request its socket peer the way Quart reads it ... Quart takes remote_addr from a Remote-Addr header its ASGI layer writes from the scope (replacing any the client sent). A test request context does not read scope_base for it, so the two socket-peer tests saw an empty address. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 19:37:28 -05:00
bvandeusenandClaude Opus 5.5	dbd6d5b8b5	feat(6838): read the client address and HTTPS from the trusted proxy hop ... grimoire/proxy.py is the one reader of X-Forwarded-For and X-Forwarded-Proto. It takes the entry TRUSTED_PROXY_HOPS in from the right (default 1; a shorter header reads its leftmost entry; 0 trusts no proxy), so an entry a client puts left of the proxy's is never believed. Before this, with TRUST_PROXY_HEADERS on, the leftmost X-Forwarded-For entry keyed the login, register, forgot and reset rate limits and the audit log, and a client could choose it. The session cookie is Secure, and HSTS (max-age=31536000) is sent, exactly when the request is HTTPS by the trusted proxy's word. Plain HTTP is untouched and nothing redirects. SECURE_COOKIES is gone (a startup warning says so when it is still set); TRUST_PROXY_HEADERS=false still maps to 0 hops, with a warning to move to TRUSTED_PROXY_HOPS. Admin audit lines now use the same client address instead of the socket peer. The placeholder-key refusal keyed on SECURE_COOKIES, so it now refuses either placeholder key outright; the instance makes its own key when none is set. Family idea #5004 (IsHTTPS, trusted-hop X-Forwarded-Proto), canon v2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 19:32:20 -05:00
bvandeusenandClaude Opus 5.5	b87178d261	fix(6495): a name defined in two packages counts only in the canon's own ... A by-name reference edge could not tell two definitions of one name apart: in a Go repo that defines `file` as importRun.file (internal/files, the canon) and as sftpRun.file (internal/replication), a mirror test calling `m.file(` was recorded as a use of the canon. names_canon now takes defined_at, every repo path that defines each name, in place of the shape file's own names. The own-file rule is unchanged. When the repo also defines the canon's name somewhere the canon is not recorded, a mention counts only from the canon's own package: the directory of a file location exactly, or under a directory location. A name defined once resolves as before. Proposer version 8 -> 9, so the next coverage refresh re-reads every row and replaces its reference edges. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-26 20:05:09 -04:00
bvandeusenandClaude Opus 5.5	2a6d9080ba	fix(6477): a plain-word call needs the parenthesis right after the word ... Read against Fabled Archives after the cleanup: of the 9 rows still linked to snippet #5448 (symbol `file`), all but one matched prose in a comment, "a file (not a directory)", "the file (ScanWaiting". The only real call was `r.file(ctx, ...)`. Formatted code never puts a space before a call's parenthesis and prose does, so the plain-word test is now `word(` with no whitespace. _PROPOSER_VERSION 8 re-reads every row once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-26 19:07:03 -04:00
bvandeusenandClaude Opus 5.5	3e2227e8c5	fix(6483): drop the cross-project uses edges the write path wrote ... Migration 0125 removed the proposer's cross-project `reference` edges, but the write path records its by-name evidence with basis `hook`, so those survived it. A hook edge across projects is impossible for the same reason a reference edge is, and the write path now applies the same by-name test (names_canon), so 0126 removes the ones written before. Judged edges keep their own basis and are untouched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-26 18:29:54 -04:00
bvandeusenandClaude Opus 5.5	cdb71e64c4	fix(6477): a body uses a canon by name only when the name can resolve to it ... The proposer's reference basis, and every uses edge it writes, counted any word-bounded mention of a canon's symbol. Three holes made that wrong at scale (snippet #5448, symbol `file`, held 2,161 uses edges): - Go, Rust, Kotlin, Swift, Dart, C, C#, Ruby and PHP were outside the language-family maps, so their canons read as "unknown, no gate" and were matched in every Python, TS and CSS body. - Canons in other projects were matched by name, though one repo never calls a function defined in another's. - A plain word (`file`, `seen`) or a module's own helper (`_run`) matched wherever it appeared. names_canon is now the one by-name test, used by match_canon, reference_canons and the write-path hint: same project, not a name the file defines itself (unless the canon is recorded there), no generic verb with or without a leading underscore, and a bare lowercase word only where it is called. The write path keeps the payload's own names in play, since a redefinition of a pulled canon is the copy it exists to flag. Repair: record_uses only adds, so replace_reference_uses now makes a row's machine-written reference edges exactly what the current rule finds, leaving judged and hook edges alone. _PROPOSER_VERSION 7 re-reads every row on its project's next refresh. Migration 0125 deletes the cross-project reference edges already stored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-26 17:41:21 -04:00
bvandeusenandClaude Opus 5.5	0b98a3a5cd	chore(6480): remove five Vue components nothing imports ... HistoryPanel, InlineAssistPanel, NoteCard, WorkspaceNoteEditor and WorkspaceTaskPanel had no importer, lazy import or global registration anywhere in frontend/src. The features they served were replaced; token sweeps kept restyling them because they match a glob. The two doc comments that named HistoryPanel.vue now name VersionHistorySection.vue, the note history that is live. SearchBar.vue stays: it is the recorded home of snippet #2961 "SearchBar - the search input recipe", and the two live search boxes are judged variants of it. Deleting it would leave the recipe pointing at nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-26 17:36:03 -04:00
bvandeusenandClaude Opus 5.5	7faaa311d7	fix(6470): a moment proposal counts only opens no hook explained, and asks the reader to judge it ... The signal counted every get_rule open against every moment from the previous three minutes, so a rule a search arm had just shown was proposed for whatever moment happened to fire. All nine pending signal proposals were wrong. - The hook skips an open of a rule a hook named this session, and sends the last three acts from 90 seconds instead of 30 from 180. - A rule already mounted anywhere gathers no signal evidence. - A signal pair keeps the actions that reached its moment and shows them as its why. - The proposal line says it is co-occurrence, not a recommendation, and asks the reader to check the rule against the moment before offering it; moments.md says the same. Plugin 2026.10.26.2029. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-26 16:29:40 -04:00
bvandeusenandClaude Opus 5.5	83cb6420e2	fix(6471): the end-of-turn shape check hears every definition a write made ... The write hooks recorded at most 12 definitions per write (alphabetical, so test functions were the ones dropped) and the post-Bash hook stopped after 4 files, so the Stop hook never asked about the rest. The caps bound the prior-art query; the written ledger now gets the full list, up to 40 files per Bash call, while the query stays at 4 files x 12 names. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-26 16:26:15 -04:00
bvandeusenandClaude Opus 5.5	db2427a3dc	feat(6249): the write-path hint asks whether a new definition copies a close snippet ... The derive check matches by name, so a renamed copy of a recorded snippet passed it and showed only as "similar" prior art. When a write introduces a definition the file does not hold (shape_ledger.new_shapes_at) and an unseen snippet on the menu clears the write-path floor by WRITEPATH_COPY_MARGIN (0.80 at the default floor), the hint now says to reuse it or extract the shared shape before another copy. Names the derive check or the stamping feed already spoke for are left to them. Covers recorded snippets only: the ledger keeps no bodies to compare an unrecorded sibling against. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 20:14:41 -04:00
bvandeusenandClaude Opus 5.5	0a4eb313fe	fix(6255): Test destination names an address that did not answer as S3 ... A 4xx with no S3 error body came from something else at that address, most often a web server on the default port. The message now says so and to check the scheme and port, beside the raw status. A 5xx without a body keeps its own reason, since a busy S3 service can answer that way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 20:03:52 -04:00
bvandeusenandClaude Opus 5.5	d51ccd9b69	fix(6253): the moment-proposal queue lists a signal pair only once it has proposed ... pending() listed every suggested signal row, including pairs still gathering evidence below the three-situation bar, so the queue held 200 "proposals" where about 25 had crossed it. A signal pair now needs proposed_at in its evidence, the same test the misfire half already applies; proposals from a pass are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 20:03:52 -04:00
bvandeusenandClaude Opus 5.5	67d3c68fbf	feat(6254): moment_usage says which rule each moment delivered, and whether it was opened ... Each moment gains by_rule: {rule_id, title, delivered, opened}, read from the (moment, rule) grouping the readout already did. The moment's totals are now summed from those rows, so the two cannot disagree. The Moments settings page shows the list under each moment, closed by default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 19:59:02 -04:00
bvandeusenandClaude Opus 5.5	95ef4af746	fix(6251): the rules warning sends its reader to the rule-arm review ... surfaced_never_pulled told a rules reader there was no judged sample for the rule arms. There is one now; the guard tying the text to REVIEWABLE caught it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 19:59:02 -04:00
bvandeusenandClaude Opus 5.5	7c1d98dd2a	feat(6251): the rule arms can be reviewed — menus_to_review re-runs prompt_rule, pre_tool_rule and write_path_rule ... A rule arm logs its query, floor, budget and project, which is everything semantic_search_rules takes, so a logged call is re-run to a depth past its budget and judged like an auto_inject menu. within_budget is the arm's own cut: inside the budget and, for the banded command and write arms, inside the band of the top hit. "Opened after" reads rule pulls, and rules created after the call are dropped as notes are. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 19:56:17 -04:00
bvandeusenandClaude Opus 5.5	4297c88cd2	fix(6252): the named-record test keeps its number after "with" ... "in 4448" is not read as a reference, so the subject went after the number. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 19:56:17 -04:00
bvandeusenandClaude Opus 5.5	dac4c59e07	fix(6252): a prompt that names nothing gets no notes menu ... "keep going", "yes please do", "is it deployed?": with no word of its own the auto-inject query was the previous reply's tail alone, and the menu handed back the records that reply was built from. In a sample of 59 logged calls, 28 came from short prompts; those with a subject of their own ("continue into DRY 14", "fix the Windows gate") led with the record meant, while the ones without were finished tasks already in context, with an open on 2 of about 15. _has_subject checks the operator's words against a list of words that name nothing; without one, the ranked menu is skipped and records named by number are still shown. The prompt rule arm is unchanged and still searches with the tail. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 19:51:58 -04:00
bvandeusenandClaude Opus 5.5	1fa9245bbf	fix(6247): a getter is seen by its pulls, so the silent list stops naming every pull door ... usage and rule_usage gain pulled_by_source, read from the per-source rows the readout already had, and _silent_surfaces counts those doors as having emitted. The rules-listing points were seen as of the previous commit, through rule_usage.by_source. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 19:28:29 -04:00
bvandeusenandClaude Opus 5.5	d05d4f3632	feat(4636): rule pull-through per surface, and per-rule usage with confirmed lessons on list_rules ... retrieval_telemetry gains rule_usage.by_source, the twin of usage.by_source: distinct rules each surface showed, how many an agent opened, and a ratio that is null on a bulk delivery. list_rules(with_usage=True, days=N) adds each rule's usage, windowed, and how many lessons are confirmed instances of it, so linked and unlinked rules can be compared through MCP. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 19:20:32 -04:00
bvandeusenandClaude Opus 5.5	71260a28e2	align(4909b): every write with a path gets its rule check, whether or not prior art matched ... The write-path rule arm ran only past the notes guard: a write whose code matched no snippet, issue or lesson returned before any rule was searched. It now runs before that guard, on `code or path`, and a write that matched nothing but a rule still returns the rule lines. Operator ruling (2026-10-05): yes. A rule about the file being written does not depend on a snippet resembling it. Cost: one more rule search per write that matched no prior art, with its own embedding (the query is `code or path`, not the notes arm's concept query, so the per-request memo does not cover it). Plus the preference slot from (c) on those writes. Expected telemetry shift, to be read on its own once this reaches main: write_path_rule calls rise toward write_path's count (14 days to 2026-10-22: write_path_rule 4,634 against write_path 3,786 — the notes arm skips trivial payloads, the rule arm does not, so the rule arm will now exceed it). Its zero-result share rises too, since the newly covered writes are the ones that matched nothing in the notes corpus. Tests: the gate test is inverted (a write with no prior art still gets its rule check); the design-only write now runs the rule arm on its path; two notes-arm tests read the write_path row instead of any row, since the rule arm writes its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 18:42:14 -04:00
bvandeusenandClaude Opus 5.5	407f594a53	fix(4909c): the tool-arm suppression tests read the arm's own row, not the slot's ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 18:39:27 -04:00
bvandeusenandClaude Opus 5.5	c3933507c9	align(4909c): the command and write rule arms reserve a line for a preference ... PRE_TOOL_RULE and WRITE_PATH_RULE now take preference_slot=True, like PROMPT_RULE. When no preference placed on score, the arm asks once more for the best preference over the same bar, and shows it as one extra line. Operator ruling (2026-10-05): yes. A preference about how to act ("let each action land before the next") is ranked against every rule whose trigger names the same command; the act is its last chance to shape anything. Cost: one kind-filtered search per call that placed no preference. The query embedding is memoised per request on both hook routes, so no extra model call. Expect a new stream of preference_slot rows from the two act arms; preference_slot's call count will rise roughly by pre_tool_rule's and write_path_rule's (~23k calls over 14 days before this change), and its zero-result share will rise with it, since most commands have no matching preference. Tests: the tool-arm call-row tests count rows under pre_tool_rule only (the slot logs under its own name), and the write-arm bar test reads the arm's own search, which is the first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 18:37:22 -04:00
bvandeusenandClaude Opus 5.5	6299335254	fix(4909d): a shared floor move records the named surface first, then its siblings ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 18:34:16 -04:00
bvandeusenandClaude Opus 5.5	c8ede427ca	align(4909d): every rule arm that annotates reads one bar, kb_rule_threshold at 0.70 ... prompt_rule, pre_tool_rule and write_path_rule now share one settings key, RULE_FLOOR_KEY = "kb_rule_threshold", default 0.70. The reply backstop keeps its own 0.80, because there the floor is a stop bar. Moving the shared floor through tune_retrieval or the Settings form records a tuning event on every surface that reads it (set_dial, via retrieval_surfaces.sharing_floor), and the result names the surfaces it carried as `moved_with`. Settings shows one "Standing-rule confidence threshold" control where it showed three. Operator ruling (2026-10-05): one shared bar for the rule arms, "especially since we're only taking the first x number of them" -- the budget limits what is shown; the bar only decides what is worth ranking. Kept a dial. Why 0.70, from records read rather than percentiles: - write_path_rule near-misses at 0.7199-0.72 were all false positives (rule 149 against a Lidarr comment, 157 against a retention Svelte file, 121 against an Archives restore, 164 against a config test, 131 against a Go package), so the old 0.72 was not hiding real hits -- but the band does noise control on this arm, so dropping 0.02 costs little. - prompt_rule: the operator set 0.70 by hand on 2026-09-18, after a 0.60 experiment admitted junk and was reverted. 0.70 is the number with a human decision behind it. - pre_tool_rule lines near 0.68 this session were mostly noise; rising to 0.70 trims them, and the band still narrows what clears. Retired keys: kb_promptrule_threshold, kb_toolrule_threshold and kb_rulehint_threshold are no longer read. Rows an install stored under them stay in the settings table, inert. On this instance the effective bars move pre_tool_rule 0.68 -> 0.70, write_path_rule 0.72 -> 0.70, prompt_rule stays 0.70; record_release_defaults writes those per-surface release rows on boot, so the telemetry shift has an event to explain it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 18:32:09 -04:00
bvandeusenandClaude Opus 5.5	f77d18cb63	fix(6245): a re-run of bind_repo(moved_from=…) finishes an earlier move ... Once the binding has moved, the old remote is no longer bound, and move_binding refused. An install that renamed its repo before snippet locations moved with it had no way to move them. When the old remote is unbound and the new one is bound to this project, bind_repo now skips the binding move and still moves the snippet locations that name the old repo. The snippet-move test gives each location its own path: rewritten to one repo, identical locations merge into one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 16:21:19 -04:00
bvandeusenandClaude Opus 5.5	e89e6a24de	fix(6245): bind_repo(moved_from=…) moves the snippet locations recorded in the old repo ... A repo renamed on its forge kept every snippet location naming the old repo: the binding and the shape ledger moved, the snippets did not. - snippets.move_location_repo rewrites, on every live snippet of the project, each location whose repo is the old remote in any form (URL, normalized key, "owner/Repo", bare "Repo", compared without case) to the new normalized key. A snippet the caller can only read is listed in read_only and left alone. - Its loop is shared with move_locations through _rewrite_locations, which saves each changed snippet through update_snippet. - bind_repo calls it after the binding moves and reports snippets_moved and snippets_read_only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 16:18:03 -04:00
bvandeusenandClaude Opus 5.5	787685ac63	fix(6244): the instance keeps its own SECRET_KEY in /data, and docker-compose.yml is the compose users deploy from ... With no SECRET_KEY set, Grimoire fell back to a fixed placeholder. The quickstart compose substituted change-me-in-production, so the README's own update step (pull, up -d) recreated the container on that placeholder, and every credential sealed under the key the user started with stopped opening. - config: with neither SECRET_KEY nor SECRET_KEY_FILE, the first start writes a random key to DATA_DIR/secret_key (mode 0600, published with a hard link so concurrent starts agree), and later starts read it back. An explicit key wins and leaves the file alone. A missing SECRET_KEY_FILE or an empty key file stops the start instead of switching keys. With no data directory (a run outside the container) the process gets a temporary key and says so. - app: warns on a public placeholder key, on a temporary key, and when /data is not a mounted volume. - Dockerfile creates /data. - docker-compose.yml is now the deploy compose (published image, both volumes, nothing to set). The build-from-source compose is docker-compose.dev.yml, and docker-compose.quickstart.yml is gone. The Swarm stack file gains the /data volume and keeps its explicit key, because a Swarm can move the app away from a node-local volume. - README: a Deploy section with the compose inline, SECRET_KEY optional, "keep both volumes", and updates that keep the key. A test holds the README's copy equal to the file. - Installs that ran on the change-me-in-production placeholder get a key of their own on the new compose; Settings then asks once for saved forge tokens and the backup secret. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 16:13:43 -04:00
bvandeusenandClaude Opus 5.5	81fe851509	licence: Fabled Grimoire is AGPL-3.0-only ... LICENSE carries the GNU Affero General Public License v3.0 text, the same file the other Fabled projects ship. pyproject.toml, the frontend's package.json and lockfile, and the plugin manifest declare it as the SPDX expression AGPL-3.0-only, and the README says what it asks of anyone who runs a modified version over a network. Reading `license` as an SPDX expression needs setuptools 77, so the build floor rises to it. The project description now matches the README's tagline. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 15:45:11 -04:00
bvandeusenandClaude Opus 5.5	92a15d3e1a	rename(547): the header draws the clasped grimoire, and the README takes the standard shape ... AppLogo still drew the old open book with a spark, so the new mark showed only in the browser tab. It now draws the same clasped grimoire as favicon.svg, in the mark's own fixed colours. That covers the header and the sign-in, register and password pages. The README follows the house order: the logo, name and tagline, a short summary, quick start including the plugin install, the settings a reader must set, setup pitfalls, updating and backups, features grouped by what you do, troubleshooting by the error text, development, and licence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 15:44:03 -04:00
bvandeusenandClaude Opus 5.5	979efe6662	feat(6243): move_path carries a moved path's snippets with its shapes ... Snippet locations are keyed by path too, so a snippet recorded under a moved directory reads `missing` at its next check. The tool is now move_path(project_id, from_path, to_path). It moves the ledger rows as before, and re-paths the project's snippet locations under from_path through update_snippet, so each body and its indexed mirror stay one record. A snippet the caller can only read is listed in snippets_read_only. The tool refuses only when nothing at all is recorded under from_path. The path test is the one snippets already uses (_path_touches), and the plugin version is minted for the skill edit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 15:07:32 -04:00
bvandeusenandClaude Opus 5.5	47b52197aa	feat(6243): a directory moved in the tree keeps its shape judgments ... Ledger rows are keyed by path, so after a directory moves the next sync marks every judged row vanished and lists the same shapes again, unjudged. move_shapes(project_id, from_path, to_path) re-keys the rows under one path to the other, in every repo of the project, keeping each row's judgment, uses edges and history and adding a `moved` event that records the path it left. A row already at the target is replaced when nobody judged it; a judged one stands, and the old row is reported in `kept`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 15:03:03 -04:00
bvandeusenandClaude Opus 5.5	5ad1df8e0f	feat(6242): a repo renamed on its forge keeps its binding and shape ledger ... A binding and every row of its project's code-shape ledger are keyed by the repo's remote. A rename on the forge changes the remote, so binding the new name started an empty ledger beside the old one and left every judgment behind. bind_repo now takes moved_from, the old remote. Its binding and the project's ledger rows move to the new key in one transaction, and the reply says how many shapes moved. The move is refused when: - the old name isn't bound to that project; - the new name is already bound; - the project already has a ledger under the new name. Each refusal leaves both names exactly as they were. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 13:53:57 -04:00
bvandeusenandClaude Opus 5.5	a07547447f	rename(547): the repo is FabledGrimoire, and no stray "scribe" is left ... The forge repo is now bvandeusen/FabledGrimoire. The plugin marketplace default, the install commands in the docs and plugin README, the CI requirements title and the example repo URLs in comments and tests follow it. docs/development.md now names the image the build actually publishes, fabledgrimoire. Two test names still said "scribes_own"; they now say "grimoires_own". What still says scribe does so on purpose: - the backup reader's accepted archive names and prefix; - the label every stored secret is sealed under; - the notes on keeping an old install's database names; - the old migrations. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 13:29:00 -04:00
bvandeusenandClaude Opus 5.5	e45e4cd063	rename(547): the mark is a clasped grimoire ... favicon.svg is a violet book with gold corners and clasp and a four-pointed star in a ring, replacing the indigo book with a spark. It is rendered to 192 and 512 PNG app icons and a 180 touch icon on the page surface. manifest.json lists those icons instead of a favicon.ico that never existed. It describes the product as the README does, and takes its colours from the design system's page surface. index.html's theme-color follows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 11:27:40 -04:00
bvandeusenandClaude Opus 5.5	101ab7bc8d	fix(design): the app serves its own fonts and names no other host ... theme.css loaded Fraunces, Inter and JetBrains Mono from Google Fonts. That sent every visitor's address to Google on every page load, and an instance with no internet drew in fallback type. All three families are now vendored under frontend/src/assets/fonts with every subset Google publishes for them, plus their OFL licences. The Content-Security-Policy no longer lists fonts.googleapis.com or fonts.gstatic.com. A new guard test fails if any stylesheet, page or component links a remote asset or preconnects to one, or if the CSP names another host. The theme.css header now describes the sheet as it is instead of how it used to read. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 11:27:40 -04:00
bvandeusenandClaude Opus 5.5	f1d26f01e2	rename(547): three hook-shell tests call the renamed functions ... The step-3 sweep matched `scribe` only after a non-letter, and in these three tests the shell call sits right after a `\n` escape in a Python string, so the character before it was the letter n. They still called scribe_recent_context, scribe_skip_prompt and scribe_checkpoint_allowed; they now call the grimoire_ names. No other escape-adjacent occurrence remains in the tree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 11:01:11 -04:00
bvandeusenandClaude Opus 5.5	c5eeec471f	rename(547): the plugin is grimoire — manifest, MCP key, hooks, env, skills ... Step 3 of the Scribe -> Grimoire rename. - Plugin `grimoire` in marketplace `grimoire-plugin`, MCP server key `grimoire`, so tools reach a session as mcp__plugin_grimoire_grimoire__*. - hooks/scribe_* -> hooks/grimoire_*, their shell functions and the TMPDIR ledgers with them; SCRIBE_URL / SCRIBE_TOKEN / SCRIBE_HOOK_DIR / SCRIBE_LEDGER_DIRS -> GRIMOIRE_*; the project marker is `.grimoire`. - skills/using-scribe -> using-grimoire, /grimoire:sync, stored processes arrive as grimoire-proc-<slug>; moment_actions names them the same way. - Migration 0124 rewrites stored skill names (rule_moments, rule_moment_judgments, moment_mappings) from scribe:/scribe-proc- to grimoire:/grimoire-proc-, so a rule mounted on a skill keeps firing. - Settings' install commands and MCP-only defaults, the docs and the tests follow. - scripts/check_plugin.py drops the smoke event for a report-check hook that has no file in plugin/hooks. Kept on purpose: the secret-sealing label, and the names that let backups written as Scribe restore and be counted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 10:52:55 -04:00
bvandeusenandClaude Opus 5.5	0f5ef0be63	rename(547): the server is grimoire — package, image, DB defaults, backups ... Step 2 of the Scribe -> Grimoire rename. - src/scribe -> src/grimoire, and every import, patch target, module path, hypercorn entry point and `python -m grimoire.restore` with it; pyproject, uv.lock and the frontend package are named grimoire. - Image git.fabledsword.com/bvandeusen/fabledgrimoire; CI's Postgres service runs as grimoire / grimoire_test. - Compose files default the DB user, database and (prod) volume to grimoire, each overridable from .env, so an install created as Scribe keeps its data by setting POSTGRES_USER, POSTGRES_DB and PGDATA_VOLUME. - Backups are written as grimoire-<ts>.tar with format grimoire-backup-tar. Archives named scribe-* with the scribe-backup-tar manifest still restore and are still counted at the destination (folder and S3), with tests. - Exports, the MCP auth realm, the ASGI scope key and the persistent logger carry the new name. Kept on purpose: the secret-sealing key label stays "scribe.secrets.v1", because every stored secret was derived under it. Plugin identity (plugin name, hooks, env vars, .scribe marker, skills) is step 3. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 10:50:45 -04:00
bvandeusenandClaude Opus 5.5	e99f1169f7	rename(547): what people read says Grimoire ... Step 1 of the Scribe -> Grimoire rename: every capitalised "Scribe" in prose becomes "Grimoire" ("Fabled Scribe" -> "Fabled Grimoire") across the UI, the PWA manifest and page title, the MCP instructions and tool docstrings, hook and skill text, docs and README, with the tests that assert on that prose moving with it. Old migrations keep their wording. Identifiers are untouched here: the package, plugin name, MCP server key, hook file names, env vars, the .scribe marker and FabledScribe repo/image names move in steps 2 and 3, along with prose that quotes them. The sweep matched "Scribe" only as a whole word, so describe/subscribe and friends are untouched. The longer name took the MCP instructions one character over their 1,600 budget; two phrases are shortened to fit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 10:46:37 -04:00
bvandeusenandClaude Opus 5.5	06be537a18	fix(ci): the image build stops pruning the runner's shared Docker daemon ... The build job ran `docker system prune -af` on the runner's shared Docker daemon. That deletes every image no container is using at that moment, including images other repos' jobs had just pulled and were about to start. Jobs with a service container wait ~14s for it to become healthy between pull and create, and fail with "No such image" when a prune lands inside that wait (CI-runner #16). The runner host prunes nightly instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 10:20:33 -04:00
bvandeusenandClaude Opus 5.5	54206afa76	fix(6229): remove the Profile settings page — nothing read it ... The Profile tab said an assistant used it to personalise chat and a daily journal. Neither exists, and nothing read the profile: the page saved to user_profiles and the backup carried it. Removed the tab, the client calls, /api/profile, the service and the model, and migration 0123 drops the table (downgrade recreates it empty). Backup format v27 stops writing user_profiles; an older archive carrying the section still restores, and the file-restore integration test now proves it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 10:14:40 -04:00
bvandeusenandClaude Opus 5.5	067aa58fbc	docs(6210): acceptance sweep — src, scripts and frontend leftovers described in the present tense ... The acceptance greps found what the per-area passes missed: - src/scribe: "Phase 7/8" removal notes in projects, settings and user_profile; a paragraph promising an auto-summary side effect that no longer exists; user_profile's claim that "upcoming MCP profile tools" read the profile, which nothing does; an instance count and instance rule titles in plugin_context; "MILESTONE 323 DECIDED" in rulebooks. - scripts/: check_plugin's header and inline comments were a history of the incidents behind each guard, with issue numbers in two failure messages; check_dangling_styles named this app's classes as its examples; check_design_tokens, measure_duplication and mint_plugin_version cited issues and checklists. - frontend/src: forty-odd comments with four-digit issue numbers that the earlier frontend scan filtered out as hex colours, plus "used to" and "Phase N" notes. Kept: illustrative ids (`#4181` as a bare-id example, `PR #198`), migration Create Date headers and one migration's dated data floor, and the plugin skills' worked examples of how to cite a record. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-21 21:54:38 -04:00