# Preview dogfood evidence This is maintainer-run operational evidence, not an independent audit or a general reliability claim. It records the acceptance campaign completed on August 14, 2026 before Tend's first public preview. ## Assessed candidate - Source commit: `306d085e518cb4fe7b20a66d1e2ceb171e54ebdc`. - Linux/amd64 candidate binary SHA-256: `a9d53e286317d5acad9c0c321dc8d6240efee1e992714a892aba5be7c190dffc`. - Candidate archive SHA-256: `52639d16cd55b1dfe7c4ce63d4523676a6e8fe7cf57ef25787938c4070f49bd3`. - Toolchain: Go 1.26.6, `CGO_ENABLED=0`, `-trimpath`. - Two fresh packages from the clean pushed commit were byte-identical. - Tests, race tests, vet, license checks, public-snapshot isolation, and `govulncheck v1.1.4` passed. The vulnerability scan reported no known reachable vulnerabilities with the August 14, 2026 database. - Trusted Gitea verification completed successfully for the exact commit. The release tag and attached assets must still identify their own exact source commit and digests. Any code change after this campaign requires the dogfood sequence to be repeated. ## Sandwich Hime website The singleton-candidate strategy packaged and activated website preview 25: - application source commit: `0429e3f0160aa4fd4d262bc5857bc232c2149cb8`; - artifact SHA-256: `25025a05bb1aa6689f5f0779064b24a7c8193ff93c1395a2b3bd342588c3926a`; - application toolchain: Go 1.26.6; - isolated transient candidate passed health, readiness, and application smoke checks before the singleton pointer changed; - explicit rollback returned to preview 24, and the exact approved preview 25 artifact was then reactivated; - canonical, documentation, news, `llms.txt`, and Gamertan-mounted routes returned HTTP 200 after reactivation. ## Gamertan The blue-green strategy packaged and activated Gamertan preview 8: - application source commit: `3acfa6a8e66ca3827c840d1fe9bc0b51c69c0a45`; - artifact SHA-256: `76db7a9a6c496c204f653dc5e42c935272159320cc344b6a4db6374535c696ad`; - application toolchain: Go 1.26.6; - the inactive slot passed health, readiness, and page-marker checks before a validated atomic Caddy handler replacement; - the handler retained `root:caddy` ownership, mode `0640`, and Sandwich Hime routing precedence; - explicit rollback restored preview 7, and the exact approved preview 8 artifact was then reactivated; - homepage, project pages, news, feed, discovery files, the Sandwich Hime mount, and EQL Helper continuity returned HTTP 200 after reactivation. ## Finding resolved during the campaign An earlier rollback attempt stopped safely before changing traffic because it applied the new release's content markers to an older release whose route set was different. Tend now uses the full configured smoke suite for new deployments and health/readiness checks for an already-recorded rollback target. A regression test requires that separation. The fixed candidate then completed both live rollback sequences. ## Boundaries The campaign covered one Linux/systemd/Caddy host and two small Go services. It did not cover databases, migrations, containers, Kubernetes, hostile root, or EQL Helper's application-specific catalog activation. Artifact transport remains an application-owned, host-key-verified step outside Tend v0.1.