@sporhq/spor 0.11.0 → 0.12.1

package/.claude-plugin/plugin.json

@@ -2,6 +2,6 @@
   "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.11.0",
+  "version": "0.12.1",
   "author": { "name": "losthammer" }
 }

package/API.md

@@ -90,6 +90,10 @@ Output: `{ "found": bool, "text": "<digest or full neighborhood>",
 
 Input `{ "id": "dec-..." }` → full raw markdown, parsed frontmatter, and
 `revision` (git blob SHA) for use in updates. Unknown id → not-found error.
+**Read-time enrichment** rides along on the same response: the node's active
+schema may carry a `get(node, ctx)` hook (GRAPH.md) that attaches derived
+context as extra top-level keys — e.g. `resolution` (what answered/resolved
+this node). These are additive; a client ignores keys it does not know.
 
 ### `put_node`
 
@@ -314,10 +318,11 @@ endpoint is the REST twin of a core call:
 | Endpoint | Typical caller | Semantics |
 |---|---|---|
 | `GET /v1/status` | session-start, monitoring | `{node_count, projects: {...}, head, uptime, metrics}`; doubles as the health check. `?titles=1` adds `titles: [{id, type, project, title}]` — the one-round-trip graph index the distiller dedups against |
-| `GET /v1/me` | `spor whoami`/`status`, onboarding | identity echo for the bearer token → `{person, name, email, bound, is_admin}`. `bound:false` means the token authenticates but maps to **no person node** (legacy/OAuth, or minted before the node existed), so routed questions and the personal queue will be empty — the client warns on it (the silent identity-degradation signal). `is_admin` reflects the `stewards→root` edge that gates the token-admin surface |
+| `GET /v1/me` | `spor whoami`/`status`, onboarding | identity echo for the bearer token → `{person, name, email, bound, is_admin, org}`. `bound:false` means the token authenticates but maps to **no person node** (legacy/OAuth, or minted before the node existed), so routed questions and the personal queue will be empty — the client warns on it (the silent identity-degradation signal). `is_admin` reflects the `stewards→root` edge that gates the token-admin surface. `org` is the slug this tenant routes to (`SPOR_ORG`/legacy `SUBSTRATE_ORG`, else `"local"`); it lets a client key its `(issuer, org)` credential store for an **opaque** `spor_oat_`/`spor_pat_` token that carries no readable `org` claim — the client falls back to it after `--org` and the JWT `org` claim (task-spor-frontdoor-me-org-echo). A connector JWT's `org` claim is enforced equal to this echo |
+| `GET /v1/me/org-choices` | `spor auth list` (live membership refresh) | re-queries the IdP's *current* org membership for the held credential's subject and returns `{org_choices: [{slug, label, default?}], source: "idp"\|"bound"}` — `source:"idp"` is a true live enumeration (orgs added/removed since the last login surface without re-authenticating); `source:"bound"` means a single org-scoped token the server couldn't expand (no enumeration). The client treats only `source:"idp"` as live and **fails open** to its cached tenant listing on anything else — `source:"bound"`, a `502 {error.code:"membership_requery_failed"}` (IdP unreachable), a `404` (older server without the endpoint), or any transport/parse error (task-spor-cli-auth-list-live-membership-requery; server half task-spor-frontdoor-held-credential-membership-requery) |
 | `GET /v1/briefing/{project}` | session-start | read the `brief-<project>` node → `{found, version, body, project_brief?, graph_status}`. The slug resolves through project-node aliases (GRAPH.md "Project identity nodes") before lookup. A BARE repo slug also rides up to its home-project grouping: the grouping's `brief-<grouping>` node returns alongside as `project_brief` (the product context spanning sibling repos), matching the shared up-resolution (dec-spor-queue-slug-resolves-to-grouping); passing the repo NODE id (`repo-<slug>`) is the escape hatch that returns only the repo brief, no `project_brief`. Optional `?fp=root:<sha>,remote:<host/path>,...` carries the repo's fingerprints: the server learns them onto the owning project node, and an unknown slug with a known fingerprint files an alias proposal in the queue |
 | `POST /v1/digest` `{query, root?, project?, min_sim?}` | prompt-context, /spor:brief | digest-mode compile → `{found, text}`; `found: false` is a successful empty result. `root` is the structural-walk twin of `query` (the two are mutually exclusive; `root` wins, an unknown id is `422`). Optional `project` is the session slug: the server scopes the compile to it — the same-project relevance boost, the grouping union, and the `always_on` norm `applies_to_*` ride-along — resolving the slug through project-node aliases/groupings inside compile (dec-spor-queue-slug-resolves-to-grouping), exactly as `/v1/queue` does. A bad slug is `422`; **omitting `project` runs the digest project-blind (byte-identical to before)**, so older clients that send only `{query}` are unaffected |
-| `GET /v1/nodes/{id}` | /spor:brief | `get_node` semantics; a live inbound resolves/answers edge rides along as `resolution` (carrying the resolver's `summary`/`title` and a `lagging` flag — set when it contradicts a still-open status, clear when the node is already terminal, e.g. an answered question pointing at its answer), and open gardener findings about the node ride along as `open_findings` |
+| `GET /v1/nodes/{id}` | /spor:brief | `get_node` semantics; the node's active schema may attach read-time enrichment via a `get(node, ctx)` hook (GRAPH.md) — the seed `question`/`issue`/`task`/`incident` schemas attach `resolution`: a live inbound resolves/answers edge carrying the resolver's `summary`/`title` and a `lagging` flag (set when it contradicts a still-open status, clear when the node is already terminal, e.g. an answered question pointing at its answer). Open gardener findings about the node ride along as `open_findings`, and a node marked stale by an inbound supersedes edge as `superseded_by`. All enrichment is additive top-level keys; ignore unknown ones |
 | `POST /v1/nodes` | drain-outbox, mechanical writers | `put_node` semantics, batch: `{nodes: [...], if_exists: "skip"}` (entries may be raw strings or `{node, if_exists, revision}`) → `{results: [...]}`, 207 when any entry failed |
 | `POST /v1/nodes/{id}/edges` `{type, to, attrs?}` | scripts, mechanical writers | `add_edge` semantics (§1): normalize/flip, dedupe, append — no revision echo. Optional `attrs` adds trailing flat edge attributes (e.g. a per-assignment `profile:` override); re-adding the same edge with different attrs upserts the set |
 | `POST /v1/nodes/{id}/status` `{status}` | scripts, mechanical writers | `set_status` semantics (§1): one-scalar update through the `transitions()` gate. Setting a work node to an in-progress status also CLAIMS it (same lease as `/claim` below) |
@@ -428,6 +433,33 @@ anything with a token.
   `{name, email}` attribution record. Access tokens are `spor_oat_…` (30d;
   legacy `sub_oat_…` accepted); refresh tokens are `spor_ort_…` (90d,
   rotating, single-use). Authorization codes are single-use, 10-minute.
+- **CLI interactive sign-in — the device authorization grant.** `spor auth
+  login` (flat alias `spor login`) defaults to the OAuth 2.0 device
+  authorization grant (RFC 8628), brokered at the Spor front door so it works
+  headless / over SSH (dec-spor-cli-auth-device-grant-front-door). Flow:
+  `POST /oauth/device_authorization {client_id?, scope?}` →
+  `{device_code, user_code, verification_uri, verification_uri_complete,
+  expires_in, interval}`; the CLI prints the URL + code (auto-opening a local
+  browser when one is present), the human approves in any browser (the
+  verification leg runs the same AuthKit login + org resolution as the
+  connector flow), and the CLI polls `POST /oauth/token
+  {grant_type: urn:ietf:params:oauth:grant-type:device_code, device_code}` —
+  answering `authorization_pending`/`slow_down` until approval, then minting the
+  same person-bound, **org-scoped**, refreshable `spor_oat_…`/`spor_ort_…` pair
+  `addGrant` mints. `--web` is the localhost-loopback optimization for when a
+  browser is on the same machine (OAuth 2.1 authorization-code + PKCE, RFC 8252):
+  the CLI binds a one-shot `http://127.0.0.1:<port>/callback` listener,
+  anonymously registers a public client for it (`POST /oauth/register`, RFC 7591),
+  opens the browser to `GET /oauth/authorize {response_type=code, client_id,
+  redirect_uri, code_challenge, code_challenge_method=S256, state, scope?}`,
+  captures the redirected `?code` (CSRF-checked against `state`), and exchanges it
+  at `POST /oauth/token {grant_type: authorization_code, code, code_verifier,
+  client_id, redirect_uri}` for the same token pair; it then best-effort
+  unregisters the throwaway client (RFC 7592 `DELETE`). It falls back to the
+  device grant when the front door exposes no loopback/DCR endpoints. `spor auth
+  login <url> <token>` / `spor join <url>
+  <token>` is the non-interactive paste path; CI stays `SPOR_TOKEN`. The minted
+  credential is stored per-tenant (§6.2).
 - **Render tickets (shared lens links).** `POST /v1/lens/{id}/ticket` (§3)
   mints a signed, expiring, **read-only** ticket carrying `{lens_id,
   sharer_person_id, exp}` — the credential a *shared* view link carries instead
@@ -476,10 +508,15 @@ spellings are still read — dual-read back-compat window); unset means local
 mode, reading `$SPOR_HOME` directly:
 
 ```
-SPOR_SERVER=https://spor.example.com
+SPOR_SERVER=https://api.sporhq.io      # hosted Spor REST base (the onboarding default)
 SPOR_TOKEN=spor_pat_...                # per-user token (§4)
+SPOR_ORG=acme                         # select a stored tenant by org (§6.2)
 ```
 
+`spor join <token>` writes both for you, defaulting `SPOR_SERVER` to the hosted
+base `https://api.sporhq.io`; pass a URL (`spor join <url> <token>`) to point at
+a self-hosted server instead.
+
 **Opt-in activation.** Spor is opt-in per repo: with the plugin installed, the
 hooks are a full no-op (no context injected, nothing distilled) in any repo that
 has not opted in. A repo is active when its mode is not `off` AND either an
@@ -548,3 +585,41 @@ Contract:
   `nodes/` and brief `history/` are committed. The SessionEnd distiller leaves
   distilled nodes **uncommitted** (for the human PR flow) instead of
   auto-committing when the graph home is the same git repo as the code repo.
+
+### 6.2 Multi-tenant credentials (the credential store + tenant selector)
+
+Server tokens are **org-scoped** (the `org` claim is the routing + isolation
+key), so a person in N orgs holds N credentials. The client is multi-tenant
+(dec-spor-client-cli-mode-tenant-resolution): tokens live in a credential store
+**keyed by `(issuer, org)`** at `$SPOR_HOME/auth/credentials.json` (mode `0600`,
+machine-local — never committed, always in the shared-graph `.gitignore`):
+
+```
+{ "version": 1,
+  "tenants": {
+    "<server>/<org>": { "server": "...", "org": "...", "person": "...",
+                        "email": "...", "access_token": "...",
+                        "refresh_token": "...", "exp": 1234567890 } },
+  "default": "<server>/<org>" }
+```
+
+- **Acquire.** `spor auth login` (device grant, §4) and `spor join <url>
+  <token>` (paste) both **ADD** a tenant — they never overwrite a sibling. The
+  org is read from the token (JWT `org` claim) or `--org`. The first tenant
+  becomes the active default.
+- **Manage.** `spor auth list` (tenants + active + token health, with a **live
+  org-membership refresh** — one `GET /v1/me/org-choices` against the active
+  tenant's issuer surfaces orgs added/removed since the last login, fail-open to
+  the cached listing when the server can't enumerate; task-spor-cli-auth-list-
+  live-membership-requery), `spor auth switch <org>`, `spor auth whoami
+  [--all]`, `spor auth logout [<org>|--all]`.
+- **Tenant selector** (which credential is active), highest wins:
+  `--org`/`--server` flag > `SPOR_SERVER`(+`SPOR_TOKEN`)/`SPOR_ORG` env > repo
+  `.spor` `org:` marker (committable, nearest-ancestor — the remote-mode sibling
+  of the `graph:` binding in §6.1) > store `default` > legacy flat config.json
+  `server`+`token` (migrated on read) > local.
+- **Refresh.** A 401/403 on a tenant carrying a `refresh_token` transparently
+  refreshes against its issuer (`grant_type=refresh_token`) and retries once.
+- **Byte-identical.** With no credential store and only a flat
+  `server`+`token` or `SPOR_*` env set, every resolved value equals the prior
+  single-tenant behavior (norm-cc-byte-identical-refactor).

package/GRAPH.md

@@ -49,6 +49,15 @@ Rules:
 - `summary` is mandatory and must stand alone — most consumers only ever see
   the summary.
 - `date` is YYYY-MM-DD (date of the underlying event, not of node creation).
+  System `created_at`/`updated_at` are NOT stored in node bytes — they are
+  derived from the graph repo's git history into an in-memory `graph.timestamps`
+  index at `loadGraph` (the FIRST commit touching `nodes/<id>.md` is `created_at`,
+  the LAST is `updated_at`), so node files stay byte-identical and git stays the
+  single source of truth (dec-spor-git-derived-timestamps). The index is lazy
+  (off the no-LLM prompt path), HEAD-keyed and cached under `cache/`. An optional
+  explicit frontmatter `created_at`/`updated_at` OVERRIDES the git-derived value
+  (the escape hatch for squash/rebase graphs); `date` is the last-resort fallback
+  when git has nothing — it stays distinct from the system `created_at`.
 - `author` and `authored_via` are optional. The remote server (see API.md
   §1) stamps `author: Name <email>` and `authored_via:
   mcp|rest|capture|gardener` from the authenticated identity on every node
@@ -238,12 +247,23 @@ return values cross back, so `require`, `process`, `eval`, the `Function`
 constructor, host prototypes, ambient time/IO, and unbounded loops are all
 unavailable (a runaway hits a fuel/memory interrupt). A hook that throws does not
 wave the write through — it **rejects** it. Write the functions accordingly: no
-external state, no side effects, decide only from the arguments. Two more
+external state, no side effects, decide only from the arguments. Three more
 attached exports are recognized: `queueSignals(node, ctx)` (a `{ name: number }`
-map blended into the decision-queue ranking) and named upgrade functions
-referenced from `payload.upgrades` (lazy, forward-only field migrations on a
-`schema_version` bump). The **client** half (hooks, the `spor` CLI, `lib/`) only
-*parses and indexes* this code for the registry knobs — it never executes it;
+map blended into the decision-queue ranking); `get(node, ctx)` — the **read-time
+enrichment** hook, run on `get_node`, returning an object whose keys ride along on
+the read. Where `transitions()` is the write-time gate, `get()` is its read-time
+peer: the server hands it a *bounded one-hop neighborhood* (`ctx.neighbors` — this
+node's inbound + outbound edges each with the neighbor's `{id, edge, dir, type,
+status, title, summary, date, superseded}`, capped — plus `ctx.non_resolving_statuses`
+and `ctx.terminal`), and the hook attaches derived context — e.g. an answered
+`question` surfacing WHAT answered it. It is read-only and **fail-soft** (a throw
+drops the enrichment, never breaks the read; the only hook that fails open rather
+than closed); reserved core keys (`id`/`raw`/`frontmatter`/`revision`) can't be
+clobbered. The seed `question`/`issue`/`task`/`incident` schemas carry one, the
+single mechanism that expresses the resolution ride-along. Finally, named upgrade
+functions referenced from `payload.upgrades` (lazy, forward-only field migrations
+on a `schema_version` bump). The **client** half (hooks, the `spor` CLI, `lib/`)
+only *parses and indexes* this code for the registry knobs — it never executes it;
 the server is the sole executor.
 
 Resolution and rollout: a graph-resident schema always beats the seed pack, and

package/QUEUE.md

@@ -118,6 +118,15 @@ export function transitions(node, proposed, graph) { ... }
 export function queueSignals(node, graph, activity) {
   return { blocking: ..., heat: ..., staleness: ..., age_days: ... };
 }
+
+// get(node, ctx) — read-time enrichment, run on get_node; the read-time peer of
+// transitions(). The host hands in a bounded one-hop neighborhood (ctx.neighbors,
+// not a live graph), and the returned object's keys ride along on the read.
+// Read-only, fail-soft. Expresses the resolution ride-along on the seed
+// question/issue/task/incident schemas (task-spor-schema-get-hook-readtime-enrichment).
+export function get(node, ctx) {
+  return { resolution: ... };
+}
 ```
 ```
 
@@ -402,8 +411,30 @@ signals via its schema's `queueSignals()`:
   so provenance hubs can't ride it; capped below the p1 bump so human
   priority stays supreme; and the why-line states the actual window
   ("N writes in the last D days") (dec-cc-queue-front-from-attribution).
+  The continuity loop ("work X → X stays on top") terminates by finishing X
+  (a resolves edge retires it) — EXCEPT a task **held open on an external
+  gate**, which has nothing to resolve, so each held pass re-raises front and
+  re-surfaces it. The **held-task self-limit** breaks that loop
+  (task-spor-queue-front-loop-self-limit-on-held-tasks): an OPEN task carrying
+  an inbound non-resolving outcome (an artifact/decision linked by any edge but
+  resolves/answers) with no live resolving edge and no live blocker has its
+  front damped to 0 in the score and its suggestion flipped `do → triage`
+  ("resolve, gate with blocked-by, set wake, or abandon") — the same posture
+  staleness takes (flip the suggestion, don't boost the score). `signals.front`
+  keeps the raw count so a `queue-policy` rank() can re-weight. The read-time
+  twin is the `schema-task` `get()` hook, which rides a `held` note along on
+  `get_node`.
 - **staleness** — anchors superseded or gone; high staleness suggests
   closing, not doing.
+- **cold_neighbors** — the count of the node's traversable neighbors whose
+  git-derived `updated_at` is newer than its own: a node that went cold while its
+  neighborhood kept moving ("context moved around it"). Fed by the
+  `graph.timestamps` index the caller injects as `timestamps`
+  (task-spor-git-derived-timestamp-index); like `needed_by_days` it rides along
+  ONLY when the index is present and the count is >0, so the queue is
+  byte-identical without it (conformance, the prompt path, a non-git home). It is
+  surfaced (signal + why-line), not yet a score weight — a ranking contribution is
+  a deliberate tuning change deferred to its own task.
 - **age**, and any org-specific signal the schema's code adds (SLA clocks,
   sprint membership, whatever the org's process actually is).
 
@@ -606,7 +637,10 @@ the structural truth:
    §2.4 sandbox in step 4 alongside `transitions()`. The blend shipped
    opinionated (§8): `priority bump + 3·blocking − 3·blocked_by +
    min(log₂(1+front), 5) + log₂(1+heat) + age/30 (capped) + neededBy urgency (0-5)`, with staleness ≥ 0.5 flipping the item's suggestion to
-   "close". The `needed_by: YYYY-MM-DD` deadline term is the inverse of
+   "close" and the held-task self-limit flipping it to "triage" (front damped
+   to 0) for an open task with a recorded non-resolving outcome but no resolver
+   and no blocker (task-spor-queue-front-loop-self-limit-on-held-tasks). The
+   `needed_by: YYYY-MM-DD` deadline term is the inverse of
    `wake`: where `wake` hides a node until its date, `needed_by` keeps it
    visible from creation and ramps its score linearly over a 30-day window to
    3 at the date, then on to a hard cap of 5 once overdue — surfacing

package/README.md

@@ -198,11 +198,21 @@ answered from what's already there, it routes to the person most likely to
 know, and their answer flows back into the graph as a node — so the next
 person who asks gets it from the graph instead.
 
-A client joins a team graph by pointing at it with two environment variables:
+A client joins a team graph with a token from your team's invite:
 
 ```bash
-export SPOR_SERVER=https://spor.example.com
-export SPOR_TOKEN=...
+spor join spor_pat_...                 # hosted Spor (https://api.sporhq.io)
+```
+
+`spor join` writes the server URL and token to your user config and confirms
+the connection. The URL defaults to the hosted Spor service
+(`https://api.sporhq.io`); pass your own to point elsewhere
+(`spor join https://spor.example.com spor_pat_...`). The equivalent two
+environment variables work too:
+
+```bash
+export SPOR_SERVER=https://api.sporhq.io
+export SPOR_TOKEN=spor_pat_...
 ```
 
 Set those and the client talks to the team graph over REST and MCP; leave