fix(deploy): keep Ever addresses out of the deploy templates (egress audit)

Merged
EV
14d ago
+5-5

The egress audit (tools/egress-audit/static-hostnames.test.mjs, job "egress-audit inputs") fails on integration/issue-triage-2026-10-31. #11580 added Ever addresses to three files that the scan covers but whose baseline records none:

  • .do/deploy.template.yaml: the three demo account addresses (ever.co x3)
  • .env.caddy.sample: the same three (ever.co x3)
  • .github/ISSUE_TEMPLATE/config.yml: the security address (ever.co x1)

The baseline may only shrink, so the comments now point to the places that already list these addresses and are exempt from the scan: README.md for the demo accounts and SECURITY.md for the security address. Only the wording changes; no setting changes.

The other failure on the branch, packages/desktop-ui-lib/src/lib/time-tracker/web-portal/web-portal-url.ts from #11576, is fixed in a separate PR.

Test: node --test tools/egress-audit/static-hostnames.test.mjs no longer reports these three files; only the web-portal file remains, and the other PR handles it.

Refs #9156 #11580. cc @evereq

🤖 Generated with Claude Code


Summary by cubic

Fixes the egress audit failure on integration/issue-triage-2026-10-31 by stopping the deploy templates from naming Ever addresses.

Removes the demo account emails and security contact from comments in .do/deploy.template.yaml, .env.caddy.sample, and .github/ISSUE_TEMPLATE/config.yml, pointing to README.md and SECURITY.md instead — both are exempt from the egress scan. Only comment wording changes; no settings change. The remaining web-portal failure is handled in a separate PR.