Add metric-anomaly + incident-followup loops and a GitHub Pages site

[DCCA]

Summary

Applies the next product-level loops and ships a best-in-class GitHub Pages landing site — built in parallel via three subagents, integrated centrally.

New loops (deterministic, turnkey via loopy run)

• metric-anomaly — z-score anomaly detection over an injected metric source; writes a markdown anomaly brief PR (reports/anomalies.md). Source via LOOPY_METRICS_FILE.
• incident-followup — sweeps overdue postmortem action items + clusters incidents by recurring root cause; writes a digest PR (reports/incident-followup.md). Source via LOOPY_INCIDENTS_FILE.

Both wired into the catalog, loopy run, and package exports.

Landing site (site/) + deploy

• Self-contained (no external deps) premium dark landing page: hero + CTA, the loop contract pipeline, a 9-loop grid, 1-click install, an honest "compared to best-in-class" table (vs Dependabot/Renovate, CodeRabbit, Vanta/Drata, Statsig/Eppo), and a long-horizon section.
• .github/workflows/pages.yml deploys site/ to GitHub Pages on push to main.

Note: set the repo's Pages source to GitHub Actions (Settings → Pages) for the deploy to publish — the site + workflow are included regardless.

OpenSpec

Three changes shipped via proposal → apply → archive; specs are the source of truth: metric-anomaly-loop.md, incident-followup-loop.md, landing-page.md.

Validation

• typecheck / lint — clean
• npm test — 126 tests (+15)
• npm run build — clean (dist/loops/metric-anomaly, dist/loops/incident-followup)
• CLI smoke: both loops listed + wired (clear guidance without a data source)

🤖 Generated with Claude Code

https://claude.ai/code/session_012CrMioorha3QtPUgWbtDbR

---

Generated by Claude Code

[DCCA]

Code review

CI green (build success, ~26s); locally typecheck, lint, 126 tests, and build pass. Reviewed the two loops, the CLI wiring, and the site.

Loops

• Deterministic and consistent. Both follow the proven dep-updates/kb-gap shape: injected data source + pure detection + a reports/**-allowlisted PR. metric-anomaly z-scores the latest point vs. its own baseline (skips flat/short series); incident-followup finds overdue open items and root-cause recurrences with deterministic normalization. Fail-safe: nothing found → no PR.
• CLI wiring is clean. File-based sources (LOOPY_METRICS_FILE, LOOPY_INCIDENTS_FILE) mirror the kb-gap pattern; missing source → clear guidance. Catalog + exports updated; smoke-tested.
• Fixed one unused-import lint error from the generated incident-followup loop during integration.

Site

• Self-contained (no CDNs/build), responsive, with an honest comparison table — the caption acknowledges specialists go deeper in their niche, and loopy's angle (one guardrailed, importable framework) is stated fairly. Copy is accurate (OpenRouter z-ai/glm-5.2, the loop contract, all loops). Pages workflow uses the standard Actions deploy.

Notes (non-blocking)

• Pages publish requires the repo's Pages source set to "GitHub Actions" (one-time setting) — documented.
• Anomaly/incident outputs are PR-as-report for now; richer non-PR adapters (alerts/dashboards) remain a noted follow-up.

Recommend merge.

---

Generated by Claude Code