feat(security): add GIT_AUTHOR_EMAIL per agent type #1

Closed
johno wants to merge 2 commits from feat/agent-email-identity into main

2 Commits

Author SHA1 Message Date
7ffb131c84 feat(security): add GIT_AUTHOR_EMAIL per agent type
Some checks failed
Block Internal PRs / Block Internal PRs (pull_request) Failing after 2s
CI / Check for .beads changes (pull_request) Successful in 7s
CI / Check embedded formulas (pull_request) Failing after 11s
CI / Test (pull_request) Failing after 1m37s
CI / Lint (pull_request) Failing after 16s
CI / Integration Tests (pull_request) Successful in 1m37s
Integration Tests / Integration Tests (pull_request) Successful in 1m39s
CI / Coverage Report (pull_request) Has been skipped
Phase 1 of agent security model: Set distinct email addresses for each
agent type to improve audit trail clarity.

Email format:
- Town-level: {role}@gastown.local (mayor, deacon, boot)
- Rig-level: {rig}-{role}@gastown.local (witness, refinery)
- Named agents: {rig}-{role}-{name}@gastown.local (polecat, crew)

This makes git log filtering by agent type trivial and provides a
foundation for per-agent key separation in future phases.

Refs: hq-biot
2026-01-19 14:52:49 -08:00
34c77e883d feat(mayor): add escalation check to startup protocol
Some checks failed
CI / Check for .beads changes (push) Has been skipped
CI / Check embedded formulas (push) Failing after 50s
CI / Test (push) Failing after 1m34s
CI / Lint (push) Failing after 52s
CI / Integration Tests (push) Successful in 1m55s
CI / Coverage Report (push) Has been skipped
Mayor now checks `gt escalate list` between hook and mail checks at startup.
This ensures pending escalations from other agents are handled promptly.

Other roles (witness, refinery, polecat, crew, deacon) are unaffected -
they create escalations but don't handle them at startup.
2026-01-18 23:07:02 -08:00