You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(tanstack-migrator): per-round merge loop, .deco sync-mirror, deep triage (#513)
* feat(tanstack-migrator): incremental-merge loop + .deco push-mirror + investigative triage
Replace the single-PR + human-merge model with an incremental per-round loop:
opening_pr → reviewing (code-review agent gate) → merging (MCP squash-merge +
branch delete) → deploying → then triaging (first deploy) or paritying (fix
rounds); each fix round cuts a fresh migration/fix-N branch off main and loops
until parity target is hit with an empty backlog. Adds mergePullRequest /
deleteBranch github wrappers and reviewing/merging statuses (plain-TEXT columns,
no migration).
Rework the .deco sync into the proven push-mirror installed on the CLIENT repo
(on:push .deco/** → rsync blocks → -tanstack repo via STOREFRONT_SYNC_TOKEN);
SYNC_DECOFILE_INSTALL opens a PR adding only that one workflow file. Make triage
uncapped + investigative (headless Playwright console capture + skill grep sweep)
and surface the new phases in the widgets/dashboard/stepper.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* feat(tanstack-migrator): wire cross-migration memory into the review phase
The code-review agent now reads framework-notes.md + fixes.md so it can (a) not
block a merge on a KNOWN framework bug and (b) recognize proven fix recipes; it
can also append a new framework-note when a diff reveals a recurring framework
bug. Triage already reads/writes all four memory files, so the new
Playwright/grep sweeps contribute too.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* chore: regenerate registry.json (adds grafana MCP entry)
Fixes the failing `check:registry` CI step — registry.json was out of date
(missing the grafana MCP). Ran `bun run build:registry`; 115 public items.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: registry.json
+49Lines changed: 49 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -2398,6 +2398,55 @@
2398
2398
]
2399
2399
}
2400
2400
},
2401
+
{
2402
+
"id": "deco/grafana",
2403
+
"title": "Grafana",
2404
+
"description": "Query self-hosted Grafana: list datasources, search/read dashboards, and run raw datasource or PromQL queries via /api/ds/query.",
2405
+
"is_public": true,
2406
+
"_meta": {
2407
+
"mcp.mesh": {
2408
+
"verified": false,
2409
+
"friendly_name": "Grafana",
2410
+
"short_description": "Query self-hosted Grafana datasources, dashboards, and PromQL — connect with your Grafana URL + a service-account token.",
2411
+
"owner": "deco",
2412
+
"has_remote": true,
2413
+
"has_oauth": false,
2414
+
"tags": [
2415
+
"grafana",
2416
+
"self-hosted",
2417
+
"observability",
2418
+
"monitoring",
2419
+
"prometheus",
2420
+
"dashboards",
2421
+
"promql",
2422
+
"metrics"
2423
+
],
2424
+
"categories": [
2425
+
"Observability"
2426
+
],
2427
+
"readme": "The Grafana MCP connects AI agents to any self-hosted (or Cloud) Grafana instance over its HTTP API. **Key Features** — **GRAFANA_LIST_DATASOURCES** lists configured datasources (uid/name/type); **GRAFANA_SEARCH_DASHBOARDS** and **GRAFANA_GET_DASHBOARD** discover dashboards and read their full JSON (panels, targets, variables) so agents can learn the exact query a panel uses; **GRAFANA_QUERY** runs any native datasource query through POST /api/ds/query; **GRAFANA_QUERY_PROMETHEUS** is a convenience wrapper for instant or range PromQL. **Use Cases** — pull metrics into agent workflows, reproduce a dashboard panel's query, inspect cost/observability dashboards, and build automations on top of existing Grafana data. **Authentication** — provide your Grafana base URL and a service-account token (Administration → Service accounts → Add token); Viewer role is enough for querying. Ideal for teams running self-hosted Grafana who want programmatic, read-only access to metrics and dashboards without exposing Grafana broadly."
2428
+
}
2429
+
},
2430
+
"server": {
2431
+
"name": "grafana",
2432
+
"title": "Grafana",
2433
+
"description": "Query self-hosted Grafana: list datasources, search/read dashboards, and run raw datasource or PromQL queries via /api/ds/query.",
0 commit comments