Background
After #214 and #217, text overview carries useful Tool authority evidence directly in the terminal. On larger local corpora, the authority summary can become very wide because category counts and high-authority tools are rendered as single lines.
Evidence
Product dogfood on current master d512ec3 using local overview output found several long text overview lines:
- longest measured line: 212 columns
- another authority-related line: 120 columns
- common terminal scan width is closer to 80-120 columns
The wide lines come from compact text overview sections, especially:
Authority category counts: ...High-authority tools: ...
No real prompts, paths, session contents, or secrets are needed to reproduce; the demo and/or a synthetic test can create enough authority categories/tool names to exercise the formatting.
User value
Terminal-first users should be able to scan the text overview without horizontal scrolling or wrapped lines that bury the evidence labels.
Adoption rationale
The first CLI report should feel polished on ordinary terminals. Tool authority is a differentiating report signal, but it loses clarity if the evidence appears as one very long line.
Suggested scope
- Keep text overview authority summary lines bounded and readable.
- Consider limiting displayed authority categories/tools, wrapping continuation lines, or reusing a compact formatter.
- Preserve the existing evidence labels: highest category, authority category counts, and high-authority tools.
- Add a focused regression test with enough authority categories/tool names to prevent a very wide single-line summary from returning.
Non-goals
- Do not change JSON, Markdown, or HTML report contracts.
- Do not change authority classification rules.
- Do not remove authority evidence from text overview.
- Do not touch release, package, npm, Homebrew, or public site surfaces.
Acceptance criteria
- Text overview authority summary remains readable in a normal terminal width.
- A synthetic test or script check prevents unbounded single-line authority output.
- Demo text overview still includes Tool authority, Highest category, Authority category counts, and High-authority tools when data exists.
go test ./..., go build, and report semantics/output checks pass.
Suggested lane
lane/product
Risk
Low to medium. The main risk is hiding too much authority evidence; keep the summary bounded but still useful.
Source
Product dogfood on master d512ec3 after #217.
Background
After #214 and #217, text overview carries useful Tool authority evidence directly in the terminal. On larger local corpora, the authority summary can become very wide because category counts and high-authority tools are rendered as single lines.
Evidence
Product dogfood on current master
d512ec3using local overview output found several long text overview lines:The wide lines come from compact text overview sections, especially:
Authority category counts: ...High-authority tools: ...No real prompts, paths, session contents, or secrets are needed to reproduce; the demo and/or a synthetic test can create enough authority categories/tool names to exercise the formatting.
User value
Terminal-first users should be able to scan the text overview without horizontal scrolling or wrapped lines that bury the evidence labels.
Adoption rationale
The first CLI report should feel polished on ordinary terminals. Tool authority is a differentiating report signal, but it loses clarity if the evidence appears as one very long line.
Suggested scope
Non-goals
Acceptance criteria
go test ./...,go build, and report semantics/output checks pass.Suggested lane
lane/product
Risk
Low to medium. The main risk is hiding too much authority evidence; keep the summary bounded but still useful.
Source
Product dogfood on master
d512ec3after #217.