Description
The private demo’s alert rules should route through the demo stack’s on-call and incident tooling: an integration, an escalation chain, a schedule and incident declaration, with chat notifications once the owner connects the chat app. Every object is private, marked illustrative and read back after apply.
Acceptance Criteria
- #1 The private packet’s alert rules route to an on-call integration and escalation chain on the demo stack, read back
- #2 A firing demo scenario opens an incident visible in the incident tooling, with chat notification once the owner’s chat connection exists
- #3 Every object is titled illustrative and nothing private lands in the public repository
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
Loop55: author private offline routing specification and review; root introspects and serially applies to the authorized destination, read back, then unpause only routed rules. Chat remains contingent on the owner connection.
Implementation Notes
Created and read back the illustrative unattached escalation chain and bearer-protected intake integration using existing service-account authority. No human responder exists in observed on-call users. The integration remains unconnected: no contact point, notification-policy linkage, test send, incident creation or alert activation. A default messenger enable flag exists without a channel identifier; delivery is not admitted from that alone. UI initialization also invokes managed credential-refresh endpoints, which remain blocked pending owner-controlled bootstrap or explicit scope. Sensitive ingress material is held only in the central credential inventory.
Closeout: owner-decision deadline expired without channel or human-bootstrap approval. Keep known-created inert chain and bearer intake, but no contact point, policy linkage, schedule coverage, notification, incident or unpause. Resume after owner-controlled human bootstrap, explicit channel and actual binding/coverage readback; no managed credential refresh or personal notification changes inferred.