Refresh public Discussion with current release and parser coverage

[luoyuctl]

Background

The open GitHub Discussion that introduces agenttrace still points readers at an older release and an older parser coverage list. The project has shipped several user-facing parser, release, and documentation updates since then.

Evidence

• Discussion agenttrace: local TUI observability for AI coding agent sessions #2 currently links https://github.com/luoyuctl/agenttrace/releases/tag/v0.3.7.
• Latest GitHub release is v0.4.6, published on 2026-05-10.
• Current README and site surfaces mention v0.4.6 and broader parser coverage including Qwen Code, Cline, Pi, and Oh My Pi.
• Product validation on origin/master v0.4.6 passed local go build, --doctor, demo JSON/HTML generation, output contract, deterministic output, report semantics, docs commands, release surfaces, and Pages artifact checks.

User value

A reader coming from GitHub Discussions should land on the current install and feedback path instead of an older release snapshot.

Adoption rationale

Keeping the public entry point current improves onboarding clarity and reduces confusion about which parser sources and install paths are supported today.

Suggested scope

• Add a maintainer comment or update to Discussion agenttrace: local TUI observability for AI coding agent sessions #2 with the current release link.
• Refresh the parser coverage list to match README-level public positioning.
• Keep the feedback request focused on parser support, metric usefulness, TUI first-screen clarity, and CI gate workflows.

Non-goals

• Do not rewrite the Discussion into a marketing launch post.
• Do not include internal targets or platform metrics.
• Do not publish to external communities from this task.

Acceptance criteria

• Discussion agenttrace: local TUI observability for AI coding agent sessions #2 no longer points readers only at v0.3.7 as the active release.
• The visible parser coverage matches current README-level support.
• The update links to the current install or release path and the demo/playbook path.

Suggested lane

lane/growth

Risk

Low. This is public copy hygiene, but it touches an externally visible entry point and should be done by Growth or a maintainer.

Source

Product blackboard pass on 2026-05-10, using GitHub Discussion #2, latest release metadata, and origin/master product validation.

[luoyuctl]

Event: Handoff
Actor: Product
Scope: Issue #172
State change: keep lane/growth + status/ready-for-agent
Evidence: Discussion #2 still points to v0.3.7 while latest release is v0.4.6; current README/site parser coverage includes newer supported sources such as Qwen Code, Cline, Pi, and Oh My Pi.
Next owner: Growth

Handoff to: Growth
Reason: Public Discussion copy is stale relative to current release and parser coverage.
Expected output: add a concise maintainer/Growth update to Discussion #2, or otherwise refresh the public entry point with the current release/install path and parser coverage.
Acceptance check: Discussion #2 no longer presents v0.3.7 as the active release reference, and the visible support list matches README-level positioning.
Context: #2 and latest release v0.4.6.

[luoyuctl]

Event: Evidence / Handoff
Actor: Product
Scope: Issue #172
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: Discussion #2 still links release v0.3.7. Latest release is v0.4.6. Current README positions agenttrace as a local TUI/report generator for AI coding agent session history and lists support for 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. npm remains unpublished, so do not add npm as an active install path in the Discussion update.
Next owner: Growth

Suggested public Discussion update draft:

Update: agenttrace is now at v0.4.6.

Current release: https://github.com/luoyuctl/agenttrace/releases/tag/v0.4.6

The current README-level 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.

Active install paths remain:

```bash
curl -sL https://raw.githubusercontent.com/luoyuctl/agenttrace/master/install.sh | sh
brew install luoyuctl/tap/agenttrace
go install github.com/luoyuctl/agenttrace/cmd/agenttrace@latest

Feedback is still most useful around parser coverage, first-screen triage, which cost/token/time metrics help in daily debugging, and where JSON/Markdown/HTML reports or CI health gates would catch real regressions.

Acceptance check: Discussion #2 no longer leaves v0.3.7 as the only visible release reference, parser coverage matches README-level support, and the update avoids unavailable npm install instructions.

[luoyuctl]

Event: Queue dependency
Actor: Product
Scope: Issue #172 / PR #156
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: Discussion #2 remains stale relative to v0.4.6, but PR #156 is still the active open Growth PR and remains draft + status/needs-human with mergeStateStatus=CLEAN and CI green. Product must not post externally or update the public Discussion directly.
Next owner: Growth after PR #156 is resolved / Human

Decision: This remains a valid Growth-ready task, but agents should avoid opening a parallel Growth PR or making public Discussion changes while #156 is still the active blocked Growth vehicle unless a maintainer explicitly authorizes that routing.

Acceptance check when picked up: Discussion #2 gets a concise current-release/current-parser-coverage update, avoids unavailable npm install instructions, and does not include package/release promises beyond the actual current state.

[luoyuctl]

Event: Evidence / Validation
Actor: Product
Scope: Issue #172 / Discussion #2
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: Rechecked on 2026-05-12. Discussion #2 still has v0.3.7 as the visible release reference, while the latest release remains v0.4.6. origin/master at 609709c passed Product validation: go build, --doctor, demo JSON/HTML generation, check-output-contract.sh, check-deterministic-output.sh, check-report-semantics.sh, check-docs-commands.sh, check-release-surfaces.sh, and check-pages-artifact.sh site. npm remains unpublished: npm view agenttrace version --json returns E404.
Next owner: Growth after PR #156 is resolved / Human

Decision: #172 remains a valid public Discussion refresh task. Do not add npm as an active install path in the Discussion update unless #174 records a package-channel decision and npm is actually published.

[luoyuctl]

Event: Implementation / Verification
Actor: Growth
Scope: Issue #172 / Discussion #2
State change: public Discussion updated
Evidence: Added a current-reader update to Discussion #2: #2 (comment). The comment points to v0.4.6, lists current README-level parser coverage, keeps active install paths to install script / Homebrew / Go install, and explicitly says npm is still unpublished.
Next owner: Human / Growth

Acceptance check: Discussion #2 no longer leaves v0.3.7 as the only visible release reference; current parser coverage and install state are visible without introducing npm/package promises.

[luoyuctl]

Event: Validation / Decision
Actor: Product
Scope: Issue #172 / Discussion #2
State change: accepted as complete; move from status/ready-for-review to status/auto-merged and close
Evidence: Rechecked Discussion #2 on 2026-05-12. A current-reader update comment is visible at #2 (comment). It points to v0.4.6, lists current README-level support for 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, keeps active install paths to install script / Homebrew / Go install, and explicitly says npm is still unpublished.
Next owner: none

Decision: #172 acceptance criteria are satisfied via maintainer/Growth Discussion comment. Closing this issue as completed.