Decide npm package publication path before launch docs go live

[luoyuctl]

Background

The repository now contains npm wrapper metadata for agenttrace, and PR #156 is open for npm launch docs/assets. The npm registry currently does not have a published agenttrace package, so the package launch path needs an explicit maintainer decision before any publish action.

Evidence

• npm view agenttrace version --json returns npm E404 for https://registry.npmjs.org/agenttrace.
• PR Add growth assets and npm launch docs #156 is open, draft, clean, and CI-green, with labels lane/growth and status/needs-human.
• PR Add growth assets and npm launch docs #156 validation notes indicate npm pack --dry-run passes, but publish was not executed because no npm auth/authorization was available.
• Product validation comment was added to PR Add growth assets and npm launch docs #156 on 2026-05-10, keeping the next owner as Human / Growth.

User value

Users should not be shown or routed through an npm install path until maintainers have decided whether and when the package should be published.

Adoption rationale

A clean package-channel decision prevents install confusion and avoids stale public instructions for a package name that is still unpublished.

Suggested scope

• Decide whether agenttrace should be published to npm now, reserved for later, or explicitly kept as a future channel.
• If publish is approved, record the required authorization in the PR or release issue before any package publish step.
• If publish is deferred, keep public docs clear that Homebrew, install script, and GitHub release binaries are the active install paths.

Non-goals

• Do not run npm publish from this issue.
• Do not create tags, GitHub releases, Homebrew changes, or external posts.
• Do not add or expose npm tokens in issues, PRs, docs, logs, or comments.

Acceptance criteria

• Maintainer decision is recorded: publish now, defer, or do not publish.
• PR Add growth assets and npm launch docs #156 either remains blocked on explicit authorization or is updated with a clear authorized next step.
• Public install docs do not imply a currently unavailable npm package unless publish has completed.

Suggested lane

lane/growth

Risk

High for release/package surface because package publishing is externally visible and requires credentials and explicit maintainer authorization.

Source

Product release-surface pass on 2026-05-10, npm registry check, and PR #156 state.

[luoyuctl]

Event: Decision
Actor: Product
Scope: Issue #174
State change: keep lane/growth + status/needs-human
Evidence: npm registry currently returns E404 for agenttrace; PR #156 is draft, clean, CI-green, and blocked on package-channel authorization.
Next owner: Human

Handoff to: Human / Growth
Reason: Publishing or advertising an npm package is externally visible and requires explicit maintainer authorization; Product must not publish packages or imply unavailable install paths.
Expected output: record one decision: publish now with explicit authorization, defer npm as a future channel, or do not publish.
Acceptance check: PR #156 and public install docs reflect the decision; no npm publish occurs without explicit authorization, and unavailable npm instructions are not promoted as active install paths.
Context: PR #156: #156.

[luoyuctl]

Event: Evidence
Actor: Product
Scope: Issue #174
State change: no label change; keep status/needs-human
Evidence: Rechecked on 2026-05-10: npm view agenttrace version --json still returns npm E404, while origin/master still contains npm/README.md with npm install -g agenttrace. This confirms the package-channel decision remains unresolved and externally visible install copy must not be promoted as active until authorization/publish state is clear.
Next owner: Human / Growth

[luoyuctl]

Event: Evidence / Decision
Actor: Product
Scope: Issue #174 / PR #156
State change: no label change; keep lane/growth + status/needs-human
Evidence: Rechecked npm on 2026-05-10: npm view agenttrace version --json still returns E404. PR #156 is CI-green / mergeStateStatus=CLEAN and now changes README + npm README copy so the npm wrapper is described as prepared but not published, routing users to install script, Homebrew, Go install, or GitHub release binaries until publication is explicitly authorized.
Next owner: Human / Growth

Decision: The public-copy risk is reduced in PR #156, but the package-channel decision is still unresolved. Keep this issue open until a maintainer records publish now / defer / do not publish.

Acceptance check: if #156 proceeds before npm publication, npm copy must stay cautious and must not present npm install -g agenttrace as an active install path. If npm publication is approved later, record explicit authorization before any publish step and then update public install docs to match the completed package state.

[luoyuctl]

Event: Evidence / Decision
Actor: Product
Scope: Issue #174 / PR #178
State change: no label change; keep lane/growth + status/needs-human
Evidence: PR #178 was merged on 2026-05-10 and added release-surface CI coverage for npm/README.md, including stale AGENTTRACE_RELEASE_TAG detection and unpublished npm install wording checks. Post-merge Product validation on origin/master passed release surfaces, docs commands, output contract, deterministic output, report semantics, and Pages artifact checks.
Next owner: Human / Growth

Decision: The public-copy drift risk is now lower on origin/master, but the package-channel decision remains unresolved. Keep this issue open until a maintainer records publish now / defer / do not publish.

Acceptance check: no npm publish occurs and no active npm install path is promoted until explicit authorization and actual package publication are complete. If publication is approved later, update docs and CI expectations to match the new active package state.