specguard-mcp 0.1.13 → 0.1.15

package/README.md

@@ -34,8 +34,8 @@ refuses to boot and takes the tools that needed no configuration down with it.
 | --- | --- | --- | --- |
 | `SPECGUARD_ENDPOINT` | `get_repository_overview`, `list_repositories`, `add_repository`, `registrable_repositories` | — | your SpecGuard instance's root URL, **including the scheme** — e.g. `https://specguard.example.com`, or `http://localhost:3000`. A value with no scheme is refused by name (`SPECGUARD_ENDPOINT is not a usable URL: "sg.example.com"`) rather than surfacing later as an opaque failure. `SPECGUARD_URL` is accepted as an alias, and is the name every message uses when it is the one you set. A blank value counts as unset, so leaving `SPECGUARD_ENDPOINT` empty in a templated config falls through to `SPECGUARD_URL` instead of suppressing it |
 | `SPECGUARD_API_KEY` | `get_repository_overview`, `near_duplicate_clusters` (default calls) | — | an agent/CI API key (`sgk_…`) issued by that deployment — a **per-repository** key, which is the single repository those tools answer about by default |
-| `SPECGUARD_USER_API_KEY` | `list_repositories` (fallback), `add_repository`, `registrable_repositories`, `remove_repository`, `create_repository_api_key`, `revoke_repository_api_key`, `list_repository_agent_keys`, `revoke_repository_agent_key`, `list_repository_agent_keys_presented_revoked`, `list_repository_members`, `add_repository_member`, `update_repository_member_permissions`, `remove_repository_member`, `rename_repository` | — | a **user** API key (`sgu_…`), minted from that deployment's account page. A different credential from the one above, not a second place to put the same value: SpecGuard decides which of them a request may use from the token's prefix, before it reads anything, and answers `401` for the other one. Set whichever your tools need — both, if you use both |
-| `SPECGUARD_AGENT_API_KEY` | `list_repositories` (preferred), `get_repository_overview` / `near_duplicate_clusters` **with** `repository` | — | an **agent** API key (`sga_…`), minted from that deployment's account page (Agent keys panel) with an explicit set of repositories and permissions. It speaks for nobody: its reach is exactly the set granted onto it, fixed at mint time, and every read is bounded by that set server-side. This is the credential to give an automated agent — one key, many repositories, none of a person's rights. When it and `SPECGUARD_USER_API_KEY` are both set, `list_repositories` uses **this** one, so discovery stays inside the set the other tools can reach |
+| `SPECGUARD_USER_API_KEY` | `list_repositories` (fallback), `add_repository`, `registrable_repositories`, `remove_repository` (fallback), `create_repository_api_key`, `revoke_repository_api_key`, `list_repository_agent_keys`, `revoke_repository_agent_key`, `list_repository_agent_keys_presented_revoked`, `list_repository_members`, `add_repository_member`, `update_repository_member_permissions`, `remove_repository_member`, `rename_repository` | — | a **user** API key (`sgu_…`), minted from that deployment's account page. A different credential from the one above, not a second place to put the same value: SpecGuard decides which of them a request may use from the token's prefix, before it reads anything, and answers `401` for the other one. Set whichever your tools need — both, if you use both |
+| `SPECGUARD_AGENT_API_KEY` | `list_repositories` (preferred), `remove_repository` (preferred), `get_repository_overview` / `near_duplicate_clusters` **with** `repository` | — | an **agent** API key (`sga_…`), minted from that deployment's account page (Agent keys panel) with an explicit set of repositories and permissions. It speaks for nobody: its reach is exactly the set granted onto it, fixed at mint time, and every read is bounded by that set server-side. This is the credential to give an automated agent — one key, many repositories, none of a person's rights. When it and `SPECGUARD_USER_API_KEY` are both set, `list_repositories` and `remove_repository` use **this** one, so discovery stays inside the set the other tools can reach |
 | `SPECGUARD_LINT_COMMAND` | `lint_intent_annotations` | `specguard-lint` | the command that runs the linter. Most Ruby projects need `bundle exec specguard-lint` |
 | `SPECGUARD_TIMEOUT_MS` | HTTP tools | `30000` | how long a call to SpecGuard may take |
 
@@ -367,16 +367,35 @@ blank value is no ask: passing an empty string and omitting the argument make th
 | `sort` | `"stale"` — re-order stalest-first: repositories CI has never ingested a run for first, then least-recently-ingested, with `full_name` breaking ties so two calls agree element for element. The same entries, a different order; the default order stays `full_name` ascending |
 
 The body comes back as SpecGuard serves it — `{"repositories": […]}`, each entry carrying `id`,
-`full_name`, `name`, `registered_at` and `role`, ordered by `full_name` ascending unless `sort`
-asks otherwise. The first four are
-deliberately the same four fields, under the same names, that `get_repository_overview` serves in its
-own `repository` block, so a client that reads one reads the other. `role` has one value per
+`full_name`, `name`, `registered_at`, `role`, `delivery_health` and `latest_run`, ordered by
+`full_name` ascending unless `sort` asks otherwise. The identity fields are deliberately the same
+fields, under the same names, that `get_repository_overview` serves in its own `repository` block,
+so a client that reads one reads the other.
+
+`delivery_health` is the entry's delivery verdict — `refusing` beside `last_rejection_at` — served
+on **every** entry, so this one call triages ingest-pipeline health across the whole reachable set
+instead of paying one `get_repository_overview` call per repository. It is the coarse sibling of
+the overview's fuller per-repository block. A quiet verdict is a finding, not a gap:
+`refusing: false` means nothing was refused, never that delivery is untracked.
+
+`latest_run` is the entry's newest run — when CI last reported, on what branch and commit, how big
+the suite is, how much of it SpecGuard can read, and the run-level cost scalars. `null` means CI
+has **never reported** for that repository — never a run that found an empty suite.
+
+`role` has one value per
 credential kind: under a **user** key (`sgu_…`) it is `owner` or `member` — the list mixes
 repositories this person owns with repositories somebody shared with them, and nothing else tells
 them apart — while under an **agent** key (`sga_…`) every entry is `agent`, the value that says the
 ownership question does not apply because the key speaks for nobody (branching on owner/member
-correctly reads false for both). Read it before assuming a repository is one you may administer. An
-empty list means no access, not an error.
+correctly reads false for both). Read it before assuming a repository is one you may administer.
+
+Under an **agent** key the top level also carries `credential.capabilities` — the calling key's own
+grant, read through the server's policy, so an agent key learns what it was granted here instead of
+discovering its permissions by hitting refusals; under a **user** key the block is absent, not
+`null` — a person key has no mint-time permission set, and a null would assert one exists and is
+empty.
+
+An empty list means no access, not an error.
 
 **It reads a different key from `get_repository_overview` — either of two, whichever is set.**
 `SPECGUARD_AGENT_API_KEY` (`sga_…`) when it is set: the answer is then the repository set granted
@@ -543,9 +562,13 @@ Authorization is the `repo.delete` capability at **either surface** — an owner
 `repo.delete`, may remove the repository. A member without it is refused `403` with SpecGuard's own
 sentence, verbatim. The repository's CI keys stop authenticating the moment it succeeds.
 
-It reads `SPECGUARD_USER_API_KEY` (`sgu_…`) — the same **person** key `add_repository` reads, and
-a different one from the `sgk_…` key `get_repository_overview` uses; `list_repositories` also
-accepts that key but does not require it (its agent key wins when both are set).
+It reads either of two credentials, whichever is set — and a different one from the `sgk_…` key
+`get_repository_overview` uses. `SPECGUARD_AGENT_API_KEY` (`sga_…`) when it is set: the call then
+reaches only the repositories granted onto that key at mint time, and only where the grant carries
+`repo.delete` — a repository outside that set is answered `404` in SpecGuard's own words.
+`SPECGUARD_USER_API_KEY` (`sgu_…`) when no agent key is set: the same **person** key `add_repository`
+reads. With both set the **agent** key wins, so the removal answers inside the same set
+`list_repositories` reports.
 
 ### `create_repository_api_key`
 

package/dist/src/tools/index.d.ts

@@ -20,7 +20,7 @@ import type { ToolDefinition } from "./types.js";
  * the two halves of the surface — one local subprocess, one authenticated HTTP
  * call — so the shape is proven on both kinds of capability rather than on one.
  *
- * == The third: the first tool that reads the OTHER credential
+ * == The first tool that reads the OTHER credential
  *
  *   - `list_repositories` wraps `GET /api/v1/repositories` (shipped:
  *     `specguard/config/routes.rb`, `Api::V1::UserRepositoriesController`).
@@ -43,15 +43,7 @@ import type { ToolDefinition } from "./types.js";
  * not offering the tool, because the agent has already committed to a plan by
  * the time it finds out.
  *
- * Duplicate clustering was once under this same forbid, on the same standing
- * rule — no tool may wrap what has not shipped. That half retired when the
- * platform moved: SPGD-703 (`specguard` `c43dc19`, 2026-08-28) shipped
- * `GET /api/v1/repository?near_duplicates=`, serving
- * `RepositoryOverview#serialized_near_duplicates` behind an opt-in ask, and
- * `near_duplicate_clusters` below wraps it. What moved was the platform, not
- * the bar.
- *
- * == The fourth: the first tool that WRITES
+ * == The first tool that WRITES
  *
  *   - `add_repository` wraps `POST /api/v1/repositories` (shipped:
  *     `specguard/config/routes.rb`, `Api::V1::UserRepositoriesController#create`).
@@ -69,10 +61,10 @@ import type { ToolDefinition } from "./types.js";
  * The standing rule is unchanged and still binding. What once kept `DELETE
  * /api/v1/repositories/:id` and the API-key endpoints out under it — "not on
  * `origin/main`, so they may not be wrapped" — stopped being true when SPGD-754
- * shipped them, and the sixth-through-eighth section below records their
+ * shipped them, and the removal-and-key-lifecycle section below records their
  * wrapping. What moved was the platform, not the bar.
  *
- * == The fifth: the read half of the registration gate
+ * == The read half of the registration gate
  *
  *   - `registrable_repositories` wraps `GET /api/v1/repositories/registrable`
  *     (shipped: `specguard/config/routes.rb:117`,
@@ -86,14 +78,14 @@ import type { ToolDefinition } from "./types.js";
  * carrying the same `{error, message}` contract — the identical defect, given
  * the identical remedy.
  *
- * The user-scoped surface as it now stands is therefore three tools: read the
- * list, read the gate's answer, write a registration. The standing rule is
- * unchanged and still binding, which is what keeps the rest out:
- * `DELETE /api/v1/repositories/:id` and the API-key endpoints (SPGD-754) are
- * NOT on `origin/main`, so they may not be wrapped here however useful a tool
- * for them would be. What moved was the platform, not the bar.
+ * The registration gate was the newest user-scoped entry when it landed; the
+ * sections below record how the surface grew after it. The standing rule is
+ * unchanged and still binding, and what it keeps out today is what has not
+ * shipped — `/check-intent` has no backing endpoint (`routes.rb` mounts it as
+ * a comment only), so it stays unwrapped. What moved was the platform, not
+ * the bar.
  *
- * == The sixth through eighth: removal and the key lifecycle
+ * == Removal and the key lifecycle
  *
  *   - `remove_repository` wraps `DELETE /api/v1/repositories/:id`, and
  *     `create_repository_api_key` / `revoke_repository_api_key` wrap the two
@@ -113,7 +105,18 @@ import type { ToolDefinition } from "./types.js";
  * as a comment only). A tool advertised in `tools/list` remains a promise an
  * agent will act on.
  *
- * == The ninth through twelfth: member management
+ * == Near-duplicate clusters: the forbid that retired
+ *
+ *   - `near_duplicate_clusters` wraps `GET /api/v1/repository?near_duplicates=`
+ *     (shipped: SPGD-703, `specguard` `c43dc19`, 2026-08-28), serving
+ *     `RepositoryOverview#serialized_near_duplicates` behind an opt-in ask.
+ *
+ * Duplicate clustering was once under the same forbid that still keeps
+ * `/check-intent` out — the standing rule: no tool may wrap what has not
+ * shipped. That half retired when the platform moved and this entry became
+ * wrappable. What moved was the platform, not the bar.
+ *
+ * == Member management
  *
  *   - `list_repository_members`, `add_repository_member`,
  *     `update_repository_member_permissions` and `remove_repository_member`
@@ -132,7 +135,7 @@ import type { ToolDefinition } from "./types.js";
  * stays scoped to the repository (a foreign id is refused 404), and there is
  * no name-based lookup.
  *
- * == The thirteenth: rename
+ * == Rename
  *
  *   - `rename_repository` wraps `PATCH /api/v1/repositories/:id` (shipped:
  *     SPGD-878, `specguard@origin/main` e026793, PR #266).
@@ -148,7 +151,7 @@ import type { ToolDefinition } from "./types.js";
  * remove-and-re-register, which destroys every key, run and intent; this one
  * keeps them.
  *
- * == The fourteenth through sixteenth: the agent-key family
+ * == The agent-key family
  *
  *   - `list_repository_agent_keys` and `revoke_repository_agent_key` wrap the
  *     inventory and revoke of `user_repository_agent_keys` (shipped: SPGD-1004,

package/dist/src/tools/index.js

@@ -36,7 +36,7 @@ import updateRepositoryMemberPermissions from "./update-repository-member-permis
  * the two halves of the surface — one local subprocess, one authenticated HTTP
  * call — so the shape is proven on both kinds of capability rather than on one.
  *
- * == The third: the first tool that reads the OTHER credential
+ * == The first tool that reads the OTHER credential
  *
  *   - `list_repositories` wraps `GET /api/v1/repositories` (shipped:
  *     `specguard/config/routes.rb`, `Api::V1::UserRepositoriesController`).
@@ -59,15 +59,7 @@ import updateRepositoryMemberPermissions from "./update-repository-member-permis
  * not offering the tool, because the agent has already committed to a plan by
  * the time it finds out.
  *
- * Duplicate clustering was once under this same forbid, on the same standing
- * rule — no tool may wrap what has not shipped. That half retired when the
- * platform moved: SPGD-703 (`specguard` `c43dc19`, 2026-08-28) shipped
- * `GET /api/v1/repository?near_duplicates=`, serving
- * `RepositoryOverview#serialized_near_duplicates` behind an opt-in ask, and
- * `near_duplicate_clusters` below wraps it. What moved was the platform, not
- * the bar.
- *
- * == The fourth: the first tool that WRITES
+ * == The first tool that WRITES
  *
  *   - `add_repository` wraps `POST /api/v1/repositories` (shipped:
  *     `specguard/config/routes.rb`, `Api::V1::UserRepositoriesController#create`).
@@ -85,10 +77,10 @@ import updateRepositoryMemberPermissions from "./update-repository-member-permis
  * The standing rule is unchanged and still binding. What once kept `DELETE
  * /api/v1/repositories/:id` and the API-key endpoints out under it — "not on
  * `origin/main`, so they may not be wrapped" — stopped being true when SPGD-754
- * shipped them, and the sixth-through-eighth section below records their
+ * shipped them, and the removal-and-key-lifecycle section below records their
  * wrapping. What moved was the platform, not the bar.
  *
- * == The fifth: the read half of the registration gate
+ * == The read half of the registration gate
  *
  *   - `registrable_repositories` wraps `GET /api/v1/repositories/registrable`
  *     (shipped: `specguard/config/routes.rb:117`,
@@ -102,14 +94,14 @@ import updateRepositoryMemberPermissions from "./update-repository-member-permis
  * carrying the same `{error, message}` contract — the identical defect, given
  * the identical remedy.
  *
- * The user-scoped surface as it now stands is therefore three tools: read the
- * list, read the gate's answer, write a registration. The standing rule is
- * unchanged and still binding, which is what keeps the rest out:
- * `DELETE /api/v1/repositories/:id` and the API-key endpoints (SPGD-754) are
- * NOT on `origin/main`, so they may not be wrapped here however useful a tool
- * for them would be. What moved was the platform, not the bar.
+ * The registration gate was the newest user-scoped entry when it landed; the
+ * sections below record how the surface grew after it. The standing rule is
+ * unchanged and still binding, and what it keeps out today is what has not
+ * shipped — `/check-intent` has no backing endpoint (`routes.rb` mounts it as
+ * a comment only), so it stays unwrapped. What moved was the platform, not
+ * the bar.
  *
- * == The sixth through eighth: removal and the key lifecycle
+ * == Removal and the key lifecycle
  *
  *   - `remove_repository` wraps `DELETE /api/v1/repositories/:id`, and
  *     `create_repository_api_key` / `revoke_repository_api_key` wrap the two
@@ -129,7 +121,18 @@ import updateRepositoryMemberPermissions from "./update-repository-member-permis
  * as a comment only). A tool advertised in `tools/list` remains a promise an
  * agent will act on.
  *
- * == The ninth through twelfth: member management
+ * == Near-duplicate clusters: the forbid that retired
+ *
+ *   - `near_duplicate_clusters` wraps `GET /api/v1/repository?near_duplicates=`
+ *     (shipped: SPGD-703, `specguard` `c43dc19`, 2026-08-28), serving
+ *     `RepositoryOverview#serialized_near_duplicates` behind an opt-in ask.
+ *
+ * Duplicate clustering was once under the same forbid that still keeps
+ * `/check-intent` out — the standing rule: no tool may wrap what has not
+ * shipped. That half retired when the platform moved and this entry became
+ * wrappable. What moved was the platform, not the bar.
+ *
+ * == Member management
  *
  *   - `list_repository_members`, `add_repository_member`,
  *     `update_repository_member_permissions` and `remove_repository_member`
@@ -148,7 +151,7 @@ import updateRepositoryMemberPermissions from "./update-repository-member-permis
  * stays scoped to the repository (a foreign id is refused 404), and there is
  * no name-based lookup.
  *
- * == The thirteenth: rename
+ * == Rename
  *
  *   - `rename_repository` wraps `PATCH /api/v1/repositories/:id` (shipped:
  *     SPGD-878, `specguard@origin/main` e026793, PR #266).
@@ -164,7 +167,7 @@ import updateRepositoryMemberPermissions from "./update-repository-member-permis
  * remove-and-re-register, which destroys every key, run and intent; this one
  * keeps them.
  *
- * == The fourteenth through sixteenth: the agent-key family
+ * == The agent-key family
  *
  *   - `list_repository_agent_keys` and `revoke_repository_agent_key` wrap the
  *     inventory and revoke of `user_repository_agent_keys` (shipped: SPGD-1004,

package/dist/src/tools/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/tools/index.ts"],"names":[],"mappings":"AAAA,OAAO,aAAa,MAAM,qBAAqB,CAAC;AAChD,OAAO,mBAAmB,MAAM,4BAA4B,CAAC;AAC7D,OAAO,sBAAsB,MAAM,gCAAgC,CAAC;AACpE,OAAO,qBAAqB,MAAM,8BAA8B,CAAC;AACjE,OAAO,gBAAgB,MAAM,wBAAwB,CAAC;AACtD,OAAO,uBAAuB,MAAM,iCAAiC,CAAC;AACtE,OAAO,uCAAuC,MAAM,mDAAmD,CAAC;AACxG,OAAO,qBAAqB,MAAM,8BAA8B,CAAC;AACjE,OAAO,qBAAqB,MAAM,8BAA8B,CAAC;AACjE,OAAO,qBAAqB,MAAM,0BAA0B,CAAC;AAC7D,OAAO,uBAAuB,MAAM,+BAA+B,CAAC;AACpE,OAAO,gBAAgB,MAAM,wBAAwB,CAAC;AACtD,OAAO,sBAAsB,MAAM,+BAA+B,CAAC;AACnE,OAAO,gBAAgB,MAAM,wBAAwB,CAAC;AACtD,OAAO,wBAAwB,MAAM,kCAAkC,CAAC;AACxE,OAAO,sBAAsB,MAAM,gCAAgC,CAAC;AACpE,OAAO,iCAAiC,MAAM,2CAA2C,CAAC;AAG1F;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4KG;AACH,MAAM,CAAC,MAAM,KAAK,GAA8B;IAC9C,qBAAqB;IACrB,qBAAqB;IACrB,gBAAgB;IAChB,aAAa;IACb,uBAAuB;IACvB,gBAAgB;IAChB,sBAAsB;IACtB,sBAAsB;IACtB,qBAAqB;IACrB,qBAAqB;IACrB,mBAAmB;IACnB,iCAAiC;IACjC,sBAAsB;IACtB,gBAAgB;IAChB,uBAAuB;IACvB,uCAAuC;IACvC,wBAAwB;CACzB,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/tools/index.ts"],"names":[],"mappings":"AAAA,OAAO,aAAa,MAAM,qBAAqB,CAAC;AAChD,OAAO,mBAAmB,MAAM,4BAA4B,CAAC;AAC7D,OAAO,sBAAsB,MAAM,gCAAgC,CAAC;AACpE,OAAO,qBAAqB,MAAM,8BAA8B,CAAC;AACjE,OAAO,gBAAgB,MAAM,wBAAwB,CAAC;AACtD,OAAO,uBAAuB,MAAM,iCAAiC,CAAC;AACtE,OAAO,uCAAuC,MAAM,mDAAmD,CAAC;AACxG,OAAO,qBAAqB,MAAM,8BAA8B,CAAC;AACjE,OAAO,qBAAqB,MAAM,8BAA8B,CAAC;AACjE,OAAO,qBAAqB,MAAM,0BAA0B,CAAC;AAC7D,OAAO,uBAAuB,MAAM,+BAA+B,CAAC;AACpE,OAAO,gBAAgB,MAAM,wBAAwB,CAAC;AACtD,OAAO,sBAAsB,MAAM,+BAA+B,CAAC;AACnE,OAAO,gBAAgB,MAAM,wBAAwB,CAAC;AACtD,OAAO,wBAAwB,MAAM,kCAAkC,CAAC;AACxE,OAAO,sBAAsB,MAAM,gCAAgC,CAAC;AACpE,OAAO,iCAAiC,MAAM,2CAA2C,CAAC;AAG1F;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+KG;AACH,MAAM,CAAC,MAAM,KAAK,GAA8B;IAC9C,qBAAqB;IACrB,qBAAqB;IACrB,gBAAgB;IAChB,aAAa;IACb,uBAAuB;IACvB,gBAAgB;IAChB,sBAAsB;IACtB,sBAAsB;IACtB,qBAAqB;IACrB,qBAAqB;IACrB,mBAAmB;IACnB,iCAAiC;IACjC,sBAAsB;IACtB,gBAAgB;IAChB,uBAAuB;IACvB,uCAAuC;IACvC,wBAAwB;CACzB,CAAC"}

package/dist/src/tools/list-repositories.d.ts

@@ -92,11 +92,51 @@ import type { ToolDefinition } from "./types.js";
  *
  * Same rule as every other tool here (`types.ts`: "A thin client that reshapes
  * its upstream is not thin"), and it has real content on this body. The
- * controller serves each entry as `id`, `full_name`, `name`, `registered_at`
- * and `role`, and says why: the first four are DELIBERATELY the same four
- * fields, under the same names, that `GET /api/v1/repository` serves in its own
- * `repository` block, so a client that has read one knows how to read the other.
- * Renaming or flattening anything here would spend that parity on the last hop.
+ * controller serves each entry as `id`, `full_name`, `name`, `registered_at`,
+ * `role`, `delivery_health` and `latest_run`
+ * (`Api::V1::UserRepositoriesController#serialize`), and it says why about the
+ * identity fields: `id`, `full_name`, `name` and `registered_at` are
+ * DELIBERATELY the same fields, under the same names, that
+ * `GET /api/v1/repository` serves in its own `repository` block, so a client
+ * that has read one knows how to read the other. Renaming or flattening
+ * anything here would spend that parity on the last hop. The rest of each
+ * entry — and the block beside `repositories:` at the top level — is payload an
+ * agent must know ARRIVES: a description that omits it sends the agent to pay
+ * per-repository calls for data this one call already handed it (SPGD-1067).
+ *
+ * `delivery_health` rides EVERY entry (`#delivery_verdicts`): `{refusing,
+ * last_rejection_at}` — the staleness verdict `get_repository_overview` serves
+ * in its fuller per-repository block, spelled here as the one-call fleet
+ * triage. "Which of my repositories has a refusing ingest pipeline?" is
+ * answerable from THIS call alone, never one overview call per repository. A
+ * quiet verdict is a finding, not a gap, on the same rule the overview's
+ * description states: `refusing: false` is "nothing was refused", not
+ * "delivery is untracked".
+ *
+ * `latest_run` is the entry's newest run at the serializer's LIST depth
+ * (`LatestRunSerializer::LIST_DEPTH`): when CI last reported, on what branch
+ * and commit, how big the suite is, how much of it SpecGuard can read, and the
+ * run-level cost scalars — the drill-ins stay on the overview's full depth.
+ * `null` means CI has NEVER reported for that repository, and on this list the
+ * key is PRESENT-and-null (`#index` always passes the block;
+ * `LatestRunSerializer#body` returns nil for a nil run), the serializer's
+ * "nil, not a zeroed block" rule — a repository CI has never run must not read
+ * byte-identically to one that ran and found an empty suite. The ABSENT-key arm
+ * of that same marker belongs to `#update`'s rename receipt, not to this list.
+ *
+ * `credential` is the block that is NOT repository-scoped: under an `sga_` key
+ * the TOP level carries `credential: {capabilities}` — the calling key's own
+ * grant (SPGD-977), with every capability in `RepositoryPolicy::CAPABILITIES`
+ * ASKED of `AgentApiKeyPolicy` server-side, so the booleans cannot disagree
+ * with a 403 the same key would get (an empty permission set thereby reads
+ * affirmatively — `view` true, every further verb false, the machine
+ * counterpart of the account page's "read only" — rather than a copy of the
+ * stored permissions array, which under-states and over-states the grant at
+ * once). Its only other carrier is the minting person's browser account page,
+ * so before it a machine credential's only discovery path for its own
+ * permissions was 403 trial-and-error. Under an `sgu_` key the block is ABSENT
+ * rather than nulled — a person key has no mint-time permission set, and a null
+ * would assert one exists and is empty.
  *
  * `role` is the field this surface adds, and its value depends on WHICH
  * credential answered — three values, one per credential kind, and all three

package/dist/src/tools/list-repositories.js

@@ -93,11 +93,51 @@ import { optionalString } from "./args.js";
  *
  * Same rule as every other tool here (`types.ts`: "A thin client that reshapes
  * its upstream is not thin"), and it has real content on this body. The
- * controller serves each entry as `id`, `full_name`, `name`, `registered_at`
- * and `role`, and says why: the first four are DELIBERATELY the same four
- * fields, under the same names, that `GET /api/v1/repository` serves in its own
- * `repository` block, so a client that has read one knows how to read the other.
- * Renaming or flattening anything here would spend that parity on the last hop.
+ * controller serves each entry as `id`, `full_name`, `name`, `registered_at`,
+ * `role`, `delivery_health` and `latest_run`
+ * (`Api::V1::UserRepositoriesController#serialize`), and it says why about the
+ * identity fields: `id`, `full_name`, `name` and `registered_at` are
+ * DELIBERATELY the same fields, under the same names, that
+ * `GET /api/v1/repository` serves in its own `repository` block, so a client
+ * that has read one knows how to read the other. Renaming or flattening
+ * anything here would spend that parity on the last hop. The rest of each
+ * entry — and the block beside `repositories:` at the top level — is payload an
+ * agent must know ARRIVES: a description that omits it sends the agent to pay
+ * per-repository calls for data this one call already handed it (SPGD-1067).
+ *
+ * `delivery_health` rides EVERY entry (`#delivery_verdicts`): `{refusing,
+ * last_rejection_at}` — the staleness verdict `get_repository_overview` serves
+ * in its fuller per-repository block, spelled here as the one-call fleet
+ * triage. "Which of my repositories has a refusing ingest pipeline?" is
+ * answerable from THIS call alone, never one overview call per repository. A
+ * quiet verdict is a finding, not a gap, on the same rule the overview's
+ * description states: `refusing: false` is "nothing was refused", not
+ * "delivery is untracked".
+ *
+ * `latest_run` is the entry's newest run at the serializer's LIST depth
+ * (`LatestRunSerializer::LIST_DEPTH`): when CI last reported, on what branch
+ * and commit, how big the suite is, how much of it SpecGuard can read, and the
+ * run-level cost scalars — the drill-ins stay on the overview's full depth.
+ * `null` means CI has NEVER reported for that repository, and on this list the
+ * key is PRESENT-and-null (`#index` always passes the block;
+ * `LatestRunSerializer#body` returns nil for a nil run), the serializer's
+ * "nil, not a zeroed block" rule — a repository CI has never run must not read
+ * byte-identically to one that ran and found an empty suite. The ABSENT-key arm
+ * of that same marker belongs to `#update`'s rename receipt, not to this list.
+ *
+ * `credential` is the block that is NOT repository-scoped: under an `sga_` key
+ * the TOP level carries `credential: {capabilities}` — the calling key's own
+ * grant (SPGD-977), with every capability in `RepositoryPolicy::CAPABILITIES`
+ * ASKED of `AgentApiKeyPolicy` server-side, so the booleans cannot disagree
+ * with a 403 the same key would get (an empty permission set thereby reads
+ * affirmatively — `view` true, every further verb false, the machine
+ * counterpart of the account page's "read only" — rather than a copy of the
+ * stored permissions array, which under-states and over-states the grant at
+ * once). Its only other carrier is the minting person's browser account page,
+ * so before it a machine credential's only discovery path for its own
+ * permissions was 403 trial-and-error. Under an `sgu_` key the block is ABSENT
+ * rather than nulled — a person key has no mint-time permission set, and a null
+ * would assert one exists and is empty.
  *
  * `role` is the field this surface adds, and its value depends on WHICH
  * credential answered — three values, one per credential kind, and all three
@@ -130,13 +170,27 @@ const listRepositories = {
         "ask about\", which no other tool here can give, because every other tool is already scoped " +
         "to one repository by its key. " +
         "Each entry carries `id`, `full_name` (`org/repo`, and the handle every other surface names " +
-        "a repository by), `name`, `registered_at` and `role`. " +
+        "a repository by), `name`, `registered_at`, `role`, `delivery_health` and `latest_run`. " +
+        "`delivery_health` is the entry's delivery verdict — `refusing` beside `last_rejection_at` — " +
+        "served on every entry, so this one call triages ingest-pipeline health across the whole " +
+        "reachable set (the coarse sibling of get_repository_overview's fuller per-repository block) " +
+        "instead of paying one overview call per repository. A quiet verdict is a finding, not a " +
+        "gap: `refusing: false` means nothing was refused, never that delivery is untracked. " +
+        "`latest_run` is the entry's newest run — when CI last reported, on what branch and commit, " +
+        "how big the suite is, how much of it SpecGuard can read, and the run-level cost scalars; " +
+        "`null` means CI has never reported for that repository, never a run that found an empty " +
+        "suite. " +
         "`role` has one value per credential kind. Under a PERSON key (`sgu_…`) it is `owner` or " +
         "`member`: the list mixes repositories this person owns with repositories somebody shared " +
         "with them, and nothing else distinguishes the two. Under an AGENT key (`sga_…`) every " +
         "entry is `agent` — the value that says the ownership question does not apply because the " +
         "key speaks for nobody; branching on owner/member correctly reads false for both. Read it " +
         "before assuming a repository is yours to administer. " +
+        "Under an AGENT key the top level also carries `credential.capabilities` — the calling " +
+        "key's own grant, read through the server's policy, so an agent key sees what it was " +
+        "granted here instead of discovering its permissions by hitting refusals; under a PERSON " +
+        "key the block is ABSENT, not `null`, because a person key has no mint-time permission " +
+        "set. " +
         "Three optional asks narrow WITHIN that set — none of them can widen it — all optional, " +
         "composable on one call: `q` (case-insensitive substring on `full_name`), " +
         "`role: \"owned\"` or `\"shared\"` (one half of the owned/shared mix — note the ask is " +

package/dist/src/tools/list-repositories.js.map

@@ -1 +1 @@
-{"version":3,"file":"list-repositories.js","sourceRoot":"","sources":["../../../src/tools/list-repositories.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,2BAA2B,EAAE,MAAM,6BAA6B,CAAC;AACzF,OAAO,EAAE,cAAc,EAAE,MAAM,WAAW,CAAC;AAG3C;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0HG;AACH,MAAM,gBAAgB,GAAmB;IACvC,IAAI,EAAE,mBAAmB;IACzB,KAAK,EAAE,mBAAmB;IAC1B,WAAW,EACT,2FAA2F;QAC3F,6FAA6F;QAC7F,gCAAgC;QAChC,6FAA6F;QAC7F,wDAAwD;QACxD,0FAA0F;QAC1F,2FAA2F;QAC3F,wFAAwF;QACxF,2FAA2F;QAC3F,2FAA2F;QAC3F,uDAAuD;QACvD,yFAAyF;QACzF,2EAA2E;QAC3E,wFAAwF;QACxF,0FAA0F;QAC1F,wFAAwF;QACxF,kCAAkC;QAClC,mFAAmF;QACnF,wEAAwE;QACxE,yFAAyF;QACzF,cAAc;QACd,4FAA4F;QAC5F,0FAA0F;QAC1F,SAAS;QACT,0FAA0F;QAC1F,6FAA6F;QAC7F,6FAA6F;QAC7F,8FAA8F;QAC9F,2FAA2F;QAC3F,4BAA4B;QAC5B,wEAAwE;QACxE,6EAA6E;IAC/E,WAAW,EAAE;QACX,IAAI,EAAE,QAAQ;QACd,UAAU,EAAE;YACV,CAAC,EAAE;gBACD,IAAI,EAAE,QAAQ;gBACd,WAAW,EACT,iFAAiF;oBACjF,gFAAgF;oBAChF,sFAAsF;oBACtF,oFAAoF;oBACpF,8CAA8C;oBAC9C,uFAAuF;oBACvF,mFAAmF;oBACnF,oFAAoF;oBACpF,gBAAgB;oBAChB,gFAAgF;oBAChF,WAAW;aACd;YACD,IAAI,EAAE;gBACJ,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,OAAO,EAAE,QAAQ,CAAC;gBACzB,WAAW,EACT,mFAAmF;oBACnF,iFAAiF;oBACjF,uFAAuF;oBACvF,iFAAiF;oBACjF,uEAAuE;oBACvE,uFAAuF;oBACvF,yFAAyF;oBACzF,wEAAwE;oBACxE,oFAAoF;oBACpF,mFAAmF;oBACnF,sFAAsF;oBACtF,oFAAoF;oBACpF,oFAAoF;oBACpF,iCAAiC;oBACjC,qEAAqE;aACxE;YACD,IAAI,EAAE;gBACJ,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,OAAO,CAAC;gBACf,WAAW,EACT,qFAAqF;oBACrF,mFAAmF;oBACnF,gFAAgF;oBAChF,sFAAsF;oBACtF,sFAAsF;oBACtF,eAAe;oBACf,iFAAiF;oBACjF,sFAAsF;oBACtF,iFAAiF;oBACjF,YAAY;oBACZ,uFAAuF;oBACvF,uFAAuF;oBACvF,WAAW;aACd;SACF;QACD,6EAA6E;QAC7E,2EAA2E;QAC3E,sEAAsE;QACtE,yEAAyE;QACzE,wEAAwE;QACxE,2EAA2E;QAC3E,2EAA2E;QAC3E,gCAAgC;QAChC,oBAAoB,EAAE,KAAK;KAC5B;IAED,KAAK,CAAC,GAAG,CAAC,IAAI,EAAE,OAAO;QACrB,MAAM,CAAC,GAAG,cAAc,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,GAAG,CAAC,CAAC;QACzC,MAAM,IAAI,GAAG,cAAc,CAAC,IAAI,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC,CAAC;QAClD,MAAM,IAAI,GAAG,cAAc,CAAC,IAAI,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC,CAAC;QAClD,2EAA2E;QAC3E,mEAAmE;QACnE,uEAAuE;QACvE,MAAM,GAAG,GAAG,2BAA2B,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QAExD,mEAAmE;QACnE,4EAA4E;QAC5E,0EAA0E;QAC1E,4EAA4E;QAC5E,wEAAwE;QACxE,2BAA2B;QAC3B,MAAM,OAAO,GAAG,MAAM,aAAa,CACjC,GAAG,EACH,sBAAsB,EACtB,EAAE,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,EACjB,OAAO,CAAC,KAAK,CACd,CAAC;QAEF,OAAO;YACL,IAAI,EAAE,IAAI,CAAC,SAAS,CAAC,OAAO,EAAE,IAAI,EAAE,CAAC,CAAC;YACtC,UAAU,EAAE,OAAO;SACpB,CAAC;IACJ,CAAC;CACF,CAAC;AAEF,eAAe,gBAAgB,CAAC"}
+{"version":3,"file":"list-repositories.js","sourceRoot":"","sources":["../../../src/tools/list-repositories.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,2BAA2B,EAAE,MAAM,6BAA6B,CAAC;AACzF,OAAO,EAAE,cAAc,EAAE,MAAM,WAAW,CAAC;AAG3C;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkKG;AACH,MAAM,gBAAgB,GAAmB;IACvC,IAAI,EAAE,mBAAmB;IACzB,KAAK,EAAE,mBAAmB;IAC1B,WAAW,EACT,2FAA2F;QAC3F,6FAA6F;QAC7F,gCAAgC;QAChC,6FAA6F;QAC7F,yFAAyF;QACzF,8FAA8F;QAC9F,0FAA0F;QAC1F,8FAA8F;QAC9F,0FAA0F;QAC1F,sFAAsF;QACtF,6FAA6F;QAC7F,2FAA2F;QAC3F,0FAA0F;QAC1F,SAAS;QACT,0FAA0F;QAC1F,2FAA2F;QAC3F,wFAAwF;QACxF,2FAA2F;QAC3F,2FAA2F;QAC3F,uDAAuD;QACvD,wFAAwF;QACxF,sFAAsF;QACtF,0FAA0F;QAC1F,wFAAwF;QACxF,OAAO;QACP,yFAAyF;QACzF,2EAA2E;QAC3E,wFAAwF;QACxF,0FAA0F;QAC1F,wFAAwF;QACxF,kCAAkC;QAClC,mFAAmF;QACnF,wEAAwE;QACxE,yFAAyF;QACzF,cAAc;QACd,4FAA4F;QAC5F,0FAA0F;QAC1F,SAAS;QACT,0FAA0F;QAC1F,6FAA6F;QAC7F,6FAA6F;QAC7F,8FAA8F;QAC9F,2FAA2F;QAC3F,4BAA4B;QAC5B,wEAAwE;QACxE,6EAA6E;IAC/E,WAAW,EAAE;QACX,IAAI,EAAE,QAAQ;QACd,UAAU,EAAE;YACV,CAAC,EAAE;gBACD,IAAI,EAAE,QAAQ;gBACd,WAAW,EACT,iFAAiF;oBACjF,gFAAgF;oBAChF,sFAAsF;oBACtF,oFAAoF;oBACpF,8CAA8C;oBAC9C,uFAAuF;oBACvF,mFAAmF;oBACnF,oFAAoF;oBACpF,gBAAgB;oBAChB,gFAAgF;oBAChF,WAAW;aACd;YACD,IAAI,EAAE;gBACJ,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,OAAO,EAAE,QAAQ,CAAC;gBACzB,WAAW,EACT,mFAAmF;oBACnF,iFAAiF;oBACjF,uFAAuF;oBACvF,iFAAiF;oBACjF,uEAAuE;oBACvE,uFAAuF;oBACvF,yFAAyF;oBACzF,wEAAwE;oBACxE,oFAAoF;oBACpF,mFAAmF;oBACnF,sFAAsF;oBACtF,oFAAoF;oBACpF,oFAAoF;oBACpF,iCAAiC;oBACjC,qEAAqE;aACxE;YACD,IAAI,EAAE;gBACJ,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,CAAC,OAAO,CAAC;gBACf,WAAW,EACT,qFAAqF;oBACrF,mFAAmF;oBACnF,gFAAgF;oBAChF,sFAAsF;oBACtF,sFAAsF;oBACtF,eAAe;oBACf,iFAAiF;oBACjF,sFAAsF;oBACtF,iFAAiF;oBACjF,YAAY;oBACZ,uFAAuF;oBACvF,uFAAuF;oBACvF,WAAW;aACd;SACF;QACD,6EAA6E;QAC7E,2EAA2E;QAC3E,sEAAsE;QACtE,yEAAyE;QACzE,wEAAwE;QACxE,2EAA2E;QAC3E,2EAA2E;QAC3E,gCAAgC;QAChC,oBAAoB,EAAE,KAAK;KAC5B;IAED,KAAK,CAAC,GAAG,CAAC,IAAI,EAAE,OAAO;QACrB,MAAM,CAAC,GAAG,cAAc,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,GAAG,CAAC,CAAC;QACzC,MAAM,IAAI,GAAG,cAAc,CAAC,IAAI,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC,CAAC;QAClD,MAAM,IAAI,GAAG,cAAc,CAAC,IAAI,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC,CAAC;QAClD,2EAA2E;QAC3E,mEAAmE;QACnE,uEAAuE;QACvE,MAAM,GAAG,GAAG,2BAA2B,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QAExD,mEAAmE;QACnE,4EAA4E;QAC5E,0EAA0E;QAC1E,4EAA4E;QAC5E,wEAAwE;QACxE,2BAA2B;QAC3B,MAAM,OAAO,GAAG,MAAM,aAAa,CACjC,GAAG,EACH,sBAAsB,EACtB,EAAE,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,EACjB,OAAO,CAAC,KAAK,CACd,CAAC;QAEF,OAAO;YACL,IAAI,EAAE,IAAI,CAAC,SAAS,CAAC,OAAO,EAAE,IAAI,EAAE,CAAC,CAAC;YACtC,UAAU,EAAE,OAAO;SACpB,CAAC;IACJ,CAAC;CACF,CAAC;AAEF,eAAe,gBAAgB,CAAC"}

package/dist/src/tools/remove-repository.js

@@ -1,4 +1,4 @@
-import { deleteJson, requireUserApiConfig } from "../support/specguard-api.js";
+import { deleteJson, requireUserOrAgentApiConfig } from "../support/specguard-api.js";
 import { requireString } from "./args.js";
 /**
  * `DELETE /api/v1/repositories/:id` as a tool — shipped in the platform
@@ -44,9 +44,15 @@ const removeRepository = {
         "cannot be brought back. " +
         "Takes `repository_id` — the numeric id `add_repository` and `list_repositories` " +
         "report, not the `org/repo` handle. " +
-        "Needs SPECGUARD_USER_API_KEY (an sgu_… key), the same credential `add_repository` " +
-        "writes with and a DIFFERENT one from the sgk_… repository key " +
-        "`get_repository_overview` uses.",
+        "It authenticates with EITHER of this server's two repository-administration credentials, " +
+        "whichever is set: SPECGUARD_AGENT_API_KEY (an sga_… key — the call then reaches only the " +
+        "repositories granted onto that key at mint time, and only where the grant carries " +
+        "`repo.delete`; a repository outside that set answers 404 in SpecGuard's own words, never " +
+        "a probe here) and, when that is not set, SPECGUARD_USER_API_KEY (an sgu_… key, the same " +
+        "credential `add_repository` writes with). With both set the agent key wins, so the " +
+        "removal answers inside the same set `list_repositories` reports. " +
+        "Either way it is a DIFFERENT credential from the sgk_… repository key " +
+        "`get_repository_overview` uses; SpecGuard refuses each in the other's place.",
     inputSchema: {
         type: "object",
         properties: {
@@ -66,7 +72,7 @@ const removeRepository = {
     },
     async run(args, context) {
         const repositoryId = requireString(args["repository_id"], "repository_id");
-        const api = requireUserApiConfig(context.config);
+        const api = requireUserOrAgentApiConfig(context.config);
         const body = await deleteJson(api, `/api/v1/repositories/${encodeURIComponent(repositoryId)}`, context.fetch);
         // 204 with no body. Nothing upstream to pass through, so the result says
         // what the verb did — in the tool's own words, because the deployment's

package/dist/src/tools/remove-repository.js.map

@@ -1 +1 @@
-{"version":3,"file":"remove-repository.js","sourceRoot":"","sources":["../../../src/tools/remove-repository.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,oBAAoB,EAAE,MAAM,6BAA6B,CAAC;AAC/E,OAAO,EAAE,aAAa,EAAE,MAAM,WAAW,CAAC;AAG1C;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,MAAM,gBAAgB,GAAmB;IACvC,IAAI,EAAE,mBAAmB;IACzB,KAAK,EAAE,mBAAmB;IAC1B,WAAW,EACT,iFAAiF;QACjF,sFAAsF;QACtF,8EAA8E;QAC9E,0DAA0D;QAC1D,mFAAmF;QACnF,sFAAsF;QACtF,uFAAuF;QACvF,kFAAkF;QAClF,0BAA0B;QAC1B,kFAAkF;QAClF,qCAAqC;QACrC,oFAAoF;QACpF,gEAAgE;QAChE,iCAAiC;IACnC,WAAW,EAAE;QACX,IAAI,EAAE,QAAQ;QACd,UAAU,EAAE;YACV,aAAa,EAAE;gBACb,IAAI,EAAE,QAAQ;gBACd,WAAW,EACT,+EAA+E;oBAC/E,+EAA+E;oBAC/E,sEAAsE;aACzE;SACF;QACD,QAAQ,EAAE,CAAC,eAAe,CAAC;QAC3B,qEAAqE;QACrE,0EAA0E;QAC1E,yEAAyE;QACzE,gEAAgE;QAChE,oBAAoB,EAAE,KAAK;KAC5B;IAED,KAAK,CAAC,GAAG,CAAC,IAAI,EAAE,OAAO;QACrB,MAAM,YAAY,GAAG,aAAa,CAAC,IAAI,CAAC,eAAe,CAAC,EAAE,eAAe,CAAC,CAAC;QAE3E,MAAM,GAAG,GAAG,oBAAoB,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QAEjD,MAAM,IAAI,GAAG,MAAM,UAAU,CAC3B,GAAG,EACH,wBAAwB,kBAAkB,CAAC,YAAY,CAAC,EAAE,EAC1D,OAAO,CAAC,KAAK,CACd,CAAC;QAEF,yEAAyE;QACzE,wEAAwE;QACxE,iCAAiC;QACjC,OAAO;YACL,IAAI,EAAE,IAAI,KAAK,EAAE,CAAC,CAAC,CAAC,uEAAuE,CAAC,CAAC,CAAC,IAAI;YAClG,UAAU,EAAE,EAAE,aAAa,EAAE,YAAY,EAAE,OAAO,EAAE,IAAI,EAAE;SAC3D,CAAC;IACJ,CAAC;CACF,CAAC;AAEF,eAAe,gBAAgB,CAAC"}
+{"version":3,"file":"remove-repository.js","sourceRoot":"","sources":["../../../src/tools/remove-repository.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,2BAA2B,EAAE,MAAM,6BAA6B,CAAC;AACtF,OAAO,EAAE,aAAa,EAAE,MAAM,WAAW,CAAC;AAG1C;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,MAAM,gBAAgB,GAAmB;IACvC,IAAI,EAAE,mBAAmB;IACzB,KAAK,EAAE,mBAAmB;IAC1B,WAAW,EACT,iFAAiF;QACjF,sFAAsF;QACtF,8EAA8E;QAC9E,0DAA0D;QAC1D,mFAAmF;QACnF,sFAAsF;QACtF,uFAAuF;QACvF,kFAAkF;QAClF,0BAA0B;QAC1B,kFAAkF;QAClF,qCAAqC;QACrC,2FAA2F;QAC3F,2FAA2F;QAC3F,oFAAoF;QACpF,2FAA2F;QAC3F,0FAA0F;QAC1F,qFAAqF;QACrF,mEAAmE;QACnE,wEAAwE;QACxE,8EAA8E;IAChF,WAAW,EAAE;QACX,IAAI,EAAE,QAAQ;QACd,UAAU,EAAE;YACV,aAAa,EAAE;gBACb,IAAI,EAAE,QAAQ;gBACd,WAAW,EACT,+EAA+E;oBAC/E,+EAA+E;oBAC/E,sEAAsE;aACzE;SACF;QACD,QAAQ,EAAE,CAAC,eAAe,CAAC;QAC3B,qEAAqE;QACrE,0EAA0E;QAC1E,yEAAyE;QACzE,gEAAgE;QAChE,oBAAoB,EAAE,KAAK;KAC5B;IAED,KAAK,CAAC,GAAG,CAAC,IAAI,EAAE,OAAO;QACrB,MAAM,YAAY,GAAG,aAAa,CAAC,IAAI,CAAC,eAAe,CAAC,EAAE,eAAe,CAAC,CAAC;QAE3E,MAAM,GAAG,GAAG,2BAA2B,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QAExD,MAAM,IAAI,GAAG,MAAM,UAAU,CAC3B,GAAG,EACH,wBAAwB,kBAAkB,CAAC,YAAY,CAAC,EAAE,EAC1D,OAAO,CAAC,KAAK,CACd,CAAC;QAEF,yEAAyE;QACzE,wEAAwE;QACxE,iCAAiC;QACjC,OAAO;YACL,IAAI,EAAE,IAAI,KAAK,EAAE,CAAC,CAAC,CAAC,uEAAuE,CAAC,CAAC,CAAC,IAAI;YAClG,UAAU,EAAE,EAAE,aAAa,EAAE,YAAY,EAAE,OAAO,EAAE,IAAI,EAAE;SAC3D,CAAC;IACJ,CAAC;CACF,CAAC;AAEF,eAAe,gBAAgB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specguard-mcp",
-  "version": "0.1.13",
+  "version": "0.1.15",
   "description": "MCP server exposing SpecGuard suite intelligence to AI coding agents",
   "license": "ISC",
   "type": "module",
@@ -19,7 +19,7 @@
   "scripts": {
     "build": "tsc --project tsconfig.build.json",
     "typecheck": "tsc --noEmit",
-    "pretest": "tsc --project tsconfig.test.json",
+    "pretest": "rm -rf .test-build && tsc --project tsconfig.test.json",
     "test": "files=$(find .test-build/test -name '*.test.js'); [ -n \"$files\" ] || { echo 'specguard-mcp: no compiled test files found — did pretest run?'; exit 1; }; node --test $files",
     "prepare": "npm run build"
   },