Problem
The existing flow is asymmetric: during enrollment, the agent connects to the supervisor and receives the supervisor’s certificate, so the agent can later push results back securely.
The missing trust is in the opposite direction: the supervisor did not receive the agent sidecar’s certificate. An HTTPS Git-agent sidecar generates a self-signed certificate when --tls-cert and --tls-key are omitted.
Publicly trusted ingress endpoints work and should continue using normal hostname verification without a renewal-sensitive pin.
Context
Discovered while reviewing PR #102: #102 (comment)
The underlying direct-HTTPS transport behavior predates caller-tool delegation, so it is tracked separately from issue #83.
Problem
The existing flow is asymmetric: during enrollment, the agent connects to the supervisor and receives the supervisor’s certificate, so the agent can later push results back securely.
The missing trust is in the opposite direction: the supervisor did not receive the agent sidecar’s certificate. An HTTPS Git-agent sidecar generates a self-signed certificate when
--tls-certand--tls-keyare omitted.Publicly trusted ingress endpoints work and should continue using normal hostname verification without a renewal-sensitive pin.
Context
Discovered while reviewing PR #102: #102 (comment)
The underlying direct-HTTPS transport behavior predates caller-tool delegation, so it is tracked separately from issue #83.