@debugbundle/cli 1.5.0 → 1.5.1

package/dist/main.cjs

@@ -15944,8 +15944,10 @@ function buildSkill() {
     "name: debugbundle",
     "description: >-",
     "  Investigate runtime incidents, inspect debug bundles, generate reproductions,",
-    "  and run improvement analysis using the DebugBundle CLI and local project scaffold.",
-    "  Use when the user reports a bug, runtime failure, or asks about production incidents.",
+    "  run improvement analysis, and inspect operational controls using the DebugBundle",
+    "  CLI and local project scaffold. Use when the user reports a bug, runtime",
+    "  failure, production incident, endpoint downtime, health-check issue, missing",
+    "  notification, webhook delivery failure, probe request, or noisy incident.",
     "metadata:",
     "  author: debugbundle",
     '  version: "1.0"',
@@ -15983,6 +15985,24 @@ function buildSkill() {
     "4. Apply the narrowest fix, then validate it with the repository test workflow from `.debugbundle/profile.json`.",
     "5. When the fix is confirmed, or when the incident was intentionally generated for smoke, verification, or dogfooding, resolve it with `debugbundle resolve <incident-id> [incident-id ...]` or MCP `resolve_incident` / `resolve_incidents` so the open queue stays actionable.",
     "",
+    "## Investigation Controls",
+    "",
+    "Use these controls when the user's issue is about observability behavior, notification delivery, targeted evidence gathering, or event noise rather than only application code.",
+    "",
+    "- Availability checks: use hosted health checks for endpoint downtime, public reachability, or project Health tab issues. These are DebugBundle-run external `GET`/`HEAD` checks, not SDK events from the customer app.",
+    "- Probes: inspect active probes with `debugbundle probe list <project-id> --json` or MCP `list_active_probes` before activating more probes. Activate probes only when targeted runtime evidence is needed and the user has asked for investigation.",
+    "- Capture policy and rules: inspect policy/rules before suppressing noisy incidents. Prefer `debugbundle capture-rule suggest <incident-id> --json` and narrow capture-policy path rules over broad drops or demotions.",
+    "- Alerts and webhooks: when the user reports missing, duplicate, or failed notifications, inspect alert config, webhook config, and webhook delivery history before changing application code.",
+    "",
+    "## Availability Checks",
+    "",
+    "- Start with `debugbundle health checks list --project-id <id> --json` or MCP `list_health_checks` to inspect saved checks and plan limits.",
+    "- For a failing check, inspect `debugbundle health checks results <check-id> --project-id <id> --json` and `debugbundle health checks daily-rollups <check-id> --project-id <id> --json` before changing code.",
+    "- Use `debugbundle health checks test --project-id <id> --url <url> --json` or MCP `test_health_check` before creating or updating a saved check. Tests are side-effect-free: no incidents, retained history rows, or counters.",
+    "- Create, update, delete, enable, or disable checks only when the user explicitly asks to change monitoring.",
+    "- Availability incidents reuse the normal incident lifecycle. If a check opened an incident, fetch the incident context, bundle, and reproduction before proposing a fix, then resolve only after the endpoint recovers or the intentional verification incident has served its purpose.",
+    "- Do not configure private, localhost, metadata-service, credentialed, or state-mutating targets. V1 health-check targets must be external `http`/`https` URLs on safe ports.",
+    "",
     "## Incident Hygiene",
     "",
     "- Treat `open` as actionable work, not historical record.",
@@ -15999,6 +16019,25 @@ function buildSkill() {
     "- Scope frontend noise by structured evidence such as service, environment, `browser_event_kind`, `browser_event_opaque`, `client_kind`, `bot_family`, and message fields. Do not broadly demote generic `Unhandled promise rejection` incidents without bot-scoped or otherwise narrow evidence.",
     "- For expected or intentionally promoted 4xx responses on known routes, use capture-policy client-error path rules instead of promoting all client errors: `debugbundle capture-policy set --client-error-path-rule <status=/path/*@GET>`.",
     "",
+    "## Notification Delivery",
+    "",
+    "When notification or automation delivery is the reported failure, inspect configuration and delivery records before changing incident logic.",
+    "",
+    "- Alerts route incident notifications to configured channels. Start with `debugbundle alert list --project-id <id> --json` and confirm condition, severity, service, cooldown, channel, and enabled state.",
+    "- Webhooks deliver signed lifecycle events to external systems. Start with `debugbundle webhook list --project-id <id> --json`, then inspect `debugbundle webhook deliveries <webhook-id> --project-id <id> --json` before retrying or testing.",
+    "- Webhook tests and retries are side-effecting delivery actions. Use them only when validating a destination or replaying an explicit failed delivery.",
+    "",
+    "## Full Documentation",
+    "",
+    "- CLI: `https://debugbundle.com/docs/cli`",
+    "- MCP tools: `https://debugbundle.com/docs/mcp/tools`",
+    "- Availability checks: `https://debugbundle.com/docs/availability-checks`",
+    "- Probes: `https://debugbundle.com/docs/probes`",
+    "- Capture policy and rules: `https://debugbundle.com/docs/capture-policy`",
+    "- Alerts: `https://debugbundle.com/docs/alerts` and `https://debugbundle.com/docs/cli/alerts`",
+    "- Webhooks: `https://debugbundle.com/docs/webhooks` and `https://debugbundle.com/docs/cli/webhooks`",
+    "- API ingestion: `https://debugbundle.com/docs/api/ingestion`",
+    "",
     "## Profile Validation",
     "",
     "Use this task after setup or whenever architecture changes make the static profile stale.",
@@ -16076,6 +16115,56 @@ function buildCliReference() {
     "",
     "Use capture-rule suggestions for repeated operational noise after inspecting an incident bundle. Use capture-policy client-error path rules for route-scoped 4xx incidents instead of promoting all client errors.",
     "",
+    "## Probes",
+    "",
+    "- `debugbundle probe activate <project-id> --label-pattern <pattern> [--service <name>] [--environment <name>] [--ttl-seconds <n>] [--trigger-ttl-seconds <n>] [--auth-file <path>] [--json]`",
+    "- `debugbundle probe list <project-id> [--auth-file <path>] [--json]`",
+    "- `debugbundle probe deactivate <project-id> <activation-id> [--auth-file <path>] [--json]`",
+    "",
+    "Use probes for targeted evidence gathering when bundle context is insufficient. Prefer narrow label patterns, scoped service/environment values, and explicit TTLs.",
+    "",
+    "## Notifications",
+    "",
+    "- `debugbundle alert list --project-id <id> [--limit <n>] [--auth-file <path>] [--json]`",
+    "- `debugbundle alert create --project-id <id> --channel <channel> --condition <condition> [--service-id <id>] [--severity-min <level>] [--cooldown <seconds>] --config-json <json> [--is-enabled <true|false>] [--auth-file <path>] [--json]`",
+    "- `debugbundle alert update <alert-id> --project-id <id> [--service-id <id|null>] [--channel <channel>] [--condition <condition>] [--severity-min <level|null>] [--cooldown <seconds>] [--config-json <json|null>] [--is-enabled <true|false>] [--auth-file <path>] [--json]`",
+    "- `debugbundle alert delete <alert-id> --project-id <id> [--auth-file <path>] [--json]`",
+    "- `debugbundle webhook list --project-id <id> [--limit <n>] [--auth-file <path>] [--json]`",
+    "- `debugbundle webhook create --project-id <id> --url <url> --event <event[,event]> [--environment <env[,env]>] [--service <svc[,svc]>] [--severity-min <level>] [--bundle-type <type[,type]>] [--verification <true|false>] [--is-enabled <true|false>] [--auth-file <path>] [--json]`",
+    "- `debugbundle webhook update <webhook-id> --project-id <id> [--url <url>] [--event <event[,event]>] [--environment <env[,env]>] [--service <svc[,svc]>] [--severity-min <level>] [--bundle-type <type[,type]>] [--verification <true|false>] [--is-enabled <true|false>] [--auth-file <path>] [--json]`",
+    "- `debugbundle webhook delete <webhook-id> --project-id <id> [--auth-file <path>] [--json]`",
+    "- `debugbundle webhook test <webhook-id> --project-id <id> [--event <verification.passed|verification.failed>] [--auth-file <path>] [--json]`",
+    "- `debugbundle webhook deliveries <webhook-id> --project-id <id> [--limit <n>] [--auth-file <path>] [--json]`",
+    "- `debugbundle webhook retry <webhook-id> <delivery-id> --project-id <id> [--auth-file <path>] [--json]`",
+    "",
+    "Use alert commands for notification routing and webhook commands for signed event delivery, delivery history, synthetic tests, and manual retries.",
+    "",
+    "## Availability Checks",
+    "",
+    "- `debugbundle health checks list --project-id <id> [--limit <n>] [--auth-file <path>] [--json]`",
+    "- `debugbundle health checks get <check-id> --project-id <id> [--auth-file <path>] [--json]`",
+    "- `debugbundle health checks create --project-id <id> --name <name> --url <url> --interval-seconds <n> [--method <GET|HEAD>] [--expected-status-min <code>] [--expected-status-max <code>] [--timeout-ms <n>] [--failure-threshold <n>] [--recovery-threshold <n>] [--environment <name>] [--service <name|null>] [--enabled <true|false>] [--auth-file <path>] [--json]`",
+    "- `debugbundle health checks update <check-id> --project-id <id> [--name <name>] [--url <url>] [--method <GET|HEAD>] [--expected-status-min <code>] [--expected-status-max <code>] [--timeout-ms <n>] [--interval-seconds <n>] [--failure-threshold <n>] [--recovery-threshold <n>] [--environment <name>] [--service <name|null>] [--enabled <true|false>] [--auth-file <path>] [--json]`",
+    "- `debugbundle health checks delete <check-id> --project-id <id> [--auth-file <path>] [--json]`",
+    "- `debugbundle health checks test --project-id <id> --url <url> [--method <GET|HEAD>] [--expected-status-min <code>] [--expected-status-max <code>] [--timeout-ms <n>] [--auth-file <path>] [--json]`",
+    "- `debugbundle health checks results <check-id> --project-id <id> [--limit <n>] [--auth-file <path>] [--json]`",
+    "- `debugbundle health checks daily-rollups <check-id> --project-id <id> [--limit <n>] [--auth-file <path>] [--json]`",
+    "",
+    "Use availability-check commands for hosted endpoint reachability. Prefer `test` before saving a new target. `test` is side-effect-free and does not create incidents or retained history. Saved checks remain visible after downgrade, but checks beyond current count or interval limits pause until the project becomes eligible again.",
+    "",
+    "## Documentation URLs",
+    "",
+    "- CLI overview: `https://debugbundle.com/docs/cli`",
+    "- Cloud workflow: `https://debugbundle.com/docs/cli/cloud-workflow`",
+    "- API overview: `https://debugbundle.com/docs/api`",
+    "- API ingestion: `https://debugbundle.com/docs/api/ingestion`",
+    "- Alerts: `https://debugbundle.com/docs/alerts` and `https://debugbundle.com/docs/cli/alerts`",
+    "- Webhooks: `https://debugbundle.com/docs/webhooks`, `https://debugbundle.com/docs/cli/webhooks`, and `https://debugbundle.com/docs/api/webhooks`",
+    "- Probes: `https://debugbundle.com/docs/probes` and `https://debugbundle.com/docs/api/probes`",
+    "- Capture policy and rules: `https://debugbundle.com/docs/capture-policy`",
+    "- Availability checks: `https://debugbundle.com/docs/availability-checks`",
+    "- MCP tool catalog: `https://debugbundle.com/docs/mcp/tools`",
+    "",
     "## Operational Paths",
     "",
     "- `.debugbundle/profile.json` \u2014 committed project map and agent validation state",
@@ -16097,7 +16186,7 @@ function buildCliReference() {
     "",
     "```bash",
     "debugbundle incidents --status open --json",
-    "debugbundle resolve <incident-id>",
+    "debugbundle resolve <incident-id> [incident-id ...]",
     "debugbundle incidents --status open --json",
     "```",
     "",
@@ -16142,6 +16231,45 @@ function buildMcpReference() {
     "",
     "Use these tools for repeated low-value operational noise only after inspecting incident evidence. Keep frontend suppression scoped by structured browser and client signals, and use path-scoped capture policy for known 4xx routes.",
     "",
+    "## Probe Tools",
+    "",
+    "- `activate_probe` \u2014 activate a remote probe pattern with optional service/environment scope and TTL.",
+    "- `list_active_probes` \u2014 list active probe activations for a project.",
+    "- `deactivate_probe` \u2014 deactivate one active probe.",
+    "",
+    "Use probes for targeted evidence gathering when incident bundles do not contain enough runtime context.",
+    "",
+    "## Notification Tools",
+    "",
+    "- `list_alerts`, `create_alert`, `update_alert`, `delete_alert` \u2014 manage incident alert rules.",
+    "- `list_webhooks`, `create_webhook`, `update_webhook`, `delete_webhook` \u2014 manage signed webhook destinations.",
+    "- `test_webhook`, `list_webhook_deliveries` \u2014 validate webhook delivery and inspect delivery history.",
+    "",
+    "Use these tools when the reported problem is missing, duplicate, delayed, disabled, or failed notification delivery.",
+    "",
+    "## Availability Check Tools",
+    "",
+    "- `list_health_checks` \u2014 list hosted health checks and plan limits for a project.",
+    "- `get_health_check` \u2014 fetch one hosted health check by id.",
+    "- `test_health_check` \u2014 run a side-effect-free target test without opening incidents or writing retained history.",
+    "- `create_health_check`, `update_health_check`, `delete_health_check` \u2014 manage saved hosted health checks when the user explicitly asks to change monitoring.",
+    "- `list_health_check_results` \u2014 inspect recent raw executions for one check.",
+    "- `list_health_check_daily_rollups` \u2014 inspect retained per-day status history for one check.",
+    "",
+    "Use these tools for endpoint downtime, public reachability, and project Health tab issues. Start with list/results/rollups, use `test_health_check` before saving target changes, and inspect the linked normal incident bundle when failures crossed the configured threshold.",
+    "",
+    "## Documentation URLs",
+    "",
+    "- MCP overview: `https://debugbundle.com/docs/mcp`",
+    "- MCP workflows: `https://debugbundle.com/docs/mcp/workflows`",
+    "- MCP tools: `https://debugbundle.com/docs/mcp/tools`",
+    "- Availability checks: `https://debugbundle.com/docs/availability-checks`",
+    "- Probes: `https://debugbundle.com/docs/probes`",
+    "- Capture policy and rules: `https://debugbundle.com/docs/capture-policy`",
+    "- Alerts: `https://debugbundle.com/docs/alerts`",
+    "- Webhooks: `https://debugbundle.com/docs/webhooks`",
+    "- API ingestion: `https://debugbundle.com/docs/api/ingestion`",
+    "",
     "## Smoke-Test Cleanup Recipe",
     "",
     '1. Call `list_incidents` with `status: "open"`.',
@@ -16276,6 +16404,15 @@ function buildSkillEvals() {
             "Use capture-policy path rules for known route-scoped 4xx incidents."
           ]
         },
+        {
+          name: "operational_controls_guidance",
+          prompt: "The user reports missing webhook deliveries and asks whether probes or alerts are available. Confirm the skill points the agent to the relevant operational controls and docs.",
+          expected_behavior: [
+            "Inspect alert and webhook configuration plus webhook delivery history before changing application code.",
+            "Use probes for targeted evidence gathering with narrow scope and TTL.",
+            "Point to the full CLI, MCP, alerts, webhooks, probes, capture policy, availability checks, and ingestion documentation URLs."
+          ]
+        },
         {
           name: "artifact_path_discovery",
           prompt: "The user reports an unknown local runtime error. Confirm the skill tells the agent which DebugBundle paths and commands to inspect first.",
@@ -27622,7 +27759,7 @@ function buildManagedAgentsSection() {
     "- Read `.agents/skills/debugbundle/SKILL.md` for the full debugging workflow.",
     "- Use `debugbundle inspect <incident-id>` or MCP `get_bundle` when a user reports an issue.",
     "- Run reproduction artifacts from `.debugbundle/bundles/local/reproductions/` before proposing a fix.",
-    "- After a fix is verified, or after an intentional smoke or dogfood incident has served its purpose, resolve it with `debugbundle resolve <incident-id>` or MCP `resolve_incident` so open incidents remain actionable.",
+    "- After a fix is verified, or after an intentional smoke or dogfood incident has served its purpose, resolve it with `debugbundle resolve <incident-id> [incident-id ...]` or MCP `resolve_incident` / `resolve_incidents` so open incidents remain actionable.",
     "- Use `debugbundle doctor` to validate local DebugBundle setup or connectivity issues.",
     MANAGED_AGENTS_END
   ].join("\n");
@@ -36537,7 +36674,7 @@ async function handleCaptureRuleCommand2(parsedArgv, dependencies) {
 // package.json
 var package_default = {
   name: "@debugbundle/cli",
-  version: "1.5.0",
+  version: "1.5.1",
   private: false,
   description: "Command-line interface for DebugBundle",
   license: "AGPL-3.0-only",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@debugbundle/cli",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "private": false,
   "description": "Command-line interface for DebugBundle",
   "license": "AGPL-3.0-only",