feat(mcp): S5 — issue-kind guidance across all instruction surfaces #73
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ships the never-landed S5 of plan #825 (T2 — Issues task_kind): the
kind=issuefeature existed in schema/tools/REST/UI, but every behavioral surface the plugin pushes to the agent still described the pre-kind convention ("tagissue" on acreate_note). Result: agents fixed bugs without reaching forkind=issueand dumped the work as logs on unrelated open tasks.Product surfaces updated (instance-agnostic, prose-only — no schema/tool-behavior change):
_INSTRUCTIONS: rewrite the "record a problem" bullet →create_task(kind="issue")with symptom→cause→fix +arose_from_id/system_ids, and an explicit "not a work-log on an unrelated task"; add Issue + System to the hierarchy section.issue" / create_note-issue →create_task(kind="issue").Tracking: issue #855. Meta-principle captured as project rule #119 (product behavior belongs in the app, not in Scribe rules).
🤖 Generated with Claude Code