@carllee1983/dbcli 7.0.1 → 8.0.0

package/assets/tasks/safe-backfill-verify.md

@@ -2,7 +2,7 @@
 name: safe-backfill-verify
 description: Plan a safe backfill/UPDATE and a read-back assertion that verifies the write achieved its goal.
 tags: [data, write, safety, verification]
-engines: [postgres, mysql]
+engines: [postgresql, mysql]
 params:
   table:
     type: string
@@ -23,8 +23,8 @@ params:
 safety:
   mode: plan-only
   requires:
-    - blacklist-list
-    - schema-check
+    - blacklist.manage
+    - schema.read
 steps:
   - type: command
     command: blacklist list

package/assets/tasks/safe-backfill.md

@@ -2,7 +2,7 @@
 name: safe-backfill
 description: Plan a safe data backfill/UPDATE with blacklist, schema and risk checks before any write.
 tags: [data, write, safety]
-engines: [postgres, mysql]
+engines: [postgresql, mysql]
 params:
   table:
     type: string
@@ -15,8 +15,8 @@ params:
 safety:
   mode: plan-only
   requires:
-    - blacklist-list
-    - schema-check
+    - blacklist.manage
+    - schema.read
 steps:
   - type: command
     command: blacklist list

package/assets/tasks/schema-drift-review.md

@@ -2,7 +2,7 @@
 name: schema-drift-review
 description: Detect drift between the cached/committed schema and the live database for one table.
 tags: [diagnostics, schema, readonly]
-engines: [postgres, mysql]
+engines: [postgresql, mysql]
 params:
   table:
     type: string
@@ -11,8 +11,8 @@ params:
 safety:
   mode: plan-only
   requires:
-    - blacklist-list
-    - schema-check
+    - blacklist.manage
+    - schema.read
 steps:
   - type: command
     command: blacklist list

package/assets/tasks/slow-endpoint-investigation.md

@@ -2,16 +2,20 @@
 name: slow-endpoint-investigation
 description: Connect proxy, explain and missing-index evidence to investigate a slow endpoint's query.
 tags: [diagnostics, performance, readonly]
-engines: [postgres, mysql]
+engines: [postgresql, mysql]
 params:
   query:
     type: string
     required: true
     description: The suspected slow SQL statement behind the endpoint (not executed by this task).
+  table:
+    type: string
+    required: true
+    description: The exact table the local observation points at (confirm via `dbcli list`).
 safety:
   mode: plan-only
   requires:
-    - blacklist-list
+    - blacklist.manage
 steps:
   - type: command
     command: blacklist list
@@ -21,6 +25,10 @@ steps:
     command: proxy analyze --format json
     reason: Aggregate observed slow queries and N+1 patterns from the local proxy event log.
     risk: readonly
+  - type: command
+    command: schema {{table}} --format json
+    reason: Confirm the selected table's live columns and indexes before reading a plan or index advice.
+    risk: readonly
   - type: command
     command: explain "{{query}}"
     reason: Inspect the query plan for the suspected statement without running it for effect.
@@ -34,7 +42,12 @@ steps:
 
 Use this task when an endpoint is slow and you want evidence, not guesses. Start from
 `proxy analyze` (requires that the local observability proxy has captured traffic) to
-find the hottest query/table, then `explain` that statement and review
-`guide missing-index-for` candidates. Index advice is ADVISORY: do not create indexes
-directly — route any proposed index through the `migration-review` pack first, then
-verify before/after with `snapshot`/`assert` or `report --section perf` deltas.
+find the hottest query/table, confirm that table's live shape with `schema` before
+reading anything into a plan, then `explain` the statement and review
+`guide missing-index-for` candidates.
+
+Everything here is a lead, not a cause. A proxy finding is what was observed locally,
+not proof of what makes the endpoint slow, and an index candidate is not a fix that has
+been shown to work. Index advice is ADVISORY: do not create indexes directly — route any
+proposed index through the `migration-review` pack first, then verify before/after with
+`snapshot`/`assert` or `report --section perf` deltas.