MCP instruction hardening + milestone-unset #56

Merged

bvandeusen merged 4 commits from dev into main 2026-06-03 11:19:09 -04:00

Conversation 0 Commits 4 Files Changed 3

+94 -7

4 Commits

Author	SHA1	Message	Date
bvandeusenandClaude Opus 4.8	f446573c3d	feat(mcp): proactive project bootstrapping at session start ... Adds an always-on _INSTRUCTIONS directive: when work touches Scribe and no project is in scope, search for a related project and propose enter_project (confirm first), or offer to create one (confirm name/goal first) — never silently adopt or create. Pairs with the enter_project handshake and the host-memory pointer directive. Closes scribe task #585. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-03 11:01:55 -04:00
bvandeusenandClaude Opus 4.8	82d6812c7f	feat(mcp): milestone_id=-1 clears a task's milestone (update_task) ... Optional FKs on update_task previously had no way to express 'remove' — 0 meant leave-unchanged and any positive int meant set, so a milestone (or project) could only be cleared via the web UI. Now -1 clears the FK (NULL); clearing project_id also clears milestone_id since a milestone can't outlive its project. update_note already NULLs on None, so the change is confined to the tool wrapper. Closes scribe task #586. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-03 10:59:47 -04:00
bvandeusenandClaude Opus 4.8	8c9ca45479	feat(mcp): instruct agents to keep a Scribe-rules pointer in host memory ... When a project subscribes to a rulebook, the agent should ensure the host's persistent memory carries a pointer that engineering/workflow rules live in Scribe (loaded via list_always_on_rules / enter_project), plus a one-line note of the current project's work. Pairs with the existing 'don't duplicate rules into memory' directive: memory holds the pointer + project context, Scribe holds the rules. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-03 10:42:23 -04:00
bvandeusenandClaude Opus 4.8	e023c21aa1	docs(mcp): instruct agents to drive task lifecycle + log work ... Adds a 'keep task state honest' directive to the MCP _INSTRUCTIONS: set in_progress on start, log progress with add_task_log as you go, set done the moment work completes (never leave finished work at todo), and write a dated dev-log note on the project at significant landings. Reinforced in the update_task status docstring. App-layer + always-loaded, no rule/config needed — closes the gap where finished work (e.g. a shipped plan) sat open because the lifecycle was available but never prescribed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-03 09:24:26 -04:00