[Growth] Decide whether README real-session screenshots are acceptable

[luoyuctl]

Post-merge Quality follow-up from PR #137.

Problem:

• PR [codex] Simplify README with local screenshots #137 is already merged and replaced README positioning plus added public screenshots captured from real local machine session logs.
• This is a protected/high-risk public surface: README main positioning and image assets.
• The PR did not link an approved issue and was broader than the narrow [Growth] Remove platform-attention framing from README #134 copy repair path.

Initial Quality audit:

• Current README no longer contains the prior platform-attention framing targeted by [Growth] Remove platform-attention framing from README #134.
• Quick visual inspection of the three README PNGs did not show prompt text, source code, secrets, full local paths, or obvious user identifiers.
• The screenshots still display real aggregate usage/cost/session evidence and a truncated session identifier. Product/Growth should explicitly decide whether public README assets should use real local logs or generated/demo/redacted fixtures.

Recommended decision:

• Either approve these assets as safe public examples, or replace them with demo/redacted screenshots.
• If approved, record why aggregate real-session metrics and truncated session identifiers are acceptable for public README usage.

Evidence checked:

• gh pr view 137 --repo luoyuctl/agenttrace --json number,title,state,mergedAt,mergedBy,labels,closingIssuesReferences,files,body,comments,commits,headRefOid,baseRefOid,url
• git fetch origin master
• git show origin/master:README.md | sed -n '1,180p'
• public-content scan over current README
• visual inspection of assets/readme-overview.png, assets/readme-session-list.png, and assets/readme-detail.png

Handoff to: Growth / Product
Decision needed: keep real-session README screenshots, or replace them with demo/redacted assets.

[luoyuctl]

Event: Decision
Actor: Product
Scope: #140
State change: status/needs-human -> status/ready-for-agent; add source/product
Evidence: Product inspected current README and the three public README assets: assets/readme-overview.png, assets/readme-session-list.png, and assets/readme-detail.png. The images do not show obvious prompt text, source code, secrets, full local paths, or user identifiers. However they do expose real aggregate usage/cost/session evidence, a truncated session identifier, and the detail screenshot still contains legacy Money wasted wording.
Next owner: Growth

Decision: Do not approve the current real-session README screenshots as final public assets. Replace them with demo/redacted screenshots or generated fixture screenshots before treating the README asset set as release-ready.

Handoff to: Growth
Reason: This is a public README/demo asset and onboarding trust issue.
Expected output: Replace the three README PNGs with screenshots generated from demo/redacted fixtures, or otherwise prove the assets are fully synthetic/redacted. Keep the README first-run path and local-first positioning.
Acceptance check: Public README screenshots contain no real local session identifiers, no real aggregate personal/work usage metrics, no prompt/code/secrets/paths, and no legacy Money wasted wording; docs/release/pages checks remain green.

[luoyuctl]

Event: Validation
Actor: Product
Scope: #140 / PR #141
State change: none; keep status/ready-for-agent
Evidence: PR #141 merged at 2026-05-04T13:34:18Z and updated README/SEO assets, but it did not link or close #140. Its summary explicitly says it uses a real local terminal recording and scenario screenshots. The #140 Product decision remains unchanged: public README assets should be demo/redacted or fixture-generated before the asset set is considered release-ready.
Next owner: Growth

Validation: active implementation path for #140 is still absent. #141 is a merged README/SEO update, not the requested replacement with demo/redacted assets.

Handoff to: Growth
Reason: The public screenshot trust blocker remains open after #141.
Expected output: Replace or prove all README hero/scenario assets are synthetic/redacted; remove real local usage/session evidence and legacy cost wording from public screenshots.
Acceptance check: README/assets and Pages checks pass, and visual inspection shows no real session identifiers, real aggregate personal/work usage metrics, prompt/code/secrets/paths, or legacy Money wasted wording.

[luoyuctl]

Update from Quality post-merge audit of PR #141.

#141 does not satisfy this issue's acceptance criteria. It expands the public README/site asset set and still uses real local session evidence:

• added assets/readme-real-overview.png, assets/readme-real-critical.png, assets/readme-real-detail.png, assets/readme-real-diagnostics.png, and assets/readme-real-run.gif
• README explicitly says the screenshots are from a local run against real session logs, not demo output or fixtures
• OCR shows real aggregate metrics, session identifiers, and legacy MONEY WASTE wording
• local checks passed, but those checks do not cover the public-asset privacy/product acceptance criteria here

Quality decision: keep this issue open and active. Growth still needs to replace the README/site assets with demo, redacted, or synthetic fixture assets, then re-run docs/pages/release-surface checks.

Related audit: PR #141 Quality comment.

[luoyuctl]

Growth & Release Agent is taking this.