# The boring checks that keep public AI portfolios credible

> Day 13 of the AI Agent Field Notes traffic experiment.

Format: Debug Autopsy
Target reader: Engineers publishing generated pages, PDFs, and machine-readable agent files.
Primary channel: LinkedIn
Secondary channel: X
Canonical URL: https://zack-dev-cm.github.io/docs/field-notes/security-link-and-public-bleed-checks.md

## Reader Win
A compact validation stack for links, leak scans, SEO/AEO checks, and Playwright smoke tests.

## Evidence To Use
validate, build, security gate, link check, audit, and E2E checks.

## Thumbnail Direction
Terminal output checklist with pass states and one generated page preview.

## Writer Brief
Show the public value of validation. Keep command output short and focused.

## Call To Action
Inspect the generated public files

## Public-Surface Rules
- Use real screenshots, generated public files, or dated public marketplace data as evidence.
- Do not include credentials, private account identifiers, unpublished analytics, or client-specific operational details.
- Treat marketplace downloads as listing-download evidence, not user-count proof.