Guidance by ownership, placement and report-back, and no more guessed record ids #155
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: bvandeusen/FabledScribe#155
Reference in New Issue
Block a user
Merge requested by the operator on 2026-09-14 to unblock live testing. The plugin installs from
main, and the server image is built from it.What rides along (11 commits, all CI-green on
dev)#4016: records that cite each other are created together, and a guessed id is refused (
441a1ac)create_recordsMCP tool andstart_planning(body=, steps=): one transaction, with{{ref:N}}placeholders rewritten to real ids and titles.#Njust above the highest assigned id.Milestone 409 "Response shapes", steps 1–3
46d9134(#4010):create_task/update_task(and the REST routes) return aplacementblock: milestone, step N of M, progress, next open step. It is share-aware.b4dbc49(#4011): the newreporting-backskill with the reply shapes.7239e3c(#4012): the reporting reflex, and a one-linereport_backcue whenupdate_taskcloses a task.#4022: instruction surfaces stop describing the always-on tier removed by milestone 394 (
6c1fd28)Milestone 410 "One owner per piece of guidance" (decision #4027), steps 1–6
f3036f0(#4028): the guidance-topic registry and loss guard.0a29252(#4029): skills own the full reflexes and name no particular client.76bfd92(#4030):_INSTRUCTIONSbecomes a client-neutral index (1,597 chars); the live session context carries live state only.106e396(#4031): the Claude Code plugin becomes a thin adapter; its static context goes from 8,705 to 1,791 chars.15621fa(#4032):plugin/PACKAGING.md, the contract for packaging Scribe for other clients.c440c49(#4033): an exactly-one-owner guard replaces the tests that required every surface to repeat itself.After merge
No schema migrations.
🤖 Generated with Claude Code
Sessions predicted the ids their next creates would get and wrote them into plan bodies and reference notes before the records existed. The database never collides; the sequence is shared by every session and user, so any concurrent create took the guessed numbers and the references pointed at someone else's records. - create_records (new MCP tool) and start_planning(body=, steps=) create their records in ONE transaction: insert, flush for the real ids, rewrite {{ref:N}} / {{ref:milestone}} placeholders as #id "title", commit. No prediction, no waiting, no stub records left behind when a batch fails. Ids need not be consecutive and nothing depends on it. - Every MCP create/update of a note, task or milestone refuses a #N sitting just above the highest assigned id (within 50): that can only be a guess. Refusal, not warning. Numbers far above the max (PRs, forge issues) pass. - notes.build_note splits validation out of create_note so the batch validates records exactly as a single create does. - writing-plans and using-scribe say to pass steps up front and never write an unassigned id; plugin version minted. Integration test runs six concurrent batches and checks each resolves its placeholders to its own records, and that a failing batch writes nothing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>Step 1 of milestone 409 "Response shapes". An agent reporting finished work is asked to say which milestone it belongs to, which step of how many, and what is next. Without those facts to hand it reconstructs them, and a reconstruction reads exactly like the truth when it is wrong. create_task and update_task (MCP) and the REST create/update task routes now return a placement block: project; and for a task in a milestone, the milestone, position {step, of}, progress {completed, total, pct} and next (the next open step, falling back to the earliest open one before it). - Step order is creation order, not get_milestone listing order, which reshuffles on every update. - Siblings are read through readable_notes_clause; position and progress are computed over that same readable set, so a collaborator is never shown a step title they cannot open, and a note share alone reveals no plan. - Fail-open and omitted when empty, like every in-band decoration. - _no_embedding moves into conftest as one opt-in fixture for both integration modules that need it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>Step 3 of milestone 410 "One owner per piece of guidance". _INSTRUCTIONS is rewritten as an index for every MCP client (1,597 of 2,000 chars): orient, rules, recall, record, plan, ids, reuse, UI, report. Each line names its tool, and the block says every reflex is stated in full in the using-scribe skill and in each tool description. - names no client: CLAUDE.md, auto-memory and "the client injects ~2k chars" are gone - gains the two reflexes it lacked: records that cite each other go through create_records with {{ref:N}}, and reports start from `placement` The comment block above it now explains ownership (decision #4027) instead of accumulating per-milestone trade history, and keeps the budget and its reason (#2562). build_session_context states only what the server knows about this session: the active project and open work, its design system, an unbound-repo hint, or that no project is bound. Removed: the "you are not holding the operator's rules" section, the closing "Reflex: search Scribe" line, the design-system usage sentence, and the plugin-specific header. using-scribe owns all of that. The truncation note no longer restates the rules ask. Tests: a pin that the live context carries no rules reflex; the cap test drives truncation through the unbound-repo hint, since a bare session is now one line; the budget test message describes the index. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>