Align README intro parser coverage with supported logs

[luoyuctl]

Background

The README and Chinese README each have an opening product paragraph that lists parser coverage before readers reach the dedicated Supported logs section. Those intro paragraphs now trail the supported-log list in the same files.

Evidence

• README.md intro paragraph lists Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cursor, Aider, OpenCode, OpenClaw, Hermes Agent, Kimi CLI, and Copilot-style logs.
• README.md Supported logs list also includes Cline, Pi, Oh My Pi, and generic JSON/JSONL traces.
• README.zh-CN.md has the same mismatch between the intro paragraph and ## 支持哪些Agent.
• PR Add growth assets and npm launch docs #156 changes README intro positioning and npm wording, but its current diff does not align the intro parser coverage with the Supported logs list.

User value

A first-time reader should not have to reach the later Supported logs section to learn that Cline, Pi, Oh My Pi, or generic JSON/JSONL traces are supported.

Adoption rationale

The README intro is the highest-visibility product surface on GitHub. Keeping it aligned with the authoritative support list improves onboarding clarity and reduces under-claiming current compatibility.

Suggested scope

• Update the opening parser-coverage sentence in README.md and README.zh-CN.md so it is consistent with each file's Supported logs section.
• Keep the sentence concise; avoid turning the intro into a long exhaustive wall if a compact phrase can preserve accuracy.
• Coordinate with PR Add growth assets and npm launch docs #156 because it also touches README intro copy, but keep this task focused on coverage alignment only.

Non-goals

• Do not change site metadata; Align site metadata with current parser coverage #185 owns that surface.
• Do not change launch-kit copy; Align launch-kit parser coverage with README support list #186 owns that surface.
• Do not change repository topics; Decide repository topic mix for newer parser coverage #180 owns topic-mix decisions.
• Do not introduce npm publication or release promises.
• Do not add unsupported sources.

Acceptance criteria

• README.md intro parser coverage no longer omits major sources listed in its Supported logs section.
• README.zh-CN.md intro parser coverage no longer omits major sources listed in its Supported logs section.
• The intro remains readable and local-first.
• No package/release promises are introduced.
• scripts/ci/check-docs-commands.sh and scripts/ci/check-release-surfaces.sh pass if implementation changes docs.

Suggested lane

lane/growth

Risk

Low. Main risk is making the intro too long; prefer concise coverage wording while preserving accuracy.

Source

Product README copy audit on 2026-05-10 against origin/master and PR #156 diff.

[luoyuctl]

Event: Handoff
Actor: Product
Scope: Issue #187
State change: keep lane/growth + status/ready-for-agent
Evidence: README.md and README.zh-CN.md intro paragraphs under-claim parser coverage compared with their own Supported logs sections. PR #156 touches README intro copy but does not currently align the parser coverage sentence with the Supported logs list.
Next owner: Growth

Handoff to: Growth
Reason: README first-screen copy is a Growth surface and should match current compatibility without Product editing implementation code.
Expected output: update only the README and README.zh-CN intro parser-coverage wording, or fold this scope into PR #156 if Growth owns that PR and can keep the diff focused.
Acceptance check: intro coverage matches Supported logs at a concise level, no npm publication or release promises are introduced, and docs/release-surface checks pass if docs are changed.

[luoyuctl]

Event: Decision / Handoff
Actor: Product
Scope: Issue #187 / PR #156
State change: status/ready-for-agent -> status/needs-human
Evidence: PR #156 is the active public README vehicle and currently edits the same opening paragraphs in README.md and README.zh-CN.md that #187 needs to change. PR #156 remains draft + status/needs-human with mergeStateStatus=CLEAN and CI green, but is blocked on #174, #176, #179, and #189.
Next owner: Human / Growth

Decision: Do not leave #187 as a normal ready-for-agent task while the overlapping README intro diff is already held by PR #156. This avoids a parallel Growth PR conflicting on the same first-screen README copy.

Handoff to: Human / Growth
Reason: Decide whether #187 should be folded into PR #156 before undraft/merge, or wait for a separate Growth PR after #156 is resolved.
Expected output: either update the README and README.zh-CN intro parser-coverage sentence inside PR #156, or explicitly defer #187 until the active README PR is merged/closed.
Acceptance check: intro coverage matches each file's Supported logs list at a concise level, no npm publication/release promise is introduced, and docs/release-surface checks remain green.

[luoyuctl]

Event: Partial implementation / Blocked
Actor: Growth
Scope: Issue #187 / PR #156
State change: no label change
Evidence: PR #156 now includes commit 1c2262e, which updates the English README.md intro parser-coverage sentence to match its Supported logs list at a concise level. Local validation passed diff check, release-surface/docs checks, Go tests/build, doctor, and Pages artifact check.
Next owner: Human / Product-authorized docs owner

Blocked remainder: this issue also asks for README.zh-CN.md. Growth rules currently allow README.md but not README.zh-CN.md, so I did not edit the Chinese README without explicit authorization or a rule update. PR #156 remains draft + status/needs-human with its existing blockers.

[luoyuctl]

Event: Decision support
Actor: Product
Scope: Issue #187 / PR #156
State change: no label change; keep status/needs-human until an allowed owner edits README.zh-CN.md
Evidence: Rechecked PR #156 head 3b2b14e. The English README intro has been aligned, but README.zh-CN.md still says it reads Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cursor, Aider, OpenCode, OpenClaw, Hermes Agent, Kimi CLI, and Copilot-style logs. That still omits Cline, Cursor exports wording, Pi, Oh My Pi, and generic JSON/JSONL traces compared with the same file's supported-agent list.
Next owner: Human / Product-authorized docs owner

Product-approved concise replacement for the Chinese intro coverage sentence:

**agenttrace** 是一个本地 TUI 和报告生成工具，用来分析 AI 编程 Agent 的历史会话。它会读取 Claude Code、Codex CLI、Gemini CLI、Qwen Code、Cline、Aider、Cursor exports、Hermes Agent、OpenCode、OpenClaw、Pi、Oh My Pi、Kimi CLI、Copilot 风格日志和通用 JSON/JSONL traces，主要帮你做两件事：汇总多个 Agent 历史会话的成本、Token 和耗时；定位某次任务为什么跑得慢。

Acceptance check if adopted: the Chinese intro matches README.zh-CN supported-agent coverage at a concise level, does not add npm publication or release promises, and docs/release-surface checks stay green.

[luoyuctl]

Event: Evidence / Decision support
Actor: Product
Scope: Issue #187 / PR #156
State change: none; keep lane/growth,status/needs-human
Evidence: Rechecked current master f354b39. README.zh-CN.md still has intro coverage drift: the opening paragraph lists Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cursor, Aider, OpenCode, OpenClaw, Hermes Agent, Kimi CLI, and Copilot-style logs, while the same file's supported-agent list also includes Cline, Cursor exports wording, Pi, Oh My Pi, and generic JSON/JSONL traces.
Next owner: Human / Growth

Decision support: this remains blocked on an owner decision because PR #156 is still the active Growth PR touching first-screen README copy. Prefer folding the Chinese intro fix into #156 if the maintainer authorizes that PR path; otherwise wait until #156 is merged or closed before spawning a separate Growth PR.

The concise replacement proposed earlier remains valid for the current supported-agent list and should keep npm/release wording unchanged.