5 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 4.8	322cbc3b5e	feat(mcp): Phase 5 — write-time near-duplicate gate (update-over-create) ... #755 Phase 5. create_note / create_task now BLOCK a near-duplicate instead of silently inserting: they return {"duplicate": true, "existing_id", message} pointing at the record to UPDATE. Fights store bloat and stale competing copies that semantic search (RAG) would otherwise resurface for reconciliation. A force=true override creates anyway for genuinely-distinct records. - services/dedup.py: find_duplicate_note — two signals, scoped to owner + same project + same kind: (1) normalized-title exact match (cheap, always); (2) semantic cosine ≥ 0.90 but ONLY when body ≥ 200 chars (short/title-only embeddings false-positive — the pre-pivot lesson). Project-less (orphan) records compare only to other orphans on BOTH signals (orphan_only on the semantic call) — they're not matched across every project. - Gate wired into the MCP create_note/create_task tools (the LLM write path) with force override; _INSTRUCTIONS documents the duplicate response + force. - Opt-in by design: the service helper is only called from the interactive create tools. Internal/programmatic creates (recurrence spawn, imports) go straight through services.create_note and are NOT gated — a recurring task spawning its next same-titled instance must not be blocked. - Scope v1: MCP tools only. REST/web (human CRUD, needs a UI affordance) and create_rule (not a RAG surface; _INSTRUCTIONS already steer it) are follow-ups. - tests: dedup service (title/semantic/body-gate/type-filter) + tool gate (blocks, force bypasses) for notes and tasks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 13:21:35 -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
bvandeusen	a40334312f	test(trash): update delete-tool tests to soft-delete contract (patch trash_svc.delete)	2026-05-29 09:24:58 -04:00
bvandeusenandClaude Opus 4.7	6aa84002b3	refactor(mcp): drop fable_ prefix from tool names; rebrand to Scribe ... MCP clients see tools namespaced by the server's local name already (mcp__<server>__<tool>), so the fable_ prefix on every tool name was redundant and ate tokens in the model's tool list. Tools renamed (34 total): fable_search → search fable_list_notes / get_note / create_note / update_note / delete_note → list_notes / ... fable_list_tasks / get_task / create_task / update_task / add_task_log → list_tasks / ... fable_list_projects / get_project / create_project / update_project → list_projects / ... fable_list_milestones / create_milestone / update_milestone → list_milestones / ... fable_list_events / create_event / get_event / update_event / delete_event → list_events / ... fable_list_tags → list_tags fable_get_recent → get_recent fable_list_persons / create_person / update_person → list_persons / ... fable_list_places / create_place / update_place → list_places / ... fable_list_lists / create_list / update_list → list_lists / ... Also rebranded in MCP scope: FastMCP("fable", ...) → FastMCP("scribe", ...) auth realm "fable-mcp" → "scribe-mcp" ASGI scope key fable_user_id → scribe_user_id ContextVar label fable_mcp_user_id → scribe_mcp_user_id Tool docstrings "in Fable" / "Fable task" → "in Scribe" / "Scribe task" Server _INSTRUCTIONS prose Deliberately kept: - The internal Python package name `fabledassistant` (per project naming convention — internal stays). - "Fabled Scribe" as the official product/brand name (page footer, smtp_from_name default). - References to the legacy `fable-mcp/` standalone package in docstrings explaining what we ported from — accurate until that directory is deleted in Phase 10. Client impact: existing MCP registrations need claude mcp remove <name> && claude mcp add ... once with a freshly-copied snippet from Settings → MCP Access. Claude Code then re-discovers tools on connect — old conversations that referenced fable_* tool names will see "tool not found" on those calls until updated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 11:48:55 -04:00
bvandeusenandClaude Opus 4.7	b026421985	feat(mcp): note CRUD tools (list/get/create/update/delete) ... Five tools wrapping services/notes.py with is_task=False. Signatures mirror the existing fable-mcp note tool contracts so Claude usage is unchanged. Key behavior the tests pin down: - list_notes repackages (rows, total) tuple into {notes, total} - tag=""/search_text="" are "no filter" sentinels - update_note ONLY sends non-default fields to the service (the main risk: a default empty string overwriting real data) - tags=[] is an explicit clear; tags=None is "leave unchanged" - project_id=0 on create => orphan; on update => leave unchanged (preserved limitation from existing fable-mcp) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-26 20:20:27 -04:00