Skip to content

[codex] Align guide parser coverage#195

Merged
luoyuctl merged 1 commit into
masterfrom
growth/guide-docs-parser-coverage
May 12, 2026
Merged

[codex] Align guide parser coverage#195
luoyuctl merged 1 commit into
masterfrom
growth/guide-docs-parser-coverage

Conversation

@luoyuctl
Copy link
Copy Markdown
Owner

Summary

  • align AI observability guide metadata and proof-strip source wording with current README support
  • align secondary docs/demo copy with current parser coverage
  • avoid npm, package-channel, or release promises

Validation

  • git diff --check
  • scripts/ci/check-pages-artifact.sh site
  • scripts/ci/check-release-surfaces.sh
  • scripts/ci/check-docs-commands.sh
  • go test ./...
  • go build -o /tmp/agenttrace-guide-docs-check ./cmd/agenttrace
  • /tmp/agenttrace-guide-docs-check --version

Notes

@luoyuctl luoyuctl added lane/growth Adoption and distribution work status/in-progress Currently being worked on labels May 12, 2026
@luoyuctl luoyuctl marked this pull request as ready for review May 12, 2026 09:53
@luoyuctl
Copy link
Copy Markdown
Owner Author

Event: Routing / Validation pending
Actor: Product
Scope: PR #195 / Issues #191 #192
State change: added lane/growth + status/in-progress
Evidence: PR #195 is a draft Growth PR that changes only docs/community-pain-points.md, docs/demo-playbook.md, and site/ai-agent-observability.html, and its body says it covers #191 and #192. The diff stays within those issue scopes and does not introduce npm/package/release promises. GitHub CI was still in progress when Product first inspected the PR.
Next owner: Growth / Product review after CI

Decision: Treat #195 as the active implementation path for #191 and #192, not as a separate release/package authorization. Keep status/in-progress until CI completes, then move to ready-for-review if checks pass and the source wording remains within README-level support.

@luoyuctl luoyuctl merged commit da631a2 into master May 12, 2026
1 check passed
@luoyuctl luoyuctl deleted the growth/guide-docs-parser-coverage branch May 12, 2026 09:53
@luoyuctl luoyuctl added status/auto-merged and removed status/in-progress Currently being worked on labels May 12, 2026
@luoyuctl
Copy link
Copy Markdown
Owner Author

Event: Validation / Decision
Actor: Product
Scope: PR #195 / Issues #191 #192
State change: fixed PR label to lane/growth + status/auto-merged after merge
Evidence: PR #195 merged on 2026-05-12 at da631a2 and changed only docs/community-pain-points.md, docs/demo-playbook.md, and site/ai-agent-observability.html. GitHub CI Test and build is SUCCESS. Product post-merge validation on origin/master da631a2 passed go build, /tmp/agenttrace-product-check --doctor, scripts/ci/check-pages-artifact.sh site, scripts/ci/check-docs-commands.sh, and scripts/ci/check-release-surfaces.sh. Source wording now includes the newer README-level source families in the affected docs/guide surfaces and does not add npm/package/release promises.
Next owner: Product

Decision: Product accepts #195 as satisfying #191 and #192. Closing those issues separately after recording validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane/growth Adoption and distribution work status/auto-merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant