From 800a7a770bb5a286ceb586b10a4b2d8729a41411 Mon Sep 17 00:00:00 2001
From: hbrooks <seanhunterbrooks@gmail.com>
Date: Mon, 13 Jul 2026 13:10:18 -0400
Subject: [PATCH] chore: drop vestigial npm packaging (private, no
 bin/publishConfig)

The CLI ships only as a Bun-compiled single binary via the Homebrew tap; it is never published to npm. Keeping a bin/publishConfig let a local 'npm i -g .' install a global 'agent' that shadowed the brew binary and froze at an old version. Mark the package private and remove bin/files/publishConfig so that footgun is gone.
---
 package.json | 11 ++---------
 1 file changed, 2 insertions(+), 9 deletions(-)

diff --git a/package.json b/package.json
index 29d7d7d..ff2d58f 100644
--- a/package.json
+++ b/package.json
@@ -5,18 +5,11 @@
   "license": "MIT",
   "type": "module",
   "packageManager": "bun@1.3.14",
-  "bin": {
-    "agent": "dist/cli.js"
-  },
-  "files": [
-    "dist"
-  ],
+  "//": "Not an npm package. The CLI ships only as a Bun-compiled single binary via the Homebrew tap (see .github/workflows/release.yml). `private` blocks accidental `npm publish`; there is deliberately no `bin` so `npm i -g .` can't install a stale global that shadows the brew binary.",
+  "private": true,
   "engines": {
     "node": ">=18"
   },
-  "publishConfig": {
-    "access": "public"
-  },
   "scripts": {
     "dev": "tsx src/cli.tsx",
     "build": "tsup",