Background
A maintainer decision in #174 says to remove npm information and code. The current repository and parked PR #156 still contain npm launch/package surfaces, so the package-channel decision needs a focused cleanup path instead of further npm metadata alignment.

Evidence

• Decide npm package publication path before launch docs go live #174 maintainer comment on 2026-05-19: i desided remove all npm info and code.
• npm view agenttrace version --json still returns npm E404.
• Add growth assets and npm launch docs #156 includes npm launch docs/package surfaces and is no longer aligned with the recorded package-channel decision.
• Align npm package surfaces with current parser coverage #189 keyword alignment has been stopped because improving npm metadata conflicts with the removal decision.

User value
Users should only see install and distribution paths that actually exist and are intended to be supported. Removing unavailable npm surfaces avoids a broken install path and keeps onboarding trust high.

Adoption rationale
Install clarity is a first-run trust issue. The project already has active non-npm paths such as install scripts, Go install, Homebrew docs, and GitHub releases; public docs should concentrate on supported paths.

Suggested scope

• Remove npm package information from public docs and site surfaces.
• Remove or neutralize npm package wrapper files from repository/package surfaces according to maintainer intent.
• Remove npm-specific launch copy from Add growth assets and npm launch docs #156 or split Add growth assets and npm launch docs #156 so non-npm public-doc improvements can proceed separately.
• Update CI/release-surface checks if they currently require npm prepared/unpublished wording.

Non-goals

• No npm publish.
• No tag, GitHub release, Homebrew publish, or external posting.
• No unrelated parser, TUI, report, or install-script behavior changes.
• No broad rewrite of README positioning beyond removing npm-specific claims.

Acceptance criteria

• No public surface promotes npm as an active, prepared, or upcoming install path.
• Repository package surfaces no longer imply npm package support.
• Release-surface checks, docs command checks, Pages checks if touched, go build, and go test ./... pass.
• Decide npm package publication path before launch docs go live #174 is updated with cleanup validation once landed.
• Align npm package surfaces with current parser coverage #189 remains closed or obsolete as a metadata-alignment route.

Suggested lane
lane/growth

Risk
P1. This touches install/distribution copy and release-surface checks. The main risk is leaving stale npm references behind or accidentally weakening checks for supported install paths.

Source
Product routing after maintainer decision in #174 and current PR #156/#189 state.