[RedStar071]

Summary

Related to #5. A presentation pass on the marketing home, on top of #71. Copy stays in packages/i18n, and the page keeps the shared tokens.

• The hero leads with what the product does ("Find the problem. Prove the fix.") and with observe mode as the safe start. The terminal is labelled as an illustrative excerpt, not a recorded run, and its command is one the CLI actually accepts (zero review --proactive). The social image had the old --mode flag and is fixed too.
• The testimonials section is gone. The three quotes named people and companies nothing in the project can back up.
• The feature grid uses typed layout slots (lead, standard, wide) instead of ids and icons, and the logo strip reads as a sentence plus a row.
• Controls on the page are 44 px tall (h-11), which matches the marketing density in packages/ui/DESIGN.md.
• A header test that clicked an external link now prevents the navigation, so the suite never opens a real URL.

Why

The home made claims the repository could not support: invented customer quotes and a CLI flag that no longer exists. Removing them and labelling the demo output keeps the page honest for a project whose pitch is "backed by evidence".

Verification

• aube run check:repo
• aube run lint:ci
• aube run typecheck
• aube test
• aube run build

Safety and compatibility

• I added or updated deterministic tests for changed behavior.
• I preserved observe mode as read-only, or explained the policy change above.
• Runtime commands and target-repository writes remain inside the runner boundary.
• I did not expose secrets, tokens, personal data, or untrusted output in logs.
• I updated documentation and Agent Skills when workflows or boundaries changed.

Marketing only: no runtime, auth or data change.

Agent context

• Agent/tools used: Codex (GPT) and Claude Code (Claude Opus 5.5) in T3 Code, with a review subagent, following the Wolfstar Agent Kit design skills.
• What the agent did, and what you changed or verified yourself: the agents reworked the home, removed the testimonials, reviewed the result, and checked a production build in Chromium on the home, Italian home, pricing, contact, blog and changelog pages at 375, 768 and 1280 px in both themes. I asked for a dedicated marketing pass.

Reviewer notes

• The hero terminal ends with "No finding was produced". It is honest for an illustrative observe run, but it sits next to "Find the problem". Happy to swap in an excerpt that shows a finding.
• Two controls this PR does not touch are below 44 px: the monthly/yearly switch on pricing (36 px) and the blog tag filters (32 px). Both clear the 24 px WCAG AA minimum.
• The blog still lists sample authors. They were left alone here.

🤖 AI disclosure: Wolfstar Agent Kit modified this description. My AI open-source policy.

Confidence Score: 5/5

The reviewed changes are safe to merge; no actionable issues remain.

_{Reviews (1) · Last reviewed commit: "feat(marketing): lead with evidence and ..." · Reviewed by Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
agent-zero-marketing	Ready	Preview	Oct 18, 2026 8:40pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
agent-zero-docs	Skipped		Oct 18, 2026 8:40pm UTC

[coldtea-pr-lens]

Architecture

Inside the changed components — 1 view

Component view — Marketing page components

Internal breakdown of changed marketing sections and layout structures.

Data flow

No data-flow sequence changed in this PR.

Review

✨ Nothing flagged · reviewed 8548bb6

Tip

Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture and data flow row. Drawing still runs as before

🪧 More tips

• Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
• Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists
• Click the link under each diagram to open it on a canvas you can zoom, pan and step through
• The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change
• Open a diagram on the canvas, then press W or click play to walk through the change one step at a time
• The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time
• Set github.draw: on-demand in .github/pr-lens.yml and PR Lens stops drawing pull requests on its own. Comment @pr-lens draw on a pull request when you want that one drawn
• Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works
• After a push, tick Redraw to draw the latest commit
• Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion

_{Thanks for using PR Lens! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out on X, Bluesky, Mastodon, Reddit or LinkedIn}