@jigyasudham/veto 2.7.1 → 2.7.3

package/MCP-REGISTRY.md

@@ -1,94 +0,0 @@
-# Publishing Veto to the official MCP Registry
-
-This document is the runbook for listing Veto on the [official Model Context
-Protocol registry](https://registry.modelcontextprotocol.io) so it appears on
-official sources and in registry-backed directories. The registry entry is
-defined by [`server.json`](../server.json) at the repo root.
-
-## How the registry verifies ownership
-
-The registry does **not** host the package — it points at the npm package
-`@jigyasudham/veto`. To prove we own that package, the registry fetches
-`https://registry.npmjs.org/@jigyasudham/veto/<version>` and reads the
-top-level **`mcpName`** field from the published `package.json`. It must equal
-the `name` in `server.json`:
-
-```
-io.github.jigyasudham/veto
-```
-
-The `io.github.jigyasudham/*` namespace is owned by proving control of the
-GitHub account `jigyasudham` (interactive OAuth at publish time).
-
-> **Critical ordering:** the npm version referenced in `server.json` must
-> already be published **with** the `mcpName` field. The previously published
-> `2.1.1` did **not** have `mcpName`, which is why this listing ships as
-> `2.1.2` — the first npm release that carries it. Always `npm publish` first,
-> then `mcp-publisher publish`.
-
-## Files involved
-
-| File | Role |
-|---|---|
-| `server.json` | The registry entry (schema `2025-12-11`). Name, description (≤100 chars), repository, and the npm package + stdio transport. |
-| `package.json` | Carries `"mcpName": "io.github.jigyasudham/veto"` — the ownership proof read off npm. Keep its `version` equal to `server.json` `version` and `packages[0].version`. |
-
-Keep all three version fields in lockstep on every release:
-`package.json.version` == `server.json.version` == `server.json.packages[0].version`.
-
-## Publish steps
-
-Run from the repo root, on a clean `main` at the tagged release commit.
-
-1. **Publish the npm release that carries `mcpName`** (the user does this — it
-   needs npm credentials):
-
-   ```bash
-   npm run build
-   npm publish --access public        # publishes @jigyasudham/veto@2.1.2
-   ```
-
-   Verify the field landed on npm:
-
-   ```bash
-   curl -s https://registry.npmjs.org/@jigyasudham/veto/2.1.2 | grep -o '"mcpName":"[^"]*"'
-   # -> "mcpName":"io.github.jigyasudham/veto"
-   ```
-
-2. **Install the registry publisher CLI** (`mcp-publisher`). Either download a
-   release binary from
-   [`modelcontextprotocol/registry`](https://github.com/modelcontextprotocol/registry/releases)
-   or build from source (`make publisher` -> `./bin/mcp-publisher`).
-
-3. **Authenticate the namespace** with the GitHub account `jigyasudham`
-   (interactive — opens a browser):
-
-   ```bash
-   mcp-publisher login github
-   ```
-
-4. **Validate and publish** the entry (reads `server.json` from the cwd):
-
-   ```bash
-   mcp-publisher publish
-   ```
-
-   The registry re-runs npm ownership validation server-side; if step 1 was
-   skipped it fails with *"NPM package is missing required 'mcpName' field"*.
-
-5. **Confirm the listing:**
-
-   ```bash
-   curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=veto" | grep -o '"name":"io.github.jigyasudham/veto"'
-   ```
-
-## Updating the listing on future releases
-
-For each new release: bump `version` in `package.json` **and** both version
-fields in `server.json`, `npm publish`, then re-run `mcp-publisher publish`.
-The `mcpName` field never changes.
-
-## Lifecycle
-
-Use `mcp-publisher status` to move the server between `active`, `deprecated`,
-and `deleted` states if needed.

package/VETO-MCP-DIAGNOSTIC.md

@@ -1,73 +0,0 @@
-# Veto MCP — connection failure diagnostic
-
-Run these in the **failing VS Code window's project terminal** (the project where the
-`veto_*` tools won't load). Paste all output back.
-
-Context: Veto's server imports `node:sqlite` at startup, which needs **Node >= 22.5.0**.
-If that window resolves an older Node, the server throws and exits immediately — the exact
-"launches but never runs the stdio loop" symptom. These four checks pin down the cause.
-
----
-
-## Run this block (PowerShell)
-
-```powershell
-# 1. What command is this project actually configured to launch for veto?
-claude mcp get veto
-
-# (fallback if the above errors)
-claude mcp list
-
-# 2. Node version this window resolves — MUST be >= 22.5.0
-node --version
-
-# 3. Can a bare `veto-server` even resolve, and is it installed globally?
-where.exe veto-server
-npm ls -g @jigyasudham/veto
-
-# 4. Decisive test — launch the server directly and watch what it prints:
-npx -y --package @jigyasudham/veto veto-server
-```
-
-For step 4:
-- **GOOD** -> prints `Veto MCP server v2.1.2 running (stdio)` then hangs. Press **Ctrl+C** to exit.
-- **BAD**  -> an error/stack trace (copy the whole thing) OR it returns to the prompt instantly.
-
----
-
-## What each result means
-
-| Check | If this is the problem | Fix |
-|---|---|---|
-| **#2 Node < 22.5.0** | `node:sqlite` import throws -> server exits immediately | Point the MCP command at a Node >= 22.5.0, or use the `npx` form below (it inherits PATH — make sure that PATH's Node is >= 22.5.0). |
-| **#3 `veto-server` not found** | config launches a bare `veto-server` that isn't on PATH | Use the `npx` command form below instead of a bare binary. |
-| **#1 config points at `dist/server.js` of a different/uninstalled path** | wrong launcher | Repoint to the `npx` form below. |
-| **#4 prints a stack trace** | the package itself errors in this environment | Copy the trace — that's the real bug; bring it back here. |
-| **#4 GOOD but tools still fail in-CLI** | config command != the working `npx` one | Repoint config to the `npx` form, then fully restart the CLI. |
-
----
-
-## The likely fix (repoint the config to the known-good launcher)
-
-Update that project's veto MCP server entry to:
-
-```json
-{
-  "command": "npx",
-  "args": ["-y", "--package", "@jigyasudham/veto", "veto-server"]
-}
-```
-
-Or via CLI from that project dir:
-
-```powershell
-claude mcp remove veto
-claude mcp add veto -- npx -y --package @jigyasudham/veto veto-server
-```
-
-Then **fully restart Claude Code** — MCP config is read only at startup, so the current
-in-memory session won't recover; the next launch will.
-
-Note: `npx -y` now pulls **2.1.2** (latest), so a healthy run reports `v2.1.2`.
-Verify the resolved Node behind `npx` is >= 22.5.0 (`node --version`), or the npx form
-will fail the same way.