@noego/proper 0.2.1 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noego/proper",
-  "version": "0.2.1",
+  "version": "0.3.0",
   "description": "",
   "main": "bin/index.js",
   "module": "bin/index.mjs",

package/readme.md

@@ -57,6 +57,14 @@ Below is a fast-track on **how to work** with SQL Proper from the command line.
    ```
    Edit those `.sql` files and add your migration scripts.
 
+   Always use `proper create` to mint the timestamp — never type one by hand.
+   Generated stamps never end in `0`, and `proper up` refuses to apply a
+   **pending** migration whose stamp ends in `000` (a tell-tale hand-typed
+   value). Migrations that were already applied are never re-checked. A
+   historical rounded key can be allowed only by listing that exact canonical
+   key in `legacy_migration_keys`; the strict check remains active for every
+   other key.
+
 3. **Apply migrations**:
    ```bash
    proper up
@@ -114,6 +122,10 @@ Here’s a sample `proper.json` for **SQLite** (change `"database": "sql"` if us
 - **database**: Either `"sql"` (for MySQL) or `"sqlite"`.
   - If using `"sql"`, fill out the `sql` object (`host`, `user`, `password`, `database`).
   - If using `"sqlite"`, define `"sqlite": { "database": "<path or :memory:>" }`.
+- **legacy_migration_keys**: Optional array of exact canonical keys for known historical
+  migrations whose rounded timestamp ends in `000`. Paths, migration filenames,
+  wildcards, nonstrings, and noncanonical spellings are rejected; unlisted rounded
+  migrations remain blocked.
 - **host** / **user** / **password** / **database**: Standard MySQL connection details if `"database": "sql"`.
 
 Use `proper init` to quickly generate a default config, or manually create your own. When running the CLI, if your config isn’t in `proper.json`, specify `--config`: