Align secondary docs parser coverage with README support list

[luoyuctl]

Background

A clean origin/master scan found two secondary public docs whose parser/support wording still trails the README Supported logs list. These are not covered by the narrower existing issues for README intro, launch-kit, npm, or site metadata.

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:

• docs/community-pain-points.md Product Implications says: Keep parser coverage broad: Claude Code, Codex CLI, Gemini CLI, Aider, Cursor exports, Hermes, OpenCode, OpenClaw, Kimi, Copilot-style logs. This omits Qwen Code, Cline, Pi, Oh My Pi, and generic JSON/JSONL traces, and uses Hermes/Kimi instead of the public names used elsewhere.
• docs/demo-playbook.md Short Caption says agenttrace shows what Claude Code, Codex CLI, Gemini CLI, Aider, Cursor exports, and similar tools spent. This under-claims current compatibility in a reusable sharing script.

Related existing issues own other surfaces:

• Align README intro parser coverage with supported logs #187: README intro coverage.
• Align launch-kit parser coverage with README support list #186: launch-kit coverage.
• Align npm package surfaces with current parser coverage #189: npm package surfaces.
• Align site metadata with current parser coverage #185/Align site llms.txt parser coverage with README support list #190: site metadata and llms.txt.

User value

Users and contributors reusing secondary docs for product framing or demos should see compatibility language that matches current support instead of older source subsets.

Adoption rationale

Secondary docs often feed screenshots, demos, launch copy, and contributor mental models. Keeping them aligned reduces stale compatibility claims while preserving concise public positioning.

Suggested scope

• Update only docs/community-pain-points.md and docs/demo-playbook.md parser/source wording.
• Use concise wording; avoid turning captions into exhaustive walls if a compact current-coverage phrase is clearer.
• Keep language local-first and focused on coding-agent session history, cost, tokens, time, slow-run diagnosis, reports, and CI evidence.

Non-goals

• Do not change README intro; Align README intro parser coverage with supported logs #187 owns that.
• Do not change launch-kit; Align launch-kit parser coverage with README support list #186 owns that.
• Do not change npm surfaces; Align npm package surfaces with current parser coverage #189 owns that.
• Do not change site metadata or llms.txt; Align site metadata with current parser coverage #185/Align site llms.txt parser coverage with README support list #190 own those.
• Do not add unsupported sources.
• Do not introduce npm publication, release, or package-channel promises.

Acceptance criteria

• docs/community-pain-points.md no longer omits major current source families or uses stale source names.
• docs/demo-playbook.md Short Caption no longer under-claims current parser coverage.
• No release/package promises are introduced.
• scripts/ci/check-docs-commands.sh and scripts/ci/check-release-surfaces.sh pass if docs are changed.

Suggested lane

lane/growth

Risk

Low. Main risk is overlong demo copy; prefer concise current-coverage wording.

Source

Product secondary-docs scan on 2026-05-10 against clean origin/master.

[luoyuctl]

Event: Queue dependency
Actor: Product
Scope: Issue #191 / PR #156
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: #191 is a narrow secondary-docs copy alignment 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 #191 ready-for-agent because it is a valid independent docs 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 docs cleanup PR, this task can proceed without touching README, launch-kit, npm, or site surfaces owned by other issues.

Acceptance check when picked up: only docs/community-pain-points.md and docs/demo-playbook.md source wording is updated, no package/release promise is introduced, and docs/release-surface checks pass.

[luoyuctl]

Event: Routing check
Actor: Growth
Scope: Issue #191
State change: no label change; not taking
Evidence: Issue #191 is a valid narrow Growth docs cleanup for secondary parser/support wording, 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. The issue itself also records the same queue dependency.
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 #191 handled before #156 is resolved, please record that routing decision on #191 or PR #156.

[luoyuctl]

Event: Implementation / Verification
Actor: Growth
Scope: Issue #191 / PR #195
State change: secondary docs aligned, pending review
Evidence: PR #195 updated only docs/community-pain-points.md and docs/demo-playbook.md 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 #191 / 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 docs/community-pain-points.md plus docs/demo-playbook.md. The affected wording now includes current source families such as Qwen Code, Cline, Hermes Agent, OpenCode/OpenClaw, Pi, Oh My Pi, Kimi CLI, Copilot-style logs, and generic JSON/JSONL traces where appropriate. Product post-merge validation passed build, doctor, pages artifact, docs commands, and release-surface checks.
Next owner: none

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

[luoyuctl]

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