@netlify/agent-runner-cli 1.104.0 → 1.105.0-netlifydb.0

package/dist/skills/general-database/SKILL@netlifydb.md

@@ -1,21 +1,24 @@
 ---
 name: general-database
-description: Use this skill whenever the task involves storing, persisting, querying, or managing data — including CRUD operations, collections, records, user data, or any application state that needs to survive between requests. Covers both relational databases (Netlify Database) and key-value storage (Netlify Blobs).
+description: Use this skill whenever the task involves storing, persisting, querying, or managing data — including CRUD operations, collections, records, user data, or any application state that needs to survive between requests. Covers both relational databases (Netlify Database) and object storage (Netlify Blobs).
 ---
 
 # Data Storage on Netlify
 
-## Relational data: Netlify Database
+Prefer Netlify Database over Netlify Blobs for any application data — records, collections, lists, user-generated content,
+or anything you would store as rows. Use Blobs only for files, binary assets (images, video), or cached responses.
 
-**Netlify Database** is the recommended solution for relational data storage. It provides a fully managed Postgres database
+## Application data: Netlify Database
+
+**Netlify Database** is the recommended solution for storing application data. It provides a fully managed Postgres database
 with zero configuration — install the `@netlify/database` package, and a database is automatically provisioned for your site.
 
-Use Netlify Database when you need:
+Use Netlify Database when you need to store:
 
-- Relational data (tables, joins, foreign keys)
-- SQL queries and filtering
-- Transactions
-- Schema migrations
+- Records, collections, or lists
+- User-generated content
+- Any data you would naturally model as rows in a table
+- Data requiring queries, filtering, or transactions
 
 There are two recommended approaches:
 
@@ -29,14 +32,14 @@ IMPORTANT: Any code that assumes a different database schema requires a correspo
 
 See the **netlify-database** skill for complete setup instructions and usage examples.
 
-## Object storage: Netlify Blobs
+## Files and binary assets: Netlify Blobs
 
-**Netlify Blobs** is the recommended solution for object storage.
+**Netlify Blobs** is the recommended solution for file and binary storage.
 
 Use Netlify Blobs when you need:
 
 - File and image storage
-- JSON document persistence
-- Cache storage
+- Binary assets (images, video, PDFs)
+- Cached responses
 
 See the **netlify-blobs** skill for complete setup instructions and usage examples.

package/dist/skills/netlify-database@netlifydb/SKILL.md

@@ -319,29 +319,29 @@ Two formats are supported:
 
 ## Inspecting migration state
 
-Before acting on migrations (generating, deleting, regenerating, resetting), check the current state. The
-`netlify db status` command is the source of truth for which migrations are applied where.
+The current database state — which migrations are already applied to your preview branch, and which migration
+files exist on disk but haven't been applied yet — is included in your context at the start of the run, under
+the "Current Netlify Database state" heading. Read that list before planning any migration work. You do not
+need to run `netlify db status` at the start of a task to get this information.
+
+If you need to re-check state mid-session — typically after generating a new migration, applying migrations, or
+running `netlify db migrations reset` — run:
 
 ```bash
 netlify db status
 ```
 
-The command automatically targets your preview database branch — `NETLIFY_DB_BRANCH` is pre-set for you, so
-no flags are needed.
+The command targets your preview database branch automatically (`NETLIFY_DB_BRANCH` is pre-set).
 
 It reports:
 - **Applied**: migrations that have been applied to the branch
 - **Pending**: migration files that exist locally but have not been applied
-- **Missing on disk**: migrations applied on the server but not present locally (drift — stop and investigate)
+- **Missing on disk**: migrations applied on the server but not present locally (drift — this is a serious
+  state; never intentionally create it)
 - **Out of order**: pending migrations whose prefix sorts before an already-applied migration. The platform
   rejects these, so fix via the "Rule of thumb" below (reset + regenerate). If `drizzle-kit generate` then
   reports no changes, the out-of-order files were redundant and deleting them was the complete fix.
 
-Run this before any migration change you're not sure about. If `missing on disk` is non-empty, run
-`netlify db migrations pull --force` to restore the missing files from the branch before generating any new
-migrations. Note that this also overwrites any unapplied migration files you have locally — regenerate those
-with `npx drizzle-kit generate` afterwards if needed.
-
 ## Iterating on migrations within a session
 
 A single agent session can run multiple times, and all runs share one preview database branch. When you realize

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@netlify/agent-runner-cli",
   "type": "module",
-  "version": "1.104.0",
+  "version": "1.105.0-netlifydb.0",
   "description": "CLI tool for running Netlify agents",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -84,7 +84,7 @@
     "@anthropic-ai/claude-code": "2.1.111",
     "@anthropic-ai/sdk": "0.90.0",
     "@google/gemini-cli": "0.38.2",
-    "@netlify/database-proxy": "^0.1.2",
+    "@netlify/database-proxy": "^0.1.4",
     "@netlify/otel": "^5.1.5",
     "@netlify/ts-cli": "^1.0.4",
     "@openai/codex": "0.121.0",