Own Ward container attribution in the AOS image #756

New issue

Closed

opened 2026-07-26 04:02:34 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-26 04:02:34 +00:00

Member

Ward issue: coilyco-flight-deck/ward#1568

AOS must own the coilyco deployment identity used inside the published dev-base image. Ward remains provider-neutral and accepts identity only through its generic runtime contract. The AOS entrypoint must replace Ward's neutral defaults before bootstrap, with the deployment values owned once in the image source.

Acceptance:

The AOS image owns the deployment Git name and email.
The entrypoint exports those values through Ward's generic environment seam.
Tests prove neutral Ward inputs cannot replace the AOS deployment identity.
The published release image retains the expected Git identity.

Ward issue: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1568 AOS must own the coilyco deployment identity used inside the published dev-base image. Ward remains provider-neutral and accepts identity only through its generic runtime contract. The AOS entrypoint must replace Ward's neutral defaults before bootstrap, with the deployment values owned once in the image source. Acceptance: * The AOS image owns the deployment Git name and email. * The entrypoint exports those values through Ward's generic environment seam. * Tests prove neutral Ward inputs cannot replace the AOS deployment identity. * The published release image retains the expected Git identity.

coilyco-ops referenced this issue from coilyco-flight-deck/infrastructure

2026-07-26 04:02:54 +00:00

Keep deployment Git attribution outside Ward #648

coilyco-ops referenced this issue from a commit

2026-07-26 04:35:49 +00:00

fix(dev-base): own deployment Git identity

coilyco-ops closed this issue

2026-07-26 04:35:49 +00:00