fix(#975): use hyperhive.local email domain to pass Forgejo validation

`@hyperhive` (no dot) is rejected by Forgejo's PATCH /admin/users API
with 422 Unprocessable Entity. Switch to `@hyperhive.local` across all
four files that construct hive-c0re/agent git emails and Forgejo account
emails, so both stay in sync and pass RFC-valid domain validation.
This commit is contained in:
atlas 2026-06-01 18:28:22 +02:00
commit 286a7c8fd3
4 changed files with 7 additions and 7 deletions

View file

@ -15,7 +15,7 @@ use crate::lifecycle;
const META_ROOT: &str = "/var/lib/hyperhive/meta";
const APPLIED_ROOT: &str = "/var/lib/hyperhive/applied";
const GIT_NAME: &str = "c0re";
const GIT_EMAIL: &str = "c0re@hyperhive";
const GIT_EMAIL: &str = "c0re@hyperhive.local";
/// Single-writer lock around every meta-repo operation. Git isn't
/// safe to drive from concurrent processes against the same `.git/`
@ -468,7 +468,7 @@ where
hyperhive.user.name = name;
programs.git.config.user = {
name = name;
email = "${name}@hyperhive";
email = "${name}@hyperhive.local";
};
# Container-wide env: every service + co-process daemon can
# resolve the agent's durable state dir without hard-coding it.