Cleanup: audit marketplace/skills so agents don’t learn deleted surface #115

Activity

1. pewpewpotato

   added the

   Task

   issue type on Sep 19, 2026
2. pewpewpotato commented on Sep 19, 2026

   

   pewpewpotato

   on Sep 19, 2026

   ContributorAuthor

   More actions

   Architecture design (normative for #115)

   Stored for TL plan. Aligns with PM product context.

   Source of truth for verbs

   • Canonical KEEP/REMOVE lists: internal/surface in autonomous-bits/spool (post-CLI/MCP: keep happy-path + context mgmt; delete Spool-VCS/Rack surface #110/KEEP: dedicated bound mutate tool for node/edge writes (not schema-migrate-only) #112), including CLI mutate / MCP spl_mutate.
   • Skills must not invent command or tool names. If a skill needs a verb not on KEEP, that is a product/architecture gap — open an issue; do not teach a workaround that reopens REMOVE.
   • Prefer MCP tool ids (spl_*) in agent-facing skills; CLI forms (spl …) OK for human/CLI skills. Both must match KEEP.

   What skills may teach

   Allowed	Notes
   Bind / context init --remote	Explicit bind file; refuse unbound writes
   mcp	Server over KEEP tools only
   mutate / spl_mutate	Graph-first ops batch → short-lived branch + PR
   query-context, search, search-expand, filter, resolve, graph	Bound projection reads
   schema / validate	Schema-first; not the general graph editor
   asset *	LFS policy unchanged (512 KiB)
   Graph merge *	File-graph merge via ctxgit, not Rack leases
   prune	Ephemeral nodes/edges → branch+PR; not pack GC
   context export / migrate-once	Escape hatch only — lossy one-shot; never ongoing SoT
   Stock git / GitHub PR review	Real review plane for context remote

   Forbidden (must not appear as current guidance)

   • Rack as remote/host/sync, Rack tokens, lease merge UX
   • .spl as durable SoT or “open the local repo” as primary workflow
   • REMOVE verbs: add, status, commit, branch, switch, push, pull, clone, workspace, remote, history, diff, branches-containing, fsck, gc, pack prune, old migrate, cherry-pick, and MCP twins (spl_add, spl_commit, spl_context as query, …)
   • Dual-SoT / “sync with Rack then git” stories

   How to mention export without implying SoT

   One short pattern only, e.g.: “If you still have a leftover .spl store, run context export / migrate-once once into the bound context git remote, then stop using .spl. Export is lossy; re-run is overwrite-at-own-risk.” No ongoing “maintain .spl” steps.

   Stock git vs Spool MCP

   • Spool MCP/CLI: graph mutate/query/schema/assets/merge/prune/bind/export.
   • Stock git/GitHub: history, diff, branch list, PR review/merge of context remotes.
   • Skills may say “review the Spool PR in GitHub”; they must not reintroduce Spool history/diff wrappers.

   Rewrite vs delete

   • Rewrite in place established skill ids that still map to KEEP work (product/architecture/engineering/implementation skills).
   • Delete skills whose only purpose is Rack / .spl-as-SoT / REMOVE verbs.
   • No deprecated-but-published half-state.

   Scope of inventory

   1. autonomous-bits/spool-marketplace plugins/ (primary)
   2. Any skill/docs under or linked from autonomous-bits/spool that teach operating Spool (e.g. .agents/skills)

   Done-definition (architecture)

   • Inventory lists every skill touched and verb findings
   • Published skills teach KEEP only; forbidden terms absent from current guidance (history CHANGELOG OK)
   • Mentions of export use the escape-hatch framing above
   • No skill contradicts always-PR / bind / projection-rebuild locks from Strategy: spec solution-shared context git remote #99–KEEP: dedicated bound mutate tool for node/edge writes (not schema-migrate-only) #112

   Architect owns this design section; eng implements under TL plan after PM+Architect context is stored.