@farhan0431/db-snap 0.3.10 → 0.3.11

package/README.md

@@ -10,6 +10,8 @@ Supports **SQLite**, **PostgreSQL**, and **MySQL/MariaDB**. The npm package
 bundles prebuilt binaries for Windows x64, macOS Intel and Apple Silicon, and
 Linux x64 (glibc and musl) and ARM64 (glibc).
 
+**MySQL/MariaDB restore is available for the original database.** Stop writers and scheduled events first. Restore is not atomic and requires a pinned safety snapshot. Interrupted restores must recover that snapshot before another restore.
+
 ## Install
 
 Requires Node.js 16 or later.
@@ -69,6 +71,10 @@ before making changes. The server also exposes tools to create, list, restore,
 and prune snapshots. It resolves the project from its working directory, so
 start it in the project you want to protect.
 
+Restore and prune are disabled by default in MCP. To enable them for a server
+session, start it with `dbsnap mcp --allow-destructive`. Each operation requires
+approval through an MCP client supporting elicitation; otherwise use the CLI.
+
 `dbsnap init` also writes `.agents/skills/dbsnap/SKILL.md` in the project.
 Whether that skill is loaded automatically depends on the AI client; the skill
 file and the MCP server are separate integrations.
@@ -85,10 +91,12 @@ file and the MCP server are separate integrations.
 | `dbsnap rollback` | Restore the latest snapshot. |
 | `dbsnap prune --keep 5` | Remove older snapshots and retain the newest five. |
 | `dbsnap diff before after` | Compare SQLite snapshot schemas and table row counts. |
+| `dbsnap pin <tag-or-id>` | Protect a snapshot from pruning; use `unpin` to remove protection. |
 
 `dbsnap list --json` and `dbsnap status --json` provide machine-readable
 output. SQLite `diff` does not compare individual row contents; PostgreSQL and
 MySQL/MariaDB snapshot diffs are not currently supported.
+Pinned snapshots survive `prune`, including `--all`.
 
 ## Database requirements
 
@@ -100,15 +108,24 @@ MySQL/MariaDB snapshot diffs are not currently supported.
 
 PostgreSQL server-side clones are stored on the database server. Use dump mode
 when the snapshot needs to survive removal of that server's data volume.
+For dump save and restore, install `pg_dump` and `pg_restore` matching the
+PostgreSQL server's major version. Mismatched tools are rejected before restore.
 
 ## Safety
 
-- The default host guard restricts operation to local and private-network
-  targets. MCP always uses that guard.
+- MCP permits SQLite and loopback database hosts only. The CLI also permits
+  private-network targets by default. A local target is not necessarily safe.
 - Project binding checks that the current target matches the recorded database.
-- Restore verifies the selected snapshot before applying it and, by default,
+- Restore checks SQLite chunks and dump artifacts before applying them and, by default,
   creates a safety snapshot first. If that snapshot cannot be created, restore
   stops; the CLI has an explicit option to skip it.
+- A PostgreSQL server-side clone has a metadata fingerprint, not a content
+  checksum. dbsnap checks that the clone exists before restore.
+- PostgreSQL restore is not atomic; an interruption can require manual
+  recovery. Clone and staged dump restores journal their cutover.
+- PostgreSQL network connections require verified TLS. Set `DBSNAP_PG_CA_CERT`
+  to a trusted CA PEM file if needed; use `DBSNAP_PG_TLS=verify-full` to require
+  TLS on loopback connections as well.
 
 dbsnap is intended for development workflows. Keep independent backups for
 data you cannot afford to lose.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@farhan0431/db-snap",
-  "version": "0.3.10",
+  "version": "0.3.11",
   "description": "Instant physical database time-machine and MCP server for AI coding agents — git commit/checkout for your local database, powered by Rust.",
   "license": "MIT",
   "bin": {