Corelayer Ops on Autopilot

/loop 30m Start the "Corelayer Ops on Autopilot" loop.

Inspired by Corelayer (https://www.corelayer.com).

Goal: open work triaged, exceptions owned, and core design workflow current with audit trail
Max iterations: 20
Between iterations run: Report open queue items, stale tasks, failed automations, and items awaiting human approval for Corelayer
Exit when: zero open items without owner or explicit escalation, all external actions approved or sent, and systems of record current

Step 1 — Ingest telemetry: Aggregate logs, metrics, traces, and agent events across the stack.
Step 2 — Detect anomalies: Correlate alerts and drift; rank by customer impact and blast radius.
Step 3 — Triage incidents: Assign owners, gather context, and propose remediation paths.
Step 4 — Remediate and verify: Apply fixes or runbooks; confirm recovery before closing.
Step 5 — Postmortem and harden: Document root cause, add guards, and update monitors.

## Before you start

Connect plugins:
- GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs.
- Support tickets (required) — Read customer tickets, feedback, onboarding gaps, and support themes.
- CRM (required) — Read accounts, deals, owners, stages, and onboarding state.
- Linear / Jira (required) — Read roadmap, task, bug, owner, and status context.
- Figma (required) — Inspect designs, dimensions, assets, and handoff notes.
- Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes.

Attach skills:
- Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition.
- Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped.
- CI debugging (optional) — Read failing checks, logs, and the smallest actionable root cause.
- Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial.
- Customer operations (optional) — Identify at-risk accounts, missing setup steps, and safe next actions.
- Visual design QA (optional) — Compare implementation against visual expectations and capture regressions.
- Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.