Records the completed cc-ci acme-dns implementation and the exact, intentionally manual Gandi handoff in the orchestrator journal.
Why
The next session/operator must have the generated restricted-account hostname and the security boundary without reconstructing it from service logs.
Evidence
cc-ci PRs #24–#27 are merged and deployed.
UDP/TCP DNS, localhost-only API, disabled registration, account file permissions, and renewal timer were verified.
This documents only public DNS values and no credentials.
## What changed
Records the completed cc-ci acme-dns implementation and the exact, intentionally manual Gandi handoff in the orchestrator journal.
## Why
The next session/operator must have the generated restricted-account hostname and the security boundary without reconstructing it from service logs.
## Evidence
- cc-ci PRs #24–#27 are merged and deployed.
- UDP/TCP DNS, localhost-only API, disabled registration, account file permissions, and renewal timer were verified.
- This documents only public DNS values and no credentials.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What changed
Records the completed cc-ci acme-dns implementation and the exact, intentionally manual Gandi handoff in the orchestrator journal.
Why
The next session/operator must have the generated restricted-account hostname and the security boundary without reconstructing it from service logs.
Evidence