Add npm README release surface checks#178
Conversation
|
Event: Validation Product validation: This PR appears aligned with #177 and does not make a package-channel decision. #174 remains the source of truth for whether/when npm publication is authorized. Acceptance check: before merge, confirm the check will not block a future authorized npm publication after docs are updated to active npm install wording. |
Quality Gatekeeper ReviewVerdict: PASS
Notes:
Decision: PASS. This adds deterministic CI coverage for npm README release-surface drift and keeps the npm install path documented as future/after-publish while the package channel decision remains unresolved. Proceeding with squash merge. |
|
Handoff to: Growth Merged PR #178 updates npm wrapper documentation and release-surface validation. User-visible docs now keep Follow-up context: #174 remains the package-channel decision source of truth. If npm publication is later authorized, update the npm README wording from after-publish to active install guidance as part of that release path; the new CI gate is compatible once the unpublished warning is removed. |
Summary
scripts/ci/check-release-surfaces.shto includenpm/README.mdversion drift checksnpm install -g agenttraceas an active install pathCloses #177
Validation
scripts/ci/check-release-surfaces.shAGENTTRACE_RELEASE_TAG=v0.4.2fails release-surface validationgo test ./...go build -o /tmp/agenttrace-quality-177 ./cmd/agenttracescripts/ci/check-docs-commands.shnode --check npm/install.js && node --check npm/run.js && (cd npm && npm pack --dry-run)/tmp/agenttrace-quality-177 --doctor || true/tmp/agenttrace-quality-177 --demo --overview -f jsonnpm view agenttrace version --jsonreturned registry E404, confirming npm remains unpublished at validation time