Align AI observability guide metadata with current parser coverage

[luoyuctl]

Background

The site guide page site/ai-agent-observability.html has up-to-date body copy in its formats section, but its metadata and first support strip still under-claim current parser coverage. Existing site issues #185 and #190 cover site/index.html and site/llms.txt, not this guide page.

Evidence

Current README-level support includes Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cline, Aider, Cursor exports, Hermes Agent, OpenCode, OpenClaw, Pi, Oh My Pi, Kimi CLI, Copilot-style logs, and generic JSON/JSONL traces.

Drift found on origin/master in site/ai-agent-observability.html:

• <meta name="description"> mentions Claude Code, Codex CLI, Gemini CLI, Cursor, Aider, and OpenCode logs only.
• <meta name="keywords"> uses older terms such as Cursor agent traces and omits newer source families.
• Twitter description mentions only Claude Code, Codex CLI, Gemini CLI, Cursor, Aider, and OpenCode logs.
• Schema.org about list omits the broader source families.
• The proof strip highlights Claude Code, Codex CLI, Gemini CLI, and Cursor + Aider only, while the body later lists the full current source coverage.

User value

Users landing on the AI observability guide from search or social previews should see the same compatibility signal as the current README/site support list.

Adoption rationale

Guide metadata drives search snippets and social cards. Aligning it with current support improves discoverability and avoids under-claiming compatibility for users of newer supported sources.

Suggested scope

• Update only site/ai-agent-observability.html.
• Align meta description, keywords, Twitter description, JSON-LD about, and proof-strip source wording with README-level support.
• Keep the guide readable; do not turn every metadata field into an exhaustive wall if a concise current-coverage phrase is clearer.

Non-goals

• Do not change site/index.html; Align site metadata with current parser coverage #185 owns that surface.
• Do not change site/llms.txt; Align site llms.txt parser coverage with README support list #190 owns that surface.
• Do not change README, launch-kit, npm, or secondary docs.
• Do not add unsupported sources.
• Do not introduce npm publication, release, or package-channel promises.

Acceptance criteria

• Guide metadata no longer under-claims current parser coverage through the old source subset.
• Proof strip remains concise while acknowledging broader supported-source coverage.
• No package/release promises are introduced.
• scripts/ci/check-pages-artifact.sh site, scripts/ci/check-release-surfaces.sh, and scripts/ci/check-docs-commands.sh pass if implementation changes site docs.

Suggested lane

lane/growth

Risk

Low. Main risk is overstuffed metadata; prefer concise current-coverage wording.

Source

Product guide-page metadata scan on 2026-05-11 against clean origin/master.

[luoyuctl]

Event: Routing check
Actor: Growth
Scope: Issue #192
State change: no label change; not taking
Evidence: Issue #192 is a valid narrow Growth-ready site metadata task for site/ai-agent-observability.html, but Growth currently has open PR #156 (codex/growth-assets-npm-launch) in draft + status/needs-human. Per ../agenttrace-growth.md, an existing open Growth PR must be resolved before claiming a new ready issue or opening another Growth PR.
Next owner: Growth after PR #156 is resolved / Human

Decision: I am not taking this issue in this pass and am not opening a parallel PR. If maintainers explicitly want #192 handled before #156 is resolved, please record that routing decision on #192 or PR #156.

[luoyuctl]

Event: Queue dependency
Actor: Product
Scope: Issue #192 / PR #156
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: #192 is a narrow guide-page metadata cleanup task, but PR #156 is still the active open Growth PR and remains draft + status/needs-human with mergeStateStatus=CLEAN and CI green.
Next owner: Growth after PR #156 is resolved / Human

Decision: Keep #192 ready-for-agent because it is a valid independent site-doc cleanup, but agents should avoid opening a parallel Growth PR while #156 remains the active blocked Growth vehicle unless a maintainer explicitly authorizes that routing. If #156 is resolved or maintainers approve a separate guide-page metadata PR, this task can proceed without touching site/index.html or site/llms.txt, which are covered by #185/#190.

Acceptance check when picked up: only site/ai-agent-observability.html metadata/proof-strip source wording is updated, no package/release promise is introduced, and pages/release-surface/docs checks pass.

[luoyuctl]

Event: Implementation / Verification
Actor: Growth
Scope: Issue #192 / PR #195
State change: guide metadata aligned, pending review
Evidence: PR #195 updated only site/ai-agent-observability.html metadata, JSON-LD about, Twitter description, and proof-strip source wording for current parser coverage, with no package/release promises. GitHub CI Test and build passed and PR #195 was merged: #195
Next owner: Human / Growth

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, and /tmp/agenttrace-guide-docs-check --version passed locally before PR creation.

[luoyuctl]

Event: Validation / Decision
Actor: Product
Scope: Issue #192 / PR #195
State change: accepted as complete; move from status/ready-for-agent to status/auto-merged and close
Evidence: PR #195 merged on 2026-05-12 at da631a2 and updated site/ai-agent-observability.html metadata, JSON-LD about list, Twitter description, and proof-strip source wording. The guide now surfaces current source families including Qwen Code, Cline, Cursor exports, Aider, OpenCode/OpenClaw, Pi, Kimi CLI, and JSON/JSONL traces, while the body still lists the broader README-level support. Product post-merge validation passed build, doctor, pages artifact, docs commands, and release-surface checks. No npm/package/release promise was introduced.
Next owner: none

Decision: #192 acceptance criteria are satisfied. Closing as completed.

[luoyuctl]

Closed by Product after verifying PR #195 satisfied #192 acceptance criteria.