Extend release-surface checks to root README npm availability wording

[luoyuctl]

Background

PR #178 added release-surface checks for npm/README.md, but origin/master root README.md still contains npm availability wording while the npm package-channel decision is unresolved. PR #156 improves this copy, but it is still draft + status/needs-human, so the repeatable guard should cover the root README too.

Evidence

• Current npm registry state is tracked by Decide npm package publication path before launch docs go live #174 and remains unresolved/unpublished.
• origin/master root README.md currently says: The npm wrapper is also available as agenttrace after each release is published.
• npm/README.md is now guarded by scripts/ci/check-release-surfaces.sh, but root README.md is not checked for unavailable npm install or availability wording.
• PR Add growth assets and npm launch docs #156 changes the root README copy to cautious unpublished-npm wording, but that PR is not merged and is blocked by Decide npm package publication path before launch docs go live #174/Add a concise strategic Roadmap for contributor routing #176.

User value

Users should not infer that npm is an active or automatically available install path before the package-channel decision is recorded and publication actually happens.

Adoption rationale

Install clarity protects first-run trust. If the root README drifts independently from npm/README.md, users may try an unavailable package path even when the npm wrapper docs are cautious.

Suggested scope

• Extend scripts/ci/check-release-surfaces.sh or an equivalent docs gate to catch root README npm availability wording while npm remains unpublished.
• Keep the check deterministic and narrow: it should guard against active or implied-available npm wording before Decide npm package publication path before launch docs go live #174 is resolved.
• If Decide npm package publication path before launch docs go live #174 later authorizes and completes npm publication, update the check and docs together to reflect the new package state.

Non-goals

• Do not publish npm from this task.
• Do not decide the npm package-channel policy; Decide npm package publication path before launch docs go live #174 owns that decision.
• Do not merge or rewrite PR Add growth assets and npm launch docs #156 from this task.
• Do not broadly rewrite README positioning beyond the npm availability guard.

Acceptance criteria

• Release-surface validation fails when root README.md presents npm as active/available while the package remains unpublished.
• Existing release/docs checks still pass on the intended current wording.
• Decide npm package publication path before launch docs go live #174 remains the source of truth for future npm publication decisions.
• Public docs continue to avoid unavailable active npm install instructions.

Suggested lane

lane/quality

Risk

Low. The main risk is making the check too broad and blocking future authorized npm docs; keep the condition tied to unpublished-state wording and update it when #174 is resolved.

Source

Product release-surface audit on 2026-05-10 after #178 merged.

[luoyuctl]

Event: Handoff
Actor: Product
Scope: Issue #181
State change: keep lane/quality + status/ready-for-agent
Evidence: #178 guards npm/README.md, but root README.md on origin/master still has npm availability wording while #174 remains unresolved. PR #156 improves the copy but is draft + status/needs-human, so a repeatable root README guard is still useful.
Next owner: Quality

Handoff to: Quality
Reason: This is a small CI/docs validation gap, not a package-channel decision.
Expected output: extend release-surface checks so root README cannot present npm as active or implied-available before npm publication is authorized and complete.
Acceptance check: the guard fails on unavailable active/implied npm wording in root README, passes on the intended cautious wording, and leaves #174 as the source of truth for future npm publication state.

[luoyuctl]

Event: Validation / Decision
Actor: Product
Scope: Issue #181 / PR #182
State change: status/in-progress -> status/ready-for-review
Evidence: PR #182 closes this issue, is non-draft, mergeStateStatus=CLEAN, and GitHub CI Test and build is SUCCESS. The diff updates root README.md from implied npm availability to cautious unpublished-package wording and extends scripts/ci/check-release-surfaces.sh to fail when root README presents npm as active while npm/README.md documents the package as unpublished.
Next owner: Quality / Human

Validation: PR #182 appears to satisfy the Product acceptance criteria for #181. Product is not merging.

Acceptance check before merge: Quality/Human confirms the guard remains deterministic, the root README wording stays cautious while npm is unpublished, and #174 continues to own the package-channel decision.

[luoyuctl]

Event: Validation / Decision
Actor: Product
Scope: Issue #181 / origin/master after PR #182
State change: status/ready-for-review -> status/auto-merged; issue already closed by merged PR
Evidence: PR #182 was merged at 2026-05-10T14:24:41Z. Post-merge Product validation fetched origin/master at bca61ea, built agenttrace v0.4.6, passed scripts/ci/check-release-surfaces.sh, passed scripts/ci/check-docs-commands.sh, and confirmed root README.md now says the npm wrapper package is not published yet.
Next owner: none for this issue

Decision: Scope complete. #174 remains open for the actual npm package-channel decision.