Evidence

Battle tested

Web Fleet records the limits of its verification alongside the features it claims.

What is exercised

• Normal, race-enabled and cross-platform Go build suites.
• First-run authentication, site management, keyboard navigation and 320px overflow checks in a real browser.
• Monitoring, TLS, DNS, crawling, broken-link provenance, analytics validation and webhook delivery.
• SQLite and PostgreSQL backup paths, service lifecycle transactions, signed release archives and update or rollback rehearsals.
• Scale measurements at 100, 1,000 and 10,000 sites.

What it does not prove

These checks are engineering evidence, not an external security audit or a universal capacity promise. Operators should rehearse backup restoration, HTTPS proxying and upgrades in their own environment.

Reproduce the checks

go test ./...
go test -race ./...
go vet ./...
./scripts/verify-release.sh ./dist

See the project HANDOVER.md, SCALE.md and release limitations for the exact evidence attached to a checkout.