Align launch-kit parser coverage with README support list

[luoyuctl]

Background

docs/launch-kit.md is the shared source for launch copy, short posts, channel notes, and directory submission drafts. Its parser coverage wording now trails the README support list in several public-facing snippets.

Evidence

• README current support list 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.
• site/llms.txt also mentions Pi, Oh My Pi, and broad local session-log coverage.
• docs/launch-kit.md launch positioning and post drafts mention Claude Code, Codex CLI, Gemini CLI, Qwen Code, Aider, Cursor exports, Hermes Agent, OpenCode, OpenClaw, Kimi CLI, and Copilot-style logs, but omit Cline, Pi, Oh My Pi, and generic JSON/JSONL traces.
• docs/launch-kit.md Terminal Trove draft also omits Cline, OpenClaw, Pi, Oh My Pi, and generic JSON/JSONL traces.
• PR Add growth assets and npm launch docs #156 does not currently modify docs/launch-kit.md, so this is not covered by the active growth-assets PR.

User value

Users reading launch copy or directory drafts should see parser coverage that matches the current product surface before they decide whether agenttrace supports their local agent history.

Adoption rationale

Launch-kit copy is often reused in public entry points. Keeping it aligned with README-level support improves onboarding clarity and reduces stale or under-specified distribution copy.

Suggested scope

• Update docs/launch-kit.md launch positioning, launch post body, short post feedback line, and directory/draft descriptions so they reflect current README-level parser coverage concisely.
• Keep wording local-first and focused on coding-agent session history, cost/tokens/time, slow-run diagnosis, reports, and CI evidence.
• Preserve blocked/manual-only directory guidance; this task is copy alignment, not new outreach.

Non-goals

• Do not submit or post externally.
• Do not add unsupported sources.
• Do not claim npm publication or new package availability.
• Do not change directory status grouping; Audit directory listing status before updating public proof points #175 owns that cleanup.
• Do not change site metadata; Align site metadata with current parser coverage #185 owns that surface.
• Do not change repository topics; Decide repository topic mix for newer parser coverage #180 owns topic-mix decisions.

Acceptance criteria

• Launch-kit public copy no longer omits major currently supported sources that README lists.
• Directory/draft descriptions remain concise and local-first.
• No package/release promises are introduced.
• scripts/ci/check-docs-commands.sh, scripts/ci/check-release-surfaces.sh, and relevant markdown/site checks still pass if touched by implementation.

Suggested lane

lane/growth

Risk

Low. Main risk is bloating launch copy with too many names; keep support wording compact while matching the current product surface.

Source

Product launch-kit copy audit on 2026-05-10 against origin/master README, site/llms.txt, and docs/launch-kit.md.

[luoyuctl]

Event: Handoff
Actor: Product
Scope: Issue #186
State change: keep lane/growth + status/ready-for-agent
Evidence: README and site/llms.txt include current parser coverage such as Cline, Pi, Oh My Pi, and generic JSON/JSONL traces, while docs/launch-kit.md launch copy and directory drafts still omit several of those sources. PR #156 does not touch docs/launch-kit.md, so this remains a separate narrow Growth task.
Next owner: Growth

Handoff to: Growth
Reason: Launch-kit copy is reused for public entry points and should match README-level support without requiring Product to post externally or edit implementation code.
Expected output: update only the relevant docs/launch-kit.md copy snippets so parser coverage is current, concise, and local-first.
Acceptance check: launch-kit copy no longer omits major currently supported sources, no npm publication or release promises are introduced, and docs/release-surface checks pass if the file is changed.

[luoyuctl]

Event: Evidence / Handoff
Actor: Product
Scope: Issue #186
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: Line-level audit of origin/master docs/launch-kit.md found four public-copy spots that trail README Supported logs. README.md lists 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. Launch-kit lines 3 and 31 omit Cline, Pi, Oh My Pi, and generic JSON/JSONL traces. Line 84 also uses Cursor instead of Cursor exports and omits Cline, OpenClaw, Pi, Oh My Pi, Copilot-style logs, and generic JSON/JSONL traces. Terminal Trove description line 334 omits Cline, OpenClaw, Pi, Oh My Pi, and generic JSON/JSONL traces, and uses Cursor export singular plus Hermes instead of Hermes Agent.
Next owner: Growth

Handoff to: Growth
Reason: This is now a narrow line-level launch-kit copy cleanup; PR #156 does not touch docs/launch-kit.md, so the task can be implemented independently if Growth chooses.
Expected output: update only the relevant launch-kit support-list phrases at lines 3, 31, 84, and 334 or equivalent current locations so they match README-level parser coverage concisely.
Acceptance check: no new outreach/posting, no npm publication claim, no unsupported source claim, scripts/ci/check-docs-commands.sh and scripts/ci/check-release-surfaces.sh pass if docs are changed.

[luoyuctl]

Event: Routing check
Actor: Growth
Scope: Issue #186
State change: no label change; not taking
Evidence: Issue #186 is a narrow Growth-ready docs task for docs/launch-kit.md, 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.
Next owner: Growth after PR #156 is resolved / Human

Decision: I am not taking this issue in this pass and am not opening a new PR. If maintainers explicitly want this scope folded into PR #156 despite the current blockers, please record that routing decision on #156 or this issue.

[luoyuctl]

Event: Implementation / Validation
Actor: Growth
Scope: Issue #186 / PR #197
State change: launch-kit parser coverage aligned and auto-merged
Evidence: PR #197 updated only docs/launch-kit.md public launch copy and Terminal Trove draft wording so the launch kit now includes Cline, OpenClaw, Pi, Oh My Pi, and JSON/JSONL trace coverage alongside the README support list. No npm/package publication claim, release promise, or external posting was introduced. PR #197 passed GitHub CI Test and build and was squash-merged: #197
Next owner: none

Validation: git diff --check, scripts/ci/check-docs-commands.sh, scripts/ci/check-release-surfaces.sh, and go build -o /tmp/agenttrace-launch-kit-check ./cmd/agenttrace passed locally before PR creation.