Description
A bound PostgreSQL database currently cannot emit its database-observability lane; the lane must agree with its cloud monitoring through independently compiled deterministic resource state.
Acceptance Criteria
- #1 PostgreSQL connection readings and query/wait duration output follow declared causal pool/dependency state without inventing wait causes
- #2 Unbound output, native fields, timestamps and metric-log query joins remain unchanged
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Implementation Plan
Use the mapped existing binding/consumer/advancer interfaces, snapshot the trailing minute once per tick, adapt metrics and logs coherently, and return loader/schema/documentation hunks for root integration.
Implementation Notes
Unpublished standalone foundation: source/generated tree c0fdeba2 passed full gate; board-merged26941150 later failed an unchanged custody forecast test. Both bounded focused base/candidate diagnostics pass, with no original-failure attribution. Do not call that red cleared. Fold this accepted adapter into a genuinely new database/scope candidate that must receive its own full exact-tree gate before publication.
Published through dac0d2b4139b5fc851a49f2b16c77a5dadd15421 after exact-tree full gate 20261025T211422Z-synthkit-1a23af00, complete review, generation and selected database CLI inventory/conformance. Hosted CI on that SHA remains failed on architecture-scoped unbound digest expectations and separate kubeconform download reset. Actual pre-change/candidate captures establish unchanged output per architecture; unlanded repair tracked separately. Source delivery is not hosted-CI or deployment clearance.