Residual spec coverage from #420: 2 unmet acceptance criteria
Residual spec coverage (auto-filed by the spec-coverage gate #9914)
The workflow for #420 (closed) landed and merged its primary mechanism, but the spec-coverage gate (#8930) flagged a partial delivery: 1/1 of the integration points named in the parent were addressed and 1/3 of its acceptance criteria were delivered. The parent has been closed per the issue-lifecycle policy; this follow-on tracks the remaining scope so it is not silently dropped.
Parent issue: #420 (closed)
Landing workflow: 420-shared-hivemind-provider-s-pg-saa8f95d9-v1
Scored change: a751721dc9fb2affc5682aa0ff22effde408f539..4e7b19a8c20e7de196a047085437a82a746240b0
Landing merge: 242cd0a55f4e95f66990e7e28a717f43593db1da (where the scored change was integrated; it need not carry the scored diff)
Unmet acceptance criteria
- Under the updated
PG_ACCESS, a connection tohivemind_sharedashivemind_shared_consumerfrom source100.64.0.10is accepted, and from an address outside every listed range is still refused. - Under the updated provider, the
fullgate'stavernstep run from a Polish fleet host connects to the provider and its groups run (any test failures are reported as test failures, not a pg_hba refusal).
Each is stated in the parent's acceptance section, and no file the landed change touched plausibly delivers it.
The gate does not distinguish deliberately-deferred from missed — verify each is still needed, then implement it or close this issue with a rationale.
Refs #9050, #8930, #15599.
Part-Of: #420 (closed)