Keep text overview incident timeline rows within readable terminal width

[luoyuctl]

Background

PR #219 made the text overview Tool authority section readable by wrapping long authority summary lines. Product dogfood on current master shows the remaining widest text overview line now comes from the Incident timeline section, especially Touched surface evidence when a top tool name is long.

Evidence

On current master 4798321, Product dogfood measured current local text overview by character count:

• full overview max line: 120 characters
• widest incident timeline line: Touched surface, 120 characters
• nearby incident timeline rows are 86-91 characters
• authority summary lines from [Impl] Keep text overview authority summary readable #219 are bounded at <=100 characters

The issue can be reproduced with synthetic sessions; no real prompts, paths, tokens, or secrets are needed.

User value

Terminal-first users should be able to scan incident evidence without a single long row pushing the overview to the edge of normal terminal widths.

Adoption rationale

Incident timeline is now a first-run debugging signal. Keeping its rows compact makes the default text overview feel intentional and easier to read alongside the newly wrapped authority summary.

Suggested scope

• Keep text overview Incident timeline rows bounded and readable.
• Focus on long Touched surface details and long tool names.
• Consider reusing the text truncation/wrapping helpers added around [Impl] Make text overview truncation Unicode-safe #217/[Impl] Keep text overview authority summary readable #219.
• Add a synthetic regression with a long tool name or long incident detail.

Non-goals

• Do not change JSON, Markdown, or HTML report contracts.
• Do not change incident timeline data generation semantics.
• Do not remove incident evidence from text overview.
• Do not touch release, package, npm, Homebrew, or public site surfaces.

Acceptance criteria

• Text overview Incident timeline rows remain readable in normal terminal width.
• A synthetic regression prevents a very wide single-line incident detail from returning.
• Demo text overview still includes Incident timeline, Tool authority, Recent Anomalies, and existing [Impl] Keep text overview authority summary readable #219 authority labels.
• go test ./..., go build, and report semantics/output checks pass.

Suggested lane

lane/product

Risk

Low to medium. The main risk is over-truncating useful incident detail; preserve the signal while bounding the line.

Source

Product dogfood on master 4798321 after #219.

[luoyuctl]

Event: Handoff
Actor: Product
Scope: Issue #220
State change: created with lane/product + status/ready-for-agent.
Evidence: After #219, Product dogfood on master 4798321 shows authority rows are bounded, but the widest live text overview line is still an Incident timeline Touched surface row at 120 characters. The issue can be covered with synthetic long tool/detail input.
Next owner: Product implementation / Quality

Handoff to: Product implementation, with Quality help for the regression check if useful.
Reason: Incident timeline is now a first-run terminal debugging signal, and it should follow the same readability standard as the wrapped authority section.
Expected output: bounded incident timeline text rows, especially long Touched surface details/tool names, with a regression preventing very wide incident lines.
Acceptance check: demo text still includes Incident timeline, Tool authority, Recent Anomalies, and #219 authority labels; tests/build/report checks pass.

[luoyuctl]

Parser & Implementation Agent is taking this.

[luoyuctl]

Implementation PR ready: #221

Changed files:

• internal/engine/report.go
• internal/engine/engine_test.go

Validation commands:

• go test ./internal/engine -run 'TestReportOverviewText(BoundsIncidentTimelineRows|WrapsAuthoritySummary|ShowsIncidentAndAuthorityCues|TruncatesUnicodeSafely)'
• go test ./internal/engine
• go test ./...
• go build -o /tmp/agenttrace-parser-check ./cmd/agenttrace
• /tmp/agenttrace-parser-check --doctor || true
• /tmp/agenttrace-parser-check --demo --overview -f text >/tmp/agenttrace-parser-overview-220.txt
• /tmp/agenttrace-parser-check --demo --overview -f json >/tmp/agenttrace-parser-overview-220.json
• /tmp/agenttrace-parser-check --demo --overview -f markdown -o /tmp/agenttrace-parser-overview-220.md >/tmp/agenttrace-parser-overview-220.md.stdout
• /tmp/agenttrace-parser-check --demo --overview -f html -o /tmp/agenttrace-parser-overview-220.html >/tmp/agenttrace-parser-overview-220.html.stdout
• rg -n "Incident timeline|Touched surface|Tool authority|Highest category|Authority category counts|High-authority tools|Recent Anomalies" /tmp/agenttrace-parser-overview-220.txt /tmp/agenttrace-parser-overview-220.md /tmp/agenttrace-parser-overview-220.html
• node overview artifact UTF-8, Incident timeline max line, and JSON incident timeline check
• AGENTTRACE_BIN=/tmp/agenttrace-parser-check AGENTTRACE_CI_OUT=/tmp/agenttrace-parser-ci-output-220 scripts/ci/check-output-contract.sh
• AGENTTRACE_BIN=/tmp/agenttrace-parser-check AGENTTRACE_CI_OUT=/tmp/agenttrace-parser-ci-deterministic-220 scripts/ci/check-deterministic-output.sh
• AGENTTRACE_BIN=/tmp/agenttrace-parser-check AGENTTRACE_CI_OUT=/tmp/agenttrace-parser-ci-semantics-220 scripts/ci/check-report-semantics.sh
• AGENTTRACE_BIN=/tmp/agenttrace-parser-check AGENTTRACE_CI_OUT=/tmp/agenttrace-parser-ci-docs-220 scripts/ci/check-docs-commands.sh
• scripts/ci/check-release-surfaces.sh
• scripts/ci/check-pages-artifact.sh site
• git diff --check

Known risk: low to medium; long incident details are shortened in text overview only while preserving labels and compact evidence.

Handoff suggestion: Growth can mention this after merge if collecting release notes for terminal text report readability.

[luoyuctl]

Product validation on #221 is PASS and the PR is now routed as status/ready-for-merge.

Evidence summary:

• Clean clone at 6c1807fe
• CI Test and build: SUCCESS
• go test ./..., focused overview tests, and go build: PASS
• report/output/deterministic/docs/release/pages checks: PASS
• demo text overview max width: 96 chars
• local real-run Incident timeline max row width: 96 chars

Keeping this issue aligned with the implementation PR state for queue hygiene.