Description
Owner ruling Q07 (loop58): a causally bound database currently rejects enabling dbo11y on the same database. In a real incident a saturated database shows in its own monitoring (connections, waits, slow queries) when the app slows. Bind the dbo11y lane to the database’s causal resource and lift the restriction.
Acceptance Criteria
- #1 dbo11y connection, wait and slow-query signals for a bound database follow its causal resource state
- #2 Unbound databases and their dbo11y output 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
Compose accepted PostgreSQL and MySQL adapter foundations as local baseline, then wire existing resourceBinder into both dbo configs, remove only blanket bound-dbo rejection, reconcile canonical contracts/authoring skill, and prove real YAML/runner/cloud-plus-dbo coherence and inventory without new scheduler seams or invented wait categories.
Implementation Notes
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.