docs: accept npx distribution spec

[CharlesYWL]

Marks the npx distribution design as Accepted, approved by Charles on 2026-08-27, with the npm scope locked as @copilot-fleet (packages @copilot-fleet/protocol, @copilot-fleet/host, @copilot-fleet/node). The spec's git update path is aligned with the current apps/node/src/updater.ts: git fetch --prune followed by git reset --hard onto @{u}, replacing every stale git pull --ff-only mention; the npm path stays npm install @copilot-fleet/node@latest in the persistent prefix.

Follow-up commits fold in Copilot's three blockers as locked decisions, then the ESM-alias correction (@fleet/protocol keys stay; specs become npm:@copilot-fleet/protocol@<version>), then a third pass from local npm pack / install:

• There is no bin/ directory. Packed bins are ./supervisor.mjs (Node) and ./host.mjs (Host) at the package root.
• Packed files is mandatory. Root .gitignore has dist/, so an unrewritten protocol pack after tsc ships 0 dist files; pointing Node's bin at the supervisor without files drops Node dist from 69 files to 0.
• npm: aliases only work for registry deps. Local smoke file:-installs protocol under the @fleet/protocol key (or overrides) and launches the bin. Publish protocol first.

Spec-only change; no runtime code is touched.

Verified locally (Node 22.14.0 / npm 10.9.7): protocol pack dist=0 src=8; node pack dist=69 src=45 bin/=0 supervisor.mjs present; rewriting the dep key to @copilot-fleet/protocol throws ERR_MODULE_NOT_FOUND; keeping the @fleet/protocol key imports; overrides + packed node bin launches.

  

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9c3fff78-75ef-48c6-a350-e21bd43367b2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[CharlesYWL]

@copilot Please review this design

[Copilot]

@copilot Please review this design

Review found three blockers before implementation:

1. publishConfig.name does not rename a package (npm publish --dry-run still publishes the manifest’s name), and Host/Node would still depend on unpublished @fleet/protocol. The release design needs publish-ready manifests that rewrite both package names and internal dependencies (or permanent workspace renames), remove private, and set scoped packages to public access.
2. The proposed Node tarball omits agents/ and public/, but runtime code reads both (agent-catalog.ts and config-assets.ts). They must be included and covered by a packed-tarball smoke test.
3. Reusing the current unbounded repoRoot() walk for install-kind/revision detection can escape an npm prefix into an ancestor workspace or git repo. That can misclassify the Node as git, report the wrong SHA, and potentially hard-reset an unrelated checkout. Detection must be bounded to the running package/runtime prefix.

The fetch/reset and packageVersion() updates in this PR accurately describe the current implementation. I did not alter the accepted spec because the packaging and detection choices need to be resolved first.