107 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5	5b824c1626	feat(design): the panel now asks whether the app agrees with its own sheet ... Retiring rulebook #2 left the /design drift panel with no data source, and because its empty state was well-written the feature read as working while it could only ever render "nothing designated" (#2419). The original question is genuinely gone: theme.css is generated from design system 2, so checking the system against a sheet derived from it would be a tautology. The question that survives is the one no server can answer. A generated sheet still has to be LOADED and APPLIED, and nothing checked that it was: absent the record declares a token the app doesn't have — the sheet was never regenerated after the record changed, or never loaded differs the app has it with another value — a stale sheet, or a later rule that overrode it unrecorded the app declares a token in the record's own family that the record has never heard of Both sides go through the same engine so the comparison is honest: declared values are set on an offscreen probe and read back, which performs the same var() substitution the browser already did to the live values. Comparing raw strings would mark every derived token as drift. The designation moved with the feature — design_rulebook_id becomes ui_design_system_id, with a migration deleting the retired key rather than leaving an inert row. The prose extractor it fed goes too (#2288 said its runtime role ended when the import landed). Three orphans of the same shape, found alongside and fixed here: - darkOverriddenNames hardcoded [data-theme="dark"]. The sheet went dark-first months ago, so it matched nothing and the "mode-aware" flag silently left the gallery. Now matches the SHAPE of a mode selector, which also holds for an install whose modes aren't light and dark. - groupFor's prefix table never heard of --fs-, so 110 tokens sat under "other". Groups now come from the record where there is one; the table can only know families that shipped with the product (rule #115). - The type scale was a hand-written table of nine sizes marked "no token", true when written and false since the scale was recorded. Now rendered from whatever size tokens the sheet declares, so it can't go stale twice. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-08-03 20:50:03 -04:00
bvandeusenandClaude Opus 5	c34454b840	refactor(theme): the accent was hand-written 16 times — now derived ... `rgba(91, 74, 138, …)` is Scribe's accent in decimal. It appears sixteen times across five files at ten different opacities, plus once as #5B4A8A. Change the accent in the design system and none of them would have moved — which is the precise failure the token system exists to prevent, hiding in a notation that does not look like a colour constant. Now `color-mix(in srgb, var(--color-primary) N%, transparent)`, so every one follows the accent. The design system already uses this form for its own tints (--fs-accent-soft, -faint, -wash), so this is the established idiom rather than a new one. The CI literal count barely moves (45 -> 44) because its regex matches #hex and fifteen of these were rgba(). Worth stating plainly: **the count was never the goal, and the check is blind to this whole class.** An rgba triple is a colour literal in every sense that matters and the report does not see it. Not touched: the badge palette in KnowledgeView (#7A6DA8, #fbbf24, #818cf8 for note/task/plan) and the remaining greys. Those are genuine unmade decisions — what colour IS a plan badge — not drift, and inventing tokens for them would be deciding by implementation. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-08-03 11:53:54 -04:00
bvandeusenandClaude Opus 5	bd60d679d9	refactor(theme): remove 184 var() fallbacks — every one was unreachable ... #2277 counted ~150 "raw colour literals bypassing the tokens". Measuring them told a different story: 184 sat in `var(--token, #fallback)` position, and a check against theme.css shows every one of those tokens IS declared. So the fallbacks could not render. Not drift — vestigial. They were also not this palette. The most common were Tailwind and Flat-UI defaults — #6366f1 indigo, #22c55e green, #f59e0b amber, #3b82f6 blue, #e74c3c and #27ae60 — a second, unsanctioned colour scheme sitting in the codebase looking like the app's colours to anyone reading it. Removing them is not tidying. #2319's lesson is that a fallback is WORSE than a missing token: a missing token renders as nothing and someone eventually notices, while a fallback renders something plausible forever. These 184 were one token rename away from silently repainting the app in Tailwind. The design token check would catch the rename — but the fallback is precisely the thing that would make it invisible if the check were ever bypassed. Literal count 152 -> 45, which matters beyond the number: a report that is mostly unreachable noise is one people stop reading, and then it stops working while still passing. What remains should be genuinely worth looking at. Done with a paren-aware transform, not a regex — `var(--x, rgba(0,0,0,.5))` nests parens and `[^)]+` would cut at the first one and leave `))` behind. Verified after: every changed line is a fallback strip and nothing else, and every var() reference still resolves. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-08-03 11:52:04 -04:00
bvandeusenandClaude Opus 5	3fc693443e	refactor(ui): the settings family migrates; two colour bugs and a dead class ... SettingsView and UserManagementView had near-identical button vocabularies — btn-delete, btn-cancel-delete, btn-confirm-delete, btn-toggle/-open/-close — defined separately in each. Parallel duplication (#2278's shape), and it had already diverged twice: - .btn-confirm-delete used --color-danger in UserManagement and --color-action-destructive in Settings. Those are different colours on purpose: the house style keeps error (something went wrong) distinct from destructive (something is about to). A delete confirmation is destructive. UserManagement was showing the error colour for a button nothing had failed in yet. - .btn-remove-slot's hover reached for --color-danger for the same reason, and is the same correction. It turned out to be dead anyway — style rules only, no template reference anywhere in the app — so it is gone. .btn-danger-outline was defined TWICE inside SettingsView, at 0.4rem 0.9rem and 0.45rem 1rem. One file, one class, two geometries, ~1200 lines apart. That is the clearest single argument for this whole task that I have found: the drift does not need two files, only enough distance that nobody sees both at once. The registration toggle keeps .btn-toggle-close, and only that. It is bound dynamically (:class="registrationOpen ? … : …"), so a name-based scan reads it as unused — checked before deleting. .btn-toggle-open went, because btn-primary now says the same thing; the close state stays because it must NOT read as the primary action it sits on. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-08-01 22:48:35 -04:00
bvandeusenandClaude Opus 5	1a959b1db0	refactor(ui): one button definition, aligned to the design system ... `.btn-primary` was defined five times in five scoped stylesheets and all five had drifted: three paddings, three font sizes, three disabled opacities — and ProjectListView had no disabled style at all, so a disabled button there looked enabled. Nothing detected any of it. A scoped duplicate is not a rule violation, not a broken reference, and not a recorded snippet, so no existing check could see it (#2273). assets/components.css is now the single definition of the core four — primary, secondary, ghost, danger — plus the small modifier, in design-system tokens throughout. Operator's call to align to the system rather than to the majority of current values, so buttons move to the 8px radius and 12px label the system specifies, from the app's 4px/14.4px. Class names are unchanged, so there are no template edits: the existing surface is repurposed, not rebuilt. STAGING PROPERTY that makes this safe to land ahead of the rest: a Vue `<style scoped>` rule compiles to `.btn-primary[data-v-…]` (specificity 0,2,0) and beats a plain global selector (0,1,0). So the shared sheet changes nothing for a view still carrying its own copy, and every intermediate state of the remaining migration is coherent rather than half-applied. Two divergences corrected on the way, both worth naming: - SnippetEditorView's `.btn-secondary` was a GHOST in disguise — outline styling under the secondary name, while the house style says secondary is filled bronze. It now looks like what it is called. - SnippetDetailView and SnippetListView tinted a ghost button's label with the ACCENT on hover. The house style reserves the accent for identity and active state, never general chrome. DesignView reported "no shared button exists" as an honest gap and declined to draw a look-alike. That gap is closed, so it now renders the app's real classes — the specimens cannot drift from the app without drifting the app. Net -177 lines. Follows: the ~20 semantic one-offs (.btn-save, .btn-delete, .btn-toggle …) and the compound overrides in ProjectView, one of which puts the accent on a primary action button. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-08-01 19:52:35 -04:00
bvandeusenandClaude Opus 5	4c9a637507	fix(theme): text on a filled colour needs its own token — the old one inverts ... 76 hardcoded `color: #fff` now resolve to --fs-text-on-action, a new token that is parchment in BOTH modes. The design system said they should supersede to --fs-text-primary, on the recorded reasoning that "there is no 'text on action' colour, there is just the text colour." That is true on dark and wrong on light. --fs-text-primary inverts to #14171A; the surfaces underneath it do not invert at all — every one of these 76 sits on an action colour, a semantic colour, the accent, or the CTA gradient, all of which hold a single value across modes. Sweeping as recorded would have put obsidian text on moss green: roughly 2.4:1, against a house style whose stated floor is WCAG AA. It would have looked correct to me, because I checked it in the mode where it was correct. --color-accent-fg had the same defect independently and is repointed too. The token check now reports zero superseded literals, down from 30 files, and raw colour literals drop 246 -> 169. Closes #2275. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-07-31 22:40:58 -04:00
bvandeusenandClaude Opus 5	4ca3ab02c4	feat(design-explorer): the drift panel — rulebook says X, tokens say Y ... Milestone #251 step 5 (#2262), plus the Settings control that makes it reachable. The comparison is deliberately thin — set arithmetic over live token values, which is the one thing the browser knows and the server doesn't. The hard half (prose to claims) already lives in Python where pytest can assert on it. Three claim kinds, and the third inverts the test: a `token` claim asks whether a custom property of that name exists; a `color` claim asks whether any token resolves to that value; a `prohibited_color` claim FAILS when present. normalizeColour is the client-side twin of normalize_hex and has one job the server cannot do: getComputedStyle reports colours as rgb()/rgba() regardless of how they were authored. So one colour has three spellings in play — #FFFFFF in the rulebook, #fff in the stylesheet, rgb(255,255,255) from the browser — and a comparison that misses any of them under-reports silently rather than erroring. THE PANEL STATES ITS OWN BLIND SPOT, which matters more than it sounds. This compares the rulebook against TOKENS. A literal hardcoded in a component, where a token should have been referenced, is invisible to it — the drift isn't in the tokens at all (#2275: 67 hardcoded whites against a rule forbidding pure white). Reading those would mean bundling every SFC's source into the app; the check belongs in CI and is tracked at #2277. A drift report that silently omitted a whole category would invite the reader to conclude the category is clean, so the panel says so in the panel rather than in a comment nobody reads. Findings are ranked violated → missing → ok, and `ok` rows are hidden behind a toggle. Same principle the auto-inject menu is built on: a short list that gets read beats a complete one that doesn't. Settings gains a rulebook picker. "None" is a first-class choice, not an unset error — most installs have no rulebook describing their design system, and saving empty DELETES the setting rather than storing a zero. The panel's empty state points at Settings and Settings points back at the panel, so neither is a dead end. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-07-30 15:32:29 -04:00
bvandeusenandClaude Opus 5	1fb883b72f	fix(write-path): give the semantic arm its own threshold + a payload floor ... Closes #2223. The write-path prior-art trigger's semantic arm shared auto-inject's 0.55 threshold, which was tuned on prose. Code embeddings sit on a much higher similarity floor — any two Python-shaped payloads share keywords, indentation and structure — so 0.55 landed INSIDE the noise band. Measured against the live instance: near-duplicate of a recorded helper 0.73-0.74 true positive unrelated colour math / Vue SFC / CSS 0.55-0.63 false positive `x = 1` 0.58 false positive 6 of 8 probe payloads produced a nudge; 4 were noise. The margin gate couldn't help — _AUTOINJECT_BAND is relative to the top hit, so with a single hit it never engages. Two gates are now the write-path arm's own: - kb_writepath_threshold, default 0.68 — above every measured false positive, still 0.05 below both true positives. Auto-inject keeps 0.55; it was tuned on prose and is not implicated. The comment this replaces explicitly reserved the split for when telemetry showed the surfaces wanted different values, so this is the change it described, not a reversal of it. - WRITEPATH_MIN_CODE_CHARS = 48 non-whitespace chars, below which the semantic arm doesn't run at all. Whitespace is excluded so a deeply indented one-liner can't pass on padding. 48 sits under the smallest plausible reusable helper (~60) and well over a degenerate edit, so it errs toward keeping recall — precision is the threshold's job. This is the cheap half of the operator's #89 idea; the full length<->threshold curve stays open there, since they asked to brainstorm it rather than have a scale invented for them. top_k stays shared — "how many titles at once" means the same thing on both surfaces. The existing tests were passing `code="x"` / `code="def f(): ..."` into the semantic arm, i.e. exactly the payloads the floor now drops, so the gate tests were never exercising a realistic payload. They now use a REAL_CODE fixture, plus new coverage for the floor (trivial payload, padding, place-arm unaffected, real helper passes) and a guard on the constant itself. Settings UI carries the new knob with the reasoning in its hint, and the write-path checkbox no longer claims it shares the threshold. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-07-29 23:26:59 -04:00
bvandeusenandClaude Opus 5	6db791965f	feat(snippets): near-duplicate finder — surface the sets worth merging ... #231's premise was unifying reusable things already scattered as one-offs. The create gate PREVENTS a new duplicate and merge_snippets CURES one you point it at, but nothing FOUND the duplicates already in the record — someone had to notice them by hand, which is the exact failure the Drafter exists to remove. One indexed self-join over note_embeddings, not an N² Python scan: pgvector's cosine distance is the same operator semantic search uses, so a similarity floor is a distance ceiling and the work stays in Postgres. `left.note_id < right.note_id` yields each unordered pair once and drops the self-pair that would otherwise dominate the ranking. Pairs are collapsed into merge SETS by connected components. Transitive on purpose: A~B plus B~C puts all three together even when A and C don't directly clear the bar, which is what merge actually does (it folds every source into one survivor). The cost is that a chain of mild resemblances can rope in a member that isn't really alike — so the UI presents a set as a proposal, shows the members, and never merges without a confirm. Two scope decisions worth naming: - OWN snippets only. merge_snippets requires one owner across the set, so surfacing someone else's would propose a merge that cannot be performed. The report is bounded by what the operator can act on, not what they can see. - Threshold defaults to 0.82, LOOSER than the write gate's 0.90, and is a setting rather than a constant (rule #25). The gate blocks a create and has to be unforgiving of noise; this only suggests a merge under review, so it must reach further or it would never surface the pairs the gate already let through — which are precisely the ones that accumulated. Fixes a real bug in the merge flow while wiring the UI: selectedList filtered the selection against the CURRENT PAGE, and doMerge derives its source ids from that list. A corpus-wide suggested group with off-page members would have rendered incomplete and silently merged only the visible subset. A group under review is now the authority for that list. Refs #2088 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs	2026-07-28 18:32:40 -04:00
bvandeusen	e0328f2b1c	feat(plugin): write-path trigger — offer prior art before code is rewritten ... The milestone headline. Auto-inject fires on the operator's prompt; the moment reuse is actually lost is later, when the agent decides mid-task to write a helper. A PreToolUse hook on Write|Edit now fires there. Channel: `additionalContext` with NO permissionDecision, so the note reaches Claude beside the tool result and the write is never blocked — a recall aid must not be able to stop the operator's work. Plain stdout would have been invisible to the model, and deny/ask would have made a nudge into a gate. Two arms, different in kind: - BY PLACE — a snippet recorded at this path (or its directory) is prior art by definition, not resemblance, so it is neither scored nor thresholded. This is what #2083's reverse lookup was built to answer. - BY MEANING — semantic search restricted to snippets (new `note_type` filter on semantic_search_notes) over the code about to be written. Place ranks first; the top-k cap spans both arms. Gates carried over from milestone 93 verbatim: threshold, margin, session dedup, titles-never-bodies. Own `source='write_path'` in retrieval_logs so precision is tunable separately — the docstring records that the place arm is unlogged and hands that to #2085. Its own on/off in Settings but the SAME threshold/top-k: one "how loud may Scribe be" knob is easier to reason about than two that drift, and splitting them later is then a data-backed change rather than a guess. Details worth keeping: the hook sends a REPO-RELATIVE path because that is how locations are recorded; the git remote resolves to a project and is never used as the location `repo` filter (different namespaces, would silently match nothing); the endpoint stays a GET because a read-scoped API key cannot POST and every other hook depends on that. plugin.json 0.1.17 -> 0.1.18. Refs #2082, milestone #232.	2026-07-28 09:08:17 -04:00
bvandeusenandClaude Opus 4.8	12f71fabdf	refactor(scribe): remove calendar + entity surfaces from web UI (frontend) ... Frontend half of the narrowing (milestone #194); matches backend b49efdc. - delete CalendarView, EventSlideOver, WeatherCard (orphan) - drop /calendar route + nav link + the g→l keyboard shortcut - strip the calendar-events API client + event/metadata bits from note types and the notes store - KnowledgeView: remove People/Places/Lists tabs, entity cards, create buttons and the upcoming-events widget; keep notes/tasks/plans/processes + the overdue-task badge - NoteEditorView: remove person/place/list forms + list-builder + entity metadata; keep note + process editors (type select = Note/Process) - DashboardView: drop the "Upcoming · 7 days" events rail card - SettingsView: remove the CalDAV integration card + save/test (its endpoints were deleted backend-side) - prune the now-dead entity/event CSS RecurrenceEditor + task recurrence rules are kept (task machinery, not calendar). Verified by a full dangler sweep. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BPtbSzA4JLMAKgFZ8VTg7Q	2026-07-19 16:10:24 -04:00
bvandeusenandClaude Opus 4.8	8126db3203	feat(plugin): knowledge auto-inject (Path A) — title-first per-turn awareness ... New UserPromptSubmit hook (scribe_autoinject.sh) + GET /api/plugin/retrieve that surface the TITLES (never bodies) of the few notes clearing four anti-bloat gates: a per-user confidence threshold (stricter than pull search), a margin gate, per-session dedup (exclude_ids), and a top-k ceiling. Each retrieval is logged to retrieval_logs as source=auto_inject so the threshold can be tuned from data. Per-user config (enable / threshold / top-k) is DB-backed via /api/settings with a Settings UI card; defaults enabled, threshold 0.55, top-k 3 (conservative — tune once auto_inject telemetry accrues). Scribe: project 2, milestone 93, task 1033. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xz4j1H7pjYSjKsEpgcNH5E	2026-06-22 20:31:07 -04:00
bvandeusenandClaude Opus 4.8	96079d5b77	feat(db): table-health readout — per-table bloat metrics in admin card ... You can't decide what to maintain without seeing what's bloating. Adds a read-only health panel driven by Postgres' own statistics views. - services/db_maintenance.py: get_table_health() queries pg_stat_user_tables + pg_total_relation_size + pg_database_size — per-table size, live/dead tuples, dead-tuple ratio (the bloat signal), and last (auto)vacuum/(auto)analyze. - routes/admin.py: admin-only GET /api/admin/db-maintenance/health. - SettingsView.vue: 'Table health' table in the maintenance card, all tables sorted by dead tuples, rows >=20% dead-ratio flagged; total DB size shown; refreshes after a Run-now so the dead-tuple drop is visible. - Tests: health row/size shaping + null-timestamp passthrough; route + service surface. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 17:53:24 -04:00
bvandeusenandClaude Opus 4.8	c4553d937c	feat(db): scheduled DB maintenance — daily targeted VACUUM (ANALYZE) ... Adds a daily off-hours VACUUM (ANALYZE) over the high-churn tables the retention/purge sweeps churn (app_logs, notifications, token tables, notes, note_versions), on top of Postgres autovacuum, to reclaim bloat left by the nightly bulk DELETEs and keep planner stats fresh. - services/db_maintenance.py: run_maintenance() over a closed table allowlist via an AUTOCOMMIT connection (VACUUM can't run in a txn); per-table summary persisted as the db_maintenance_last_run admin setting. - services/db_maintenance_scheduler.py: BackgroundScheduler cron (default 04:00 UTC, after the 03:30 trash purge); enabled-gate checked at fire time; live reschedule on hour change. Wired into app.py start/stop. - routes/admin.py: admin-only GET/PUT /api/admin/db-maintenance + POST /run. - settings.py: set_admin_setting() (write-side of get_admin_setting) for out-of-request writes. - SettingsView.vue: admin 'Database maintenance' card — enable toggle, run-hour (UTC), Run-now, last-run summary. - Tests: allowlist is closed, VACUUM issued per table, one failure doesn't abort the rest, summary persisted; route/scheduler/service surface. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 16:42:04 -04:00
bvandeusenandClaude Opus 4.8	da511fcc9f	feat(ui): declutter dashboard done-recently + MCP-access, add per-project stats ... Dashboard: - 'Done recently' chip-cloud -> compact uniform list (Active-now row style), showing 5 with inline expand to the rest (backend already returns up to 8). - New 'Projects' rail card: each active project with 'N open · M done'. Backend already computed done_count (dashboard.py) — now surfaced in the /api/dashboard payload per active project. MCP Access (Connect Claude / Claude Code): - Progressive disclosure: lead with the pre-filled plugin-install snippet; fold server name, scope, marketplace URL, and the MCP-only path into a single 'Customize' expander. Desktop tab keeps its own server-name field. - Marketplace URL now defaults to this instance's own repo via config.PLUGIN_MARKETPLACE_URL (env-overridable); /api/plugin/marketplace-url falls back to it, so the field + install snippet are pre-filled out of the box instead of showing a generic placeholder. Refs #761 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-10 11:04:23 -04:00
bvandeusenandClaude Opus 4.8	1d82e81527	feat(plugin): admin-configurable marketplace URL as the install default ... The Settings install command had a <your-scribe-repo> placeholder — not copyable. Add an instance-global 'plugin_marketplace_url' setting (admin sets it to the app's own repo) that every user's MCP Access reads, so the /plugin marketplace add command is copyable out of the box. Keeps it universal (each deployment configures its own repo) rather than hardcoding one. - services/settings.get_admin_setting(key): admin-scoped global read. - routes/plugin: GET /api/plugin/marketplace-url (any user) + PUT (admin). - SettingsView: Admin → 'Plugin marketplace' field to set it; MCP Access marketplace field falls back to the configured value. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-10 00:17:05 -04:00
bvandeusenandClaude Opus 4.8	c0b3ec7d9b	feat(settings): lead MCP Access with plugin install, demote raw MCP ... Per operator: the plugin install should supersede the bare MCP connection in Settings, since the plugin incorporates the MCP and adds the session-start hook + skills. The Claude Code tab now leads with /plugin marketplace add + install (with a persisted marketplace-URL field and the base-URL/key/project-id prompts spelled out), and the old 'claude mcp add' command moves into a collapsed 'Advanced: connect the MCP only' disclosure. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-09 23:52:15 -04:00
bvandeusenandClaude Opus 4.8	70ab3f38c6	chore: remove pre-pivot dead code + finish Scribe rebrand (#599 t1-3) ... - Header wordmark Fabled -> Scribe; fable:calendar-changed event -> scribe:calendar-changed; SettingsView CSS comment. - Drop dead Project.auto_summary + summary_updated_at columns (migration 0063) -- the Ollama-era summarizer is gone; model + 2 frontend types + projects test updated. - Remove pivot vestiges: diagnostics _curator_busy()/curator_busy heartbeat field, tz BRIEFING_DAY_START_HOUR/user_briefing_date dead aliases, the ignored 'model' param on get_embedding (+ its test). ruff src/ clean; CI is the gate. Part of scribe plan #599. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-03 16:16:44 -04:00
bvandeusenandClaude Opus 4.8	b255a0f90e	refactor: rename package fabledassistant -> scribe (code-only) ... Renames src/fabledassistant -> src/scribe and all imports, plus the default DB name and DB user/password (fabled -> scribe) in config + compose. 952 refs / 154 files. Reverses the old 'internal name stays fabledassistant' convention. Code-only: live databases are still physically named 'fabledassistant'. Deployed environments must set POSTGRES_DB / POSTGRES_USER (or rename the DB) since the defaults now resolve to 'scribe'. Repo (FabledScribe), git host (fabledsword), MCP (fabled-git) and the image name (fabledscribe) are intentionally unchanged. ruff check src/ clean locally; CI (typecheck + pytest) is the gate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-03 15:48:35 -04:00
bvandeusenandClaude Opus 4.8	64bc50c788	chore(frontend): drop dead settings toggle, types, and store list-surface ... Drift-audit Group 7 frontend cleanup (no behavioral change): - SettingsView: remove the 'auto-consolidate task bodies' toggle and its saveAutoConsolidate handler. The auto_consolidate_tasks setting has zero backend readers (curator removed in Phase 8); the control did nothing. - AppSettings type: drop the dead assistant_name / default_model hints (kept the open string index signature the store actually uses). Delete the fully orphaned types/chat.ts (zero importers). - notes/tasks Pinia stores: remove the list/filter/sort/pagination surface that backed the removed /notes and /tasks list views (verified no consumer uses the tasks/notes arrays, refresh, or any filter/sort/pagination method). Kept currentNote/currentTask, loading, fetch/create/update/delete, convert, patchStatus, startPlanning, backlinks, tags. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-02 19:47:28 -04:00
bvandeusen	e5565b73dc	feat(trash): Settings retention field (trash_retention_days, 0=keep forever)	2026-05-29 12:12:04 -04:00
bvandeusenandClaude Opus 4.7	4806c34a3c	refactor: Phase 10 — Ollama service, image cache, config, frontend orphans ... Final cleanup phase of the MCP-first pivot. docker-compose: - docker-compose.yml: drop ollama service + OLLAMA_URL/MODEL env vars + IMAGE_CACHE / VAPID env comments - docker-compose.prod.yml: drop ollama service + Ollama env + GPU reservation - docker-compose.quickstart.yml: drop ollama service + Ollama env + GPU-reservation comment; quickstart instructions now point at the MCP Access tab instead of model-pull Config: - Drop OLLAMA_URL, OLLAMA_MODEL, OLLAMA_BACKGROUND_MODEL, OLLAMA_KEEP_ALIVE_*, OLLAMA_NUM_CTX, EMBEDDING_MODEL (fastembed is hard-coded inside services/embeddings.py) - Drop IMAGE_CACHE_DIR, IMAGE_MAX_BYTES (image cache subsystem deleted) - Drop VAPID_PRIVATE_KEY, VAPID_PUBLIC_KEY, VAPID_CLAIMS_SUB (push deleted in phase 8) - Drop VOICE_ENABLED, STT_BACKEND, STT_MODEL, TTS_BACKEND (voice deleted in phase 8) - Drop Config.validate() rules for those keys Image cache deletion: - services/images.py, routes/images.py, models/image_cache.py - models/__init__.py: drop ImageCache import - app.py: drop images_bp registration - alembic/versions/0054_drop_image_cache.py: DROP TABLE image_cache Frontend client.ts orphan exports stripped: - getVoiceStatus, getVoiceList, getVoiceLibrary, installVoice, uninstallVoice, transcribeAudio, synthesiseSpeech, VoiceStatusResult / VoiceEntry / VoiceLibraryEntry types - getJournalConfig, saveJournalConfig, getJournalToday/Day/Days, triggerJournalPrep, runJournalCurator, listPendingActions, approvePendingAction, rejectPendingAction, listJournalMoments, updateJournalMoment, deleteJournalMoment, geocodeAddress - JournalConfig / JournalLocation / JournalConversation / JournalMessage / JournalDayPayload / JournalMoment / CuratorRunResult / PendingCuratorAction types - consolidateProfile, clearProfileObservations, listProfileObservations - ProfileObservationEntry, learned_summary/observations_* fields on UserProfile - consolidateTask (cascading update to TaskEditorView) - getFableMcpInfo, getNewsItems, GetNewsItemsParams, NewsItem import TaskEditorView: - Drop the auto-summary banner + Re-consolidate button - Drop isBodyAutoMaintained gate (editor is always user-controlled now) - Drop reconsolidate function + reconsolidating ref SettingsView: - profile ref no longer initialises learned_summary / observations_count / observations_updated_at (those fields are gone from UserProfile type) Surviving frontend composables/components flagged for likely future cleanup but not deleted in this commit (no compile errors, just unreferenced after Phase 7-8): - useAssist, useFloatingAssist, useTagSuggestions, useVad, useListenMode, useOnnxPreloader (composables) - WorkspaceNoteEditor, WorkspaceTaskPanel, WeatherCard, InlineAssistPanel (components) - api/client.ts still references /api/notes/assist/* and /api/notes/suggest-tags via useAssist + useTagSuggestions — those endpoints 404 now but no caller hits them; dead at runtime, harmless. Compose stack collapses to two services: `app` + `db`. No Ollama, no voice models, no fable-mcp wheel build. First-boot install reduces to: docker compose up -d → visit web UI → register → Settings → MCP Access → copy snippet → claude mcp add … → done. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 19:10:25 -04:00
bvandeusenandClaude Opus 4.7	91bafb641f	refactor: Phase 8 — backend deletion (chat / voice / push / journal / curator) ... Mega-commit. Strips all server-side LLM machinery now that Phase 7 has removed the corresponding UI surfaces and the MCP HTTP endpoint is the sole assistant interface. Deleted (services/): chat, generation_buffer, generation_log, generation_task, llm, tools/ (entire package), stt, tts, voice_config, voice_library, push, journal_closeout, journal_pipeline, journal_prep, journal_scheduler, journal_search, curator, curator_scheduler, consolidation, tag_suggestions, research, weather, article_fetcher, pending_actions, moments, assist, wikipedia. Deleted (routes/): chat, voice, push, journal, quick_capture, fable_mcp_dist. Deleted (models/): conversation, generation_tool_log, push_subscription, pending_curator_action, moment, weather_cache. Deleted (tests/): test_generation_log, test_journal_*, test_consolidation, test_lookup_tool, test_notes_consolidation_trigger, test_record_moment_guards, test_research_pipeline, test_tools_*, test_tool_use_fixes, test_voice_library, test_weather_service, test_calendar_tool_tz, test_wikipedia. Deleted (top-level): fable-mcp/ (legacy standalone stdio package — wheel-build pipeline also removed from Dockerfile). app.py: - blueprint registrations for the 6 deleted routes - startup hook trimmed: no more Ollama warmup, KV-cache priming, journal/curator schedulers, voice model loading - shutdown hook simplified - httpx import dropped (was for Ollama calls) pyproject.toml: - removed deps: pywebpush, feedparser, html2text, trafilatura - removed [voice] extras entirely - description updated for the MCP-first architecture Dockerfile: - removed faster-whisper / piper-tts install steps - removed bundled piper voice download stage - removed fable-mcp wheel build stage Surviving-file edits: - services/auth.py: drop Conversation table claim on first-user setup - services/backup.py: drop conversation / push-subscription export+restore; v1/v2 restore now silently skip pre-pivot conversation data - services/notes.py: drop maybe_consolidate trigger on task done/cancelled; drop _maybe_trigger_project_summary (LLM auto-summary) - services/projects.py: drop generate_project_summary + backfill_project_summaries (both LLM-driven) - services/user_profile.py: drop append_observations / consolidate / clear_learned_data (curator-tied) and build_profile_context (was LLM system-prompt builder) - services/notifications.py: stub out _fire_push_notif (was send_push_notification) - services/event_scheduler.py: drop event-reminder push + chat-retention cleanup job; keep CalDAV pull-sync + reminders job (in-app) - services/diagnostics.py: _curator_busy() always False - routes/notes.py: drop /assist, /assist/stream, /suggest-tags endpoints - routes/tasks.py: drop /<id>/consolidate endpoint - routes/settings.py: drop /models, KV-cache-prime-on-save, journal-schedule timezone hook, and the SearXNG search-test endpoint; inline _is_private_url (was in services/llm.py) - routes/admin.py: drop /voice, /voice/reload endpoints - routes/profile.py: drop /consolidate, /observations (GET, DELETE) - models/__init__.py: drop the 6 dead model imports Frontend cascade: - stores/push.ts: deleted entirely (no callers after Phase 7) - stores/settings.ts: drop checkVoiceStatus + voice-status state - views/SettingsView.vue: drop Locations section + journalConfig state (was tied to /api/journal/config); drop JournalConfig + journal/voice api/client imports - frontend/api/client.ts: orphaned voice/journal/profile-observation/ fable-mcp-dist exports are left as dead but harmless (call them and they 404; type-check is clean). Pre-existing v1 backups that contained conversations/messages still restore — those tables are silently dropped from the import path. Anyone pulling the new image with a populated database will need the Phase 9 migration to drop the dead tables (coming next). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 17:47:18 -04:00
bvandeusenandClaude Opus 4.7	8bec68abc0	fix(ui): restore missing </div> closing the Notifications tab ... The earlier sed-delete of the Push/ChatHistory/About sections from the Notifications tab also clipped the tab's outer </div>. Vue's type-checker happily accepted the unbalanced structure (templates type-check on script bindings, not tag pairing) but Vite's Vue compiler failed at build time: Element is missing end tag. file: src/views/SettingsView.vue:1062:5 (The reported line 1062 was the outermost .settings-content div — Vue's parser blames the outermost open tag when an inner sibling goes unclosed.) Confirmed by counting: 115 open <div, 116 </div> before — and now 116/116 after restoring the closing tag between the Email Notifications section and the Integrations tab. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 15:38:06 -04:00
bvandeusenandClaude Opus 4.7	ba6f2c7614	refactor(ui): purge SettingsView dead JS left over from Phase 7 ... The Phase 7 template strip left script-level state, functions, and imports that no template ever referenced. TypeScript strict mode (noUnusedLocals + noUnusedParameters) caught all of them on CI. Removed from the script: - chat retention: chatRetentionDays, savingRetention, saveRetention - VAPID/push: vapidResetting/Msg/Error, resetVapidKeys, usePushStore, pushStore.checkSubscription() call in onMounted - admin voice block: adminVoiceEnabled, adminVoiceSttModel, savingAdminVoice, adminVoiceSaved, voiceLoadingModels, saveAdminVoice, reloadVoiceModels (plus the matching admin template block — that was still present and referenced these) - user voice block: voiceStatus, voiceStatusLoading, availableVoices, voiceTtsVoice, voiceTtsSpeed, voiceSpeechStyle, savingVoice, voiceSaved, voiceTabLoaded, the whole voice library (voiceLibrary, voiceLibraryLoading/Error/Filter/Expanded, installingVoiceIds, uninstallingVoiceIds, filteredVoiceLibrary, formatVoiceSize, loadVoiceLibrary, refreshInstalledVoices, installLibraryVoice, uninstallLibraryVoice, loadVoiceTab, voicePreviewing, previewVoice, saveVoiceSettings) - observations / consolidation: consolidating, clearingObs, observations, observationsExpanded/Loading/Loaded, toggleObservations, onToggleCloseout, runConsolidate, clearObservations - assistant / model management: assistantName, defaultModel, backgroundModel, installedModels, defaultChatModel, OllamaModel interface, ollamaModels, pullModelName, pullProgress, pulling, deletingModel, formatBytes, loadOllamaModels, pullModel, deleteModel, saveAssistant, saving, saved - api/client imports: getVoiceStatus, getVoiceList, getVoiceLibrary, installVoice, uninstallVoice, synthesiseSpeech, consolidateProfile, clearProfileObservations, listProfileObservations, VoiceStatusResult, VoiceEntry, VoiceLibraryEntry, ProfileObservationEntry Surviving: journalConfig + locations editor + temp_unit selector (Profile→Locations section still uses these to manage home/work addresses for any future feature; the journal-specific prep/closeout fields on the same object are dead but harmless as object members). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 15:26:51 -04:00
bvandeusenandClaude Opus 4.7	18eb1e7ab2	refactor(ui): Phase 7 — strip chat/voice/journal/workspace/home surfaces ... Frontend deletion phase of the MCP-first pivot. All in-app conversational surfaces are gone — Claude/MCP is the assistant now. Deleted views: ChatView, JournalView, WorkspaceView, HomeView Deleted components: ChatPanel, ChatInputBar, ChatMessage, ChatStreamingBubble, ToolCallCard, ToolConfirmCard, WorkspaceChatWidget Deleted composables + store: useVoiceRecorder, useVoiceAudio, useStreamingTts, stores/chat Router changes: - / now redirects to /knowledge (was /journal) - dropped /chat, /chat/:id, /journal, /workspace/:projectId - /tasks still redirects to / (→ /knowledge) - /notes still redirects to /knowledge KnowledgeView: - removed ChatPanel + ChatInputBar embeds - removed minichat floating widget + state + handlers - removed Chat link from today bar - removed `chatStore` driven auto-refresh-on-tool-call watch App.vue: - removed useChatStore + startStatusPolling/stopStatusPolling - removed VAD ONNX preloader (voice subsystem dead) - removed visibilitychange listener (only did voice status re-check) - removed `c` single-key shortcut (focus chat / goto chat) - removed `g+c` two-key sequence (goto chat) - removed Chat section from shortcuts overlay - removed `.chat-page` / `.workspace-root` CSS overflow rule AppHeader.vue: - removed useChatStore + status indicator (Ollama model status) - removed Chat / Journal nav links (desktop + mobile) SettingsView.vue (4598 → 4079 lines): - removed Voice tab entirely - Notifications tab: dropped Push Notifications + Chat History + About sections (kept Email Notifications) - General tab: dropped Assistant (name + model pickers) + Model Management sections (kept Tasks + Timezone) - Profile tab: dropped Journal + Observations sections - VALID_TABS + tab list array no longer include "voice" - removed `loadVoiceTab()` activation trigger Service worker (frontend/public/sw.js): - dropped push and notificationclick handlers (push subsystem only fired on internal generation completion, which is gone) - kept empty fetch handler as PWA installability shell Script-level dead code (state refs, helper functions referencing removed APIs) remains in SettingsView and stores/push.ts and stores/settings.ts for now — Phase 8 backend deletion will clean those up alongside the matching backend route removals. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 15:14:00 -04:00
bvandeusenandClaude Opus 4.7	0cc09f917d	fix(ui): claude mcp add takes URL as positional arg, not --url ... The generated Claude Code snippet was outputting: claude mcp add ... scribe-dev --url <URL> --header ... But `claude mcp add` errors out with `unknown option '--url'`. The URL is a positional argument, not a flag: claude mcp add [--transport ...] [--scope ...] <name> <url> [--header ...] Dropped --url and put the URL inline as a positional. Claude Desktop JSON snippet was already correct (uses {url, headers} keys, not a CLI flag). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 12:45:28 -04:00
bvandeusenandClaude Opus 4.7	97c22941a8	feat(ui): configurable MCP server name + scope; start Scribe rebrand ... Settings → MCP Access now lets you tune the generated snippet: - Server name input (default: 'scribe', stored per browser in localStorage). The name appears both in the claude mcp add command and as the JSON key in claude_desktop_config.json's mcpServers map. - Scope dropdown: user / project / local. Drives the --scope flag in the claude mcp add snippet. Picks 'project' to commit the server into the current repo's .mcp.json. User-visible 'Fable' → 'Scribe' in MCP Access tab copy (lead text, Claude Desktop step). Branding pivot in the rest of the app (assistant_name placeholder, SMTP defaults, version line, etc.) is deferred — chat/journal copy is going away in Phase 7 anyway. Deliberately NOT touched: - Tool names (fable_*) — protocol-level identifiers; renaming breaks any Claude session, agent, or automation that referenced them. Warrants its own phase. - mcp/server.py: FastMCP('fable', ...) server name — same reason. - Internal package name fabledassistant — per the project's naming convention (CLAUDE.md memory), internal stays. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 11:22:28 -04:00
bvandeusenandClaude Opus 4.7	27b5c45f27	feat(ui): MCP Access tab — HTTP transport, in-app endpoint ... Rewrites the apikeys settings tab for the new MCP architecture: - Tab label: 'API Keys' → 'MCP Access' - Shows the in-app MCP URL (<origin>/mcp) with a copy button - Claude Code snippet uses --transport http + --url + --header - Claude Desktop snippet uses {url, headers: {Authorization}} - Drops the wheel-download flow, the 'Other' client tab, and the stdio env file / Claude config download helpers — those were for the standalone fable-mcp package which goes away in phase 8 The api_keys backend stays unchanged — keys double as bearer tokens for the /mcp endpoint via the existing auth.py middleware. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-26 21:23:06 -04:00
bvandeusenandClaude Opus 4.7	1b65c44339	ux: rename model fields + enforce serial curator execution ... Three coordinated changes per operator request 2026-05-24: 1. Settings UI rename matching the language we actually use: - Chat Model -> Chat & Voice Model - Worker Model -> Curator Model Setting KEYS (default_model / background_model) unchanged on purpose; renaming them requires a migration touching 50+ call sites for purely UX-facing benefit. 2. Settings UI help text rewritten: - Chat & Voice: documents that it handles chat AND small conversational automations (titles, tags). Recommends OLLAMA_NUM_PARALLEL=2+ on the Ollama server so background automations get their own KV-cache slot and don't evict the chat model's working state. - Curator: notes the app enforces SERIAL execution regardless of NUM_PARALLEL — only one curator pass runs at a time. This matters most for 70b CPU models where a second instance would waste system RAM. 3. Enforce serial curator execution globally: - New module-level _CURATOR_RUN_LOCK in services/curator.py. - run_curator_for_conversation now wraps its body in 'async with _CURATOR_RUN_LOCK' — every entry point (scheduler sweep, manual route trigger, future hooks) is serialized through it. - is_curator_running() helper exposes the lock state. - routes/journal.py manual trigger checks is_curator_running() first and returns 409 {busy: true} immediately rather than blocking the HTTP request for minutes waiting for a 70b CPU pass to finish. The user can retry once the curator clears. Why a 409 instead of queue: a curator pass on a 70b CPU model can take 5+ minutes. Tying up an HTTP worker that long is bad; making the user wait without feedback is worse. 409 surfaces the busy state immediately and the user retries when they want. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-24 11:30:42 -04:00
bvandeusenandClaude Opus 4.7	85b212fbf2	refactor(models): route tasks to chat vs worker per new architecture ... Chat and background model roles effectively swapped during the conversation+curator pivot, but call sites still used OLD routing. This commit re-routes each call to the model whose new role fits. Moved to background_model (worker — heavy, deliberate): - services/journal_prep.py: daily prep generation. - services/user_profile.py: observation consolidation. Moved to default_model (chat — small, fast): - services/chat.py save_response_as_note: note title generation. - services/tag_suggestions.py: tag suggestions. Already routed correctly (unchanged): curator, closeout, consolidation, project summaries, history summarization. SettingsView.vue: help text rewritten for both model fields to describe new roles. Background Model UI label renamed to Worker Model so the heavier role is visible from the picker. Warning copy updated to recommend OLLAMA_MAX_LOADED_MODELS=2+ so chat and worker can stay loaded simultaneously. Schema names default_model and background_model unchanged on purpose (renaming requires migration + touches ~50 call sites for UX-only gain). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-23 11:00:47 -04:00
bvandeusenandClaude Opus 4.7	37596ce31c	remove(llm): retire think_enabled setting entirely ... Two-in-one cleanup motivated by the chat hang in dev 2026-05-22. The crash root cause from the guarded-task traceback: UnboundLocalError: cannot access local variable 'get_setting' where it is not associated with a value File generation_task.py:257, in run_generation think = (await get_setting(user_id, 'think_enabled', 'false'))... generation_task.py imports get_setting at module top, but a later 'if voice_mode: from ... import get_setting' block scopes it as a function-local. When voice_mode=False the local import never runs, but Python had already flagged get_setting as local for the entire body — the think_enabled read at line 257 hit UnboundLocalError. The line itself was dead-weight anyway. With the conversation+curator architecture: chat ships tools=[] (think on a no-tools pass is pure latency cost; nothing for the model to reason ABOUT in tool-call terms), and the curator hardcodes think=False already. The user setting was a holdover from before the architecture pivot. Removing it entirely is cleaner than fixing the scoping bug to preserve a toggle nobody should be using: - generation_task.py: think hardcoded False. Removed the get_setting call (which fixes the UnboundLocalError as a side effect). - SettingsView.vue: dropped the Enable model thinking checkbox, the thinkEnabled / savingThinkEnabled refs, the saveThinkEnabled function, and the think_enabled load step. - Migration 0050: DELETE FROM settings WHERE key='think_enabled' to clean up any stored rows. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-22 21:03:25 -04:00
bvandeusenandClaude Opus 4.7	39ab5d69a9	feat(voice): admin UI to browse + install piper voices from HuggingFace ... Building on the kokoro→piper swap (B1), this adds the admin-side voice management story so additional voices can be installed without rebuilding the image. The bundled two voices stay as immediate defaults; everything else is opt-in via a one-click install from the catalog. Backend (services/voice_library.py): - fetch_catalog() pulls voices.json from the piper-voices HF repo with a 24h in-memory TTL. Manual refresh available via ?refresh=1 on the library endpoint. - shape_catalog_for_ui() projects the raw HF dict (~250 voices, lots of nesting) into UI-friendly cards: id, name, language, country, quality, size, install state. Sorted by language_code then name for stable display. Install state distinguishes bundled (read-only) from user (admin-installed, can be removed). - install_voice() downloads .onnx + .onnx.json into /data/voices with atomic .tmp → rename so a failed partial download can't leave a corrupt model around. Idempotent — re-installing an already-present voice is a no-op. - uninstall_voice() removes /data voices; bundled /opt voices raise PermissionError (403 at the route layer). - Strict voice-id regex prevents path traversal in install/uninstall. Routes (admin-only, since these write to shared /data and affect all users on the instance): - GET /api/voice/voices/library - POST /api/voice/voices/install - DELETE /api/voice/voices/<voice_id> Frontend: - New "Voice Library" section in Settings → Voice, visible only to admin users. Collapsed by default; expand to load the catalog on-demand (doesn't hammer HF for non-admins). - Free-text filter across id, language code, language name, country, and dataset name. Refresh button forces a catalog re-fetch. - Per-voice row shows id, language/country/quality/speaker count, size, and either an Install button, a Remove button (user voices), or a "bundled" badge (read-only voices in /opt/piper-voices). - Installs and uninstalls refresh both the library list AND the active voice picker so the new voice is immediately selectable. - VoiceLibraryEntry exported from api/client.ts; new client helpers getVoiceLibrary/installVoice/uninstallVoice. Tests: - Pure-transformation unit tests for shape_catalog_for_ui, _resolve_file_urls, and the voice-id regex (path-traversal coverage). - DB/network paths (fetch_catalog, install_voice) need a real environment — left to CI integration tests or device verification. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-22 08:18:22 -04:00
bvandeusenandClaude Opus 4.7	a28f75994a	feat(voice): swap kokoro TTS → piper-tts ... Kokoro has been stale upstream since April 2025 (`requires_python<3.13`), which broke the Python 3.14 build. Piper is the active replacement: maintained by OHF/Home Assistant, depends only on onnxruntime + pathvalidate (no torch, no spacy, no transformers), and has cp314 support today. Dockerfile: - Add `pip install piper-tts` after the STT install. - Bundle two default voices (en_US-amy-medium, en_US-ryan-medium) into /opt/piper-voices at build. Additional voices can be downloaded into /data/voices via the admin UI (separate commit). - Image add over the STT-only baseline: ~150 MB. services/tts.py — full rewrite: - New voice-discovery layer scans /opt/piper-voices + /data/voices for .onnx + .onnx.json pairs. /data wins over /opt for the same id so admin-downloaded voices can override bundled defaults. - Single PiperVoice kept warm; switches via _switch_voice() when the user changes their voice_tts_voice setting. - list_voices() returns metadata read from .onnx.json sidecars (label derived from filename, language, quality, sample_rate). - synthesise() uses piper's SynthesisConfig; converts kokoro-shaped `speed` multiplier to piper's `length_scale` (1.0 / speed). - `voice_blend` parameter accepted but ignored — piper has no blend equivalent; first entry's voice is used if anything is passed. - Dropped: HuggingFace commit-hash tracking (~80 lines), the daily check_for_kokoro_updates task, voice-tensor blending math. routes/voice.py: - tts_backend reports "piper" in /api/voice/status. - /api/voice/voices no longer requires tts_available() — even with the active voice failed to load, the catalog still lets the user pick a different one. - Synthesise request body dropped the voice_blend field; speed and voice still supported. alembic 0047_reset_voice_tts_settings: - Deletes any stored voice_tts_voice (kokoro IDs that don't map to piper) and voice_tts_blend (no piper equivalent) rows. Both re-default cleanly on next read. frontend: - VoiceBlendEntry type removed from api/client.ts. - synthesiseSpeech() signature dropped the voiceBlend parameter. - SettingsView.vue Voice Blend section removed entirely (slider, preview, slot management). voice_tts_blend save path removed. - Default voice id changed from "af_heart" to "en_US-amy-medium". - VoiceEntry gains optional language/quality/sample_rate fields from the richer piper sidecar metadata. Voice paths remain lazily guarded — `VOICE_ENABLED=false` (default) starts the app cleanly regardless of which TTS deps are present. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-22 07:59:09 -04:00
bvandeusenandClaude Opus 4.7	d345b32856	feat(llm): user-controlled think mode (default off); remove qwen3 hardcode ... The chat generation pipeline previously forced think=True unconditionally to match qwen3's combined think+tools template, locking the system into that model family. Bench data (2026-05-21, qwen3:30b-a3b/qwen3:32b on CPU) showed thinking adds 1-2 minutes per turn for unclear quality benefit — qwen3:30b-a3b even produced more rambling with think on. This decouples think from the model family by reading a per-user `think_enabled` setting (default `false`). Non-qwen3 models can now run through the same pipeline without the silent-generation failure mode that content-gated thinking would have caused — they just don't think. qwen3 users who still want thinking can opt in via the Settings UI. Settings UI: - New "Enable model thinking" checkbox in General → Assistant section. - Help text explains the default-off rationale and when to opt in. - Persists via the existing settings API; no schema migration needed (Setting is key/value text). Telemetry to confirm whether this regresses tool-call reliability on qwen3 (the current model) is in a follow-up commit (generation_tool_log). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-21 22:00:44 -04:00
bvandeusen	b519a1c140	feat(frontend): auto-consolidate tasks toggle in General settings ... New Tasks section in the General tab with a single checkbox controlling whether the consolidation pipeline fires automatically. Persists to the auto_consolidate_tasks user setting (string 'true'/'false'). Manual 'Re-consolidate' in the task editor bypasses the gate.	2026-05-13 12:23:06 -04:00
bvandeusenandClaude Opus 4.7	bb650ba563	feat(profile): Settings panel with recent journal observations ... Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-12 14:44:51 -04:00
bvandeusenandClaude Opus 4.7	c663532fd4	feat(profile): Settings toggle for nightly journal closeout ... Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-12 14:43:59 -04:00
bvandeusenandClaude Opus 4.7	bc239119f3	fix: SettingsView TS errors + calendar month/year font ... CI typecheck failed: JournalLocation interface requires `address: string`, but Profile-tab Locations code created defaults like `{ label: 'Home' }` without it. Symptoms were six TS2741 errors in SettingsView.vue. Fix: include `address` in defaults and treat the user's place-name input as the address field. Now homeQuery / workQuery sync to locations.{home|work}.address — both at load time and on geocode. loadJournalConfig now reads address (was reading label, which is fixed to "Home"/"Work"); geocodeFor writes the typed query into address while also setting lat/lon on success. Calendar Month/Year title was actually rendering Fraunces, not Inter as I'd claimed. FullCalendar renders .fc-toolbar-title as an <h2>, which the global theme.css `h1, h2 { font-family: 'Fraunces' }` rule catches before the parent .fc font-family inherit can do anything. At 1.1rem it's below the doc's "Fraunces only at ≥18px" threshold, so explicit Inter override on the deep selector. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-28 07:58:15 -04:00
bvandeusenandClaude Opus 4.7	30dfbce426	fix(typography): strip chrome italic; reserve italic for emphasis ... Per the design rule "italic is for emphasis, not for design", removed every chrome `font-style: italic` declaration across the frontend. 42 declarations gone across 24 files: empty-state placeholder copy, loading messages, "no results" hints, ghost text, voice/role labels, field placeholder text, brand wordmark, et al. Markdown content emphasis is unaffected — `<em>` and `<i>` tags from `*emphasis*` markup still render italic via browser default styling (prose.css doesn't override em behavior). User-typed emphasis in notes, journal entries, and chat messages keeps its italic. Specific spots that lost the decorative italic: - KnowledgeView .filter-label, .empty-narrator - NoteEditorView .ef-label, link-suggest related - ChatPanel .empty-msg, .empty-greeting, .role-label - ChatMessage .role-assistant .role-label (the "Fable" voice tag — was italic per the doc's Illuminated Transcript spec, but per the new typography rule the speaker tag stays regular and lets the border-left + glow do the bubble framing on their own) - AppHeader .brand-text ("Fabled" wordmark) - editor-shared.css .title-input::placeholder - ProjectView .project-title-input::placeholder - HomeView .urgency-loading - WorkspaceTaskPanel .empty-group - WeatherCard .weather-unavailable - SharedWithMeView .empty-msg - DiffView empty-state spans - ToolCallCard .tool-event-more - SettingsView 7 spots (.you-label, .geo-pending, hint text, etc.) - + several other empty-state / hint text spots Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-28 07:54:26 -04:00
bvandeusenandClaude Opus 4.7	39d56cfcf3	feat(settings): re-add journal config to Profile tab; clear briefing remnants ... The Briefing Settings section was removed during the briefing→journal migration but its data (locations, temp unit, prep schedule) is still read by the journal backend. There was no UI to set any of it, so weather couldn't render and prep timing wasn't tunable. Re-adds the missing config inside the existing Profile tab — it's all "about the user" data and a separate Journal tab would just clutter the sidebar. New sections: Locations (after Work Schedule) - Home and Work place-name inputs with on-blur geocoding via /api/journal/weather/geocode - Temperature unit toggle (Celsius / Fahrenheit) - Status messages distinguish ok / pending / error Journal (before What the Assistant Has Learned) - Daily prep auto-generate toggle - Prep generation hour:minute (24-hour input) - Day rollover hour (so 1–3am entries still count as the previous day) - All controls disable cleanly when prep is off Cleanup - Profile "About You" desc: "chat and briefings" → "chat and the daily journal" - Profile "Interests" desc: "personalise news and briefing context" → "personalise the journal's daily prep and chat responses" - Profile "Work Schedule" desc: "Helps the briefing" → "Helps the journal" - Profile "What the Assistant Has Learned" desc: clarifies the summary is included in the journal's system prompt; observations come from journal + chat (not briefing) - General "Timezone" desc: "schedule briefings" → "schedule the daily journal prep" - Removed the dead `.briefing-*` CSS block (~190 lines of styles for retired briefing UI: feed-row, slot-row, add-feed-form, etc.) and replaced with fresh `.location-row`, `.unit-toggle`, `.unit-btn`, `.checkbox-label`, `.time-row`, `.time-input`, `.geo-msg` rules used by the new sections. unit-btn.active uses Moss action-primary per Hybrid; tokens flow through the rest. The "What the Assistant Has Learned" section was confirmed load-bearing for the journal — `journal_pipeline.py:139` calls `build_profile_context()` which feeds learned_summary plus other profile fields into the journal's system prompt. Not a remnant. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-28 00:05:07 -04:00
bvandeusenandClaude Opus 4.7	541e2ed713	feat(design): surface phase PR 6 — Settings polish ... Settings is the densest button surface in the app. Per the surface- phase spec, classify every button on a deliberate token. Button reclassification per Hybrid rule - btn-save (~13 instances across General/Account/Notifications/ Integrations/Data/Briefing/Admin tabs): flat accent → Moss action-primary - btn-primary (Groups tab "Save Retention", "+ New Group"): flat accent → Moss action-primary - btn-secondary (Detect timezone, Test SMTP, Refresh, Export, Add slot, Preview voice, etc.): outline-on-bg-secondary + hover-to-accent → Bronze action-secondary, filled - btn-danger filled (Reset VAPID, Revoke API key Yes): added the rule (was previously unstyled — relied on no-rule). Now Oxblood action-destructive. - btn-danger-outline (Invalidate sessions, Clear observations, Delete personal data): generic --color-danger → Oxblood action-destructive - btn-danger-sm hover (group + member delete): --color-danger → --color-action-destructive - btn-delete row hover, btn-confirm-delete (user delete two-stage): --color-danger → Oxblood. Confirm filled, cancel ghost. - btn-toggle-open ("Open registration"): flat accent → Moss - model-delete-btn hover: --color-danger → Oxblood - btn-warn hover: muted-border-warning → filled-warning Two-weights-only - Snapped every font-weight 600/700 to 500. Out of scope for this PR - Voice/tone copy audit across labels and help text — per spec, opportunistic only. Skipped. - Settings row de-bordering — current section dividers are structural; left as-is. - Validation-state colors (.input-error etc.) keep --color-danger (Error terracotta) per the doc — Error is for validation/error messages, Oxblood is for destructive actions. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-27 23:13:38 -04:00
bvandeusenandClaude Opus 4.7	93a3beb5d6	feat(design): surface phase PR 1 — Lucide icon migration + scale enforcement ... Replaces every hand-inlined SVG in the chrome (60 across 15 files) with Lucide components. Snaps icon sizes to the doc's 16/24 scale — all icons in this pass land at 16. AppLogo wordmark stays as the legitimate "custom app icon" exception per the doc; GraphView's <svg> mount point for D3 stays as well. Replaces emoji-as-icons in clear button-affordance cases with their Lucide equivalents: ✕ → X (close/dismiss buttons across 8 files), ✓ → Check (ProjectView task-advance button), 🎤 → Mic (ChatPanel voice CTA), 📎 → Paperclip (ChatView context toggle), &uarr; → ArrowUp (ChatInputBar Send), &times; → X (ChatPanel context-note remove), ☀/☾ → Sun/Moon (AppHeader theme toggle). Inline emoji punctuation in textual confirmation copy ("Saved ✓", "Created ✓", `done: "✓"` status maps, `'✓' : '📄'` interpolations) is left for surface-phase voice/tone touchups — replacing requires structural template changes and is best done per-component. Stroke weight stays at Lucide's default 2px; tightening to the doc's 1.5/1 is deferred per the surface-phase spec (option ii: drop-in + scale enforcement). Adds lucide-vue-next ^0.469.0 to frontend/package.json. Docker rebuild handles the install. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-27 19:56:01 -04:00
bvandeusenandClaude Opus 4.7	7a9a8b7819	feat(design): foundation pass — dusty violet palette, warm parchment light, Inter + JetBrains Mono ... Applies the FabledSword + Scribe iteration palette to theme.css end to end: indigo (#7c3aed) → dusty violet (#5B4A8A) accent, cool grey → Obsidian/Iron/Pewter dark surfaces, warm parchment (#F5F1E8) light mode, Inter body + JetBrains Mono code loaded alongside Fraunces, and neutral hairline scrollbars (chrome is structural, not branded). Adds the action token set (--color-action-primary Moss, --color-action-secondary Bronze, --color-action-destructive Oxblood, --color-action-ghost-border Pewter) but does not yet reclassify any buttons — surface-phase work. Buttons remain dusty-violet gradients in the meantime, by design. Removes deprecated --color-accent-warm; replaces concrete usages with --color-text-secondary (dates, flavor copy) or --color-warning (paused status). Sweeps hardcoded indigo literals in component scoped CSS so they don't bypass the token system. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-27 17:20:01 -04:00
bvandeusenandClaude Opus 4.7	dbd9f00061	refactor: hard-cut RSS infrastructure (scope C) ... Removes the entire RSS feature surface — feeds, items, embeddings, reactions, discussion-note flow, briefing news context, settings, env-vars, and DB tables. Keeps the URL-generic article-reader (the read_article LLM tool) under a clean module so the LLM can still fetch arbitrary article content from URLs the user provides. Backend: - New services/article_fetcher.py — single source of trafilatura URL→text - New services/tools/article.py — read_article tool (was nested under tools/rss) - Delete services/rss.py, rss_classifier.py, rss_filtering.py, article_context.py - Delete services/tools/rss.py - Delete models/rss_feed.py (RssFeed, RssItem), models/rss_item_embedding.py - services/embeddings.py: drop upsert/semantic_search/backfill RSS helpers - services/llm.py: remove _build_briefing_article_context, briefing-conv branch, ARTICLE_DISCUSS_SEED skip-RAG branch; drop get_rss_items / add_rss_feed from the actions list - services/generation_task.py: drop _maybe_save_article_discussion_note + caller - routes/chat.py: drop /api/chat/from-article/<id> endpoint - routes/journal.py: re-import via web.py refactor (article_fetcher path) - services/tools/__init__.py: register `article`, drop `rss` - services/tools/_registry.py: drop the requires=='rss' check - app.py: drop backfill_rss_item_embeddings + backfill_rss_article_content tasks - config.py: prose-only edit (no env var change — RSS env vars were never first-class) Frontend: - stores/settings.ts: drop rssEnabled - SettingsView.vue: drop the RSS-classification mention - api/client.ts: drop openArticleInChat (the from-article endpoint is gone) Tests: - Delete tests/test_rss_service.py, test_news_api.py, test_article_reading.py Migration: - 0042_drop_rss: DROP TABLE rss_item_embeddings, rss_item_reactions, rss_items, rss_feeds; DELETE settings rows for rss_enabled / briefing_*_topics Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-26 12:33:30 -04:00
bvandeusenandClaude Opus 4.7	7602bf2293	feat(briefing): hard-cut tear-down ... Backend: - Delete briefing services (pipeline, scheduler, conversations, profile, tools) - Delete routes/briefing.py + remove blueprint registration - Move _get_temp_unit into services/weather.get_temp_unit (reads top-level temp_unit setting) - Rename briefing_preferences.py → rss_filtering.py (functions are RSS-specific) - Strip briefing scheduler hooks from app.py - Strip briefing scheduler call from routes/settings.py - Update test imports (test_rss_service, test_tz_helpers) Frontend: - Delete BriefingView, BriefingSetupWizard, BriefingToolStatusRow - Strip /briefing route + nav links (AppHeader, KnowledgeView) - Strip Settings → Briefing tab + state + functions + imports - Strip briefing-intermediate handling from ChatMessage - Hide /news route + nav links (NewsView depended on briefing endpoints; orphaned in tree) - Drop unused useSettingsStore from AppHeader The Android BriefingScreen lives in a separate repo and is not touched here. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-25 22:33:37 -04:00
bvandeusenandClaude Opus 4.7	e652dece9b	refactor: rename Fabled Assistant to Fabled Scribe ... Updates user-visible branding across frontend (PWA manifest, page title, Settings, push fallback), backend (email templates and subjects, LLM system prompt, CalDAV displayname, SMTP from-name default), README, quickstart compose, and MCP server description. Also updates the CI image path and quickstart image reference to git.fabledsword.com/bvandeusen/fabledscribe in preparation for the Forgejo repo rename. Internal Python package, env vars, and database schema unchanged. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-25 16:28:25 -04:00
bvandeusenandClaude Opus 4.6	3ac32dc3bc	feat: add rss_enabled user setting to toggle RSS functionality ... RSS is now off by default. When disabled: - Scheduler skips RSS feed sync during compilation slot - Briefing pipeline skips RSS item gathering - RSS LLM tools (get_rss_items, add_rss_feed) are hidden - API routes return empty results for feeds/news - Frontend hides News nav link, RSS Feeds and News Preferences in settings - Briefing view hides news sidebar section Toggle in Settings > Briefing > RSS / News. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-04-17 13:58:50 -04:00
Bryan Van DeusenandClaude Opus 4.6	102c0b74a0	feat(settings): tabbed MCP install instructions with Claude Code flow ... Replace the hand-edit-JSON instructions in Settings → API Keys with a tabbed UI (Claude Code / Claude Desktop / Other). The Claude Code tab leads with the `claude mcp add` command, pre-filled with FABLE_URL and the most recently generated API key, plus copy-to-clipboard buttons on every snippet. Recommend `uv tool install` or `pipx install` over bare `pip install` so fable-mcp reliably lands on PATH under PEP 668. Also fix incorrect priority values in fable-mcp tool docstrings — the enum is `none|low|medium|high`, not `low|normal|high`. DRY pass: extract shared `copyToClipboard()` helper used by both `copyApiKey` and the new snippet buttons; reuse existing `btn btn-secondary btn-sm` for the copy buttons instead of a bespoke class. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-10 12:35:50 -04:00
bvandeusenandClaude Sonnet 4.6	2ac894b5d1	refactor(theme): DRY hardcoded violet values into CSS custom properties ... Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-08 12:19:38 -04:00