@sporhq/spor 0.2.1 → 0.2.3

package/.claude-plugin/marketplace.json

@@ -0,0 +1,14 @@
+{
+  "name": "spor",
+  "owner": {
+    "name": "Anthony Allen"
+  },
+  "description": "Spor context compiler — knowledge-graph briefings, capture, and decision queue for Claude Code",
+  "plugins": [
+    {
+      "name": "spor",
+      "source": "./",
+      "description": "Maintains a typed knowledge graph and compiles lineage-aware context briefings: session-start injection, per-prompt digests, capture at discovery, end-of-session distillation, decision queue"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,7 @@
+{
+  "name": "spor",
+  "displayName": "Spor Context Compiler",
+  "description": "Maintains a typed, versioned knowledge graph and compiles compact briefings from it: session-start injection, per-prompt relevance digests, capture at discovery, end-of-session distillation, decision queue.",
+  "version": "0.2.3",
+  "author": { "name": "losthammer" }
+}

package/README.md

@@ -64,10 +64,13 @@ For the per-host event mapping, fidelity notes, distiller backend, and the
 `AGENTS.md` fallback for hosts with no hook support, see
 [adapters/](adapters/).
 
-To start with a populated graph, point the bundled `spor-backfill` agent at
-your existing sources: it mines git history, design docs, and issue trackers
-into a first graph. Or skip that and just work — distillation grows the graph one session
-at a time.
+To start with a populated graph, ask your agent to run the bundled
+`spor-backfill` agent against your existing sources — in Claude Code:
+*"use the spor-backfill subagent to bootstrap a Spor graph for this repo."*
+It is a **subagent** (invoked through the Task tool, not a `/spor:` slash
+command), so it runs in its own context, mining git history, design docs, and
+issue trackers into a first graph. Or skip that and just work — distillation
+grows the graph one session at a time.
 
 ## What your agent gets, and gives back
 
@@ -88,7 +91,9 @@ The loop runs without you having to drive it:
 You can also ask for any of this directly: an on-demand briefing for a task,
 a correction when a briefing was wrong, a capture of work you're deferring,
 and a ranked queue of what to do next. In Claude Code these surface as
-`/spor:brief`, `/spor:correct`, `/spor:defer`, and `/spor:next`.
+`/spor:brief`, `/spor:correct`, `/spor:defer`, and `/spor:next`. (Graph
+bootstrapping is separate: `spor-backfill` is a *subagent* you invoke by
+asking your agent to use it — it does not appear in the `/spor:` slash menu.)
 
 Corrections are durable. When a briefing includes something stale or misses
 something it should have known, you record the correction once, and every

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sporhq/spor",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "Spor — a shared memory substrate for teams and agents. Decisions, their reasons, and the traces they leave. Knowledge-graph context compiler: session-start briefings, per-prompt digests, capture at discovery, end-of-session distillation, decision queue.",
   "license": "Apache-2.0",
   "author": "Anthony Allen",
@@ -26,6 +26,7 @@
     "spor-hook": "./bin/spor-hook.js"
   },
   "files": [
+    ".claude-plugin/",
     "lib/",
     "bin/",
     "scripts/engines/",

package/scripts/engines/session-start.js

@@ -61,6 +61,25 @@ function nodeBody(raw) {
   return u.stripTrailingNewlines(u.byteHead(awkOut, 7000));
 }
 
+// Durable repo-identity node text (issue-spor-onboard-no-repo-identity-node),
+// mirroring the server's learnFingerprints registration so local and remote
+// produce the same shape. Ungrouped by default — no grouped-under edge; the
+// standing grouping suggester proposes the single home project.
+function repoNodeMarkdown(slug, fp, today) {
+  return `---
+id: repo-${slug}
+type: repo
+title: ${slug}
+summary: Git-repo identity for '${slug}', auto-registered from its fingerprints when the repo first appeared in the local graph. Ungrouped — no home project yet; the grouping suggester proposes a grouped-under home.
+slugs: [${slug}]
+fingerprints: [${fp.join(", ")}]
+date: ${today}
+---
+
+Auto-registered repo identity for \`${slug}\` (issue-spor-onboard-no-repo-identity-node). Created on first sight so the repo is a first-class node: the anchor for rename-healing fingerprint matching and for a \`grouped-under\` home. It starts UNGROUPED by default — repo-scoped reads work on the slug, and the standing grouping suggester proposes its single home project for confirmation. Slug aliases and fingerprints accumulate here across renames and re-clones.
+`;
+}
+
 async function sessionStart(input) {
   const graph = u.graphHome();
   const nodes = path.join(graph, "nodes");
@@ -412,6 +431,26 @@ ${pbody}`;
     /* fail open */
   }
 
+  // Ensure this repo has a durable identity node once it actually has content
+  // in the graph (issue-spor-onboard-no-repo-identity-node). Mirrors the
+  // server's learnFingerprints in remote mode: a backfilled/distilled repo with
+  // no `type: repo` node yet gets one registered from its git fingerprints, so
+  // it is a first-class node — the anchor for a grouped-under home and for
+  // rename-healing. Gated on projCount>0 (real graph content), no owning repo
+  // node yet, and fingerprints present, so a session in some unrelated checkout
+  // never spawns an identity node. Ungrouped by default; the grouping suggester
+  // proposes the home. Pure side effect, written AFTER the briefing is built so
+  // it never alters this run's output; fail-open — never blocks session-start.
+  try {
+    const fp = cwd && fs.existsSync(cwd) ? u.repoFingerprints(cwd) : [];
+    const repoFile = path.join(nodes, `repo-${slug}.md`);
+    if (!owner && projCount > 0 && fp.length && /^[a-z0-9][a-z0-9-]*$/.test(slug) && !fs.existsSync(repoFile)) {
+      fs.writeFileSync(repoFile, repoNodeMarkdown(slug, fp, new Date().toISOString().slice(0, 10)));
+    }
+  } catch {
+    /* best effort — never block session-start */
+  }
+
   return envelope(ctx);
 }