cdno migrate

Record the version of the Research Logbook Method this cdno implements in the vault ([vault] method_version in .cuaderno/config.toml), running any file migrations that version needs and logging the move in today’s daily note.

cdno migrate [OPTIONS]

Options

Plus the global options. --json prints the same report as an object: dry_run, outcome (planned, migrated or nothing_to_do), vault (null when unstamped), vault_described, binary, migrations, config_line, log_entry and read_through.

migrate asks nothing and confirms nothing: run it with --dry-run first to see exactly what will change.

What it does

• This cdno implements RLM 1.2. A vault without a recorded version is unstamped and read as RLM 1.0; cdno migrate stamps it, or a vault stamped 1.0, with 1.2.

• File migrations, when a version needs any, never touch the journal or any append-only note. When there are none the report says none: additive.

• The daily log gains one entry:

  vault migrated
    was: unstamped (read as 1.0)
    now: 1.2
  

• A vault below RLM 1.1 gets a read-through, whether or not it is stamped: every hard date on a parked map (a hard milestone, or an action note’s due:), which the commitments register now keeps, listed with its map, overdue first. Drop or re-date each; cdno lint warns on the overdue ones until the vault records RLM 1.1.

    read-through (hard dates on parked maps, overdue first; drop or re-date each):
      2026-04-15  Grant report  (hard milestone on [[beta]], overdue)
      2026-05-01  Shelved draft  (action due on [[beta]], overdue)
      2026-11-01  Final review  (hard milestone on [[beta]])
  

• A vault already at this cdno’s version prints vault is at RLM 1.2; nothing to do: its read-through is done.

• A vault on a newer version than this cdno is refused with a non-zero exit: upgrade cdno instead.

migrate runs only when you run it: never when a vault opens, and never over MCP.

The notice

When a vault records an older method version than this cdno, other commands print one line on stderr after they finish, naming both versions and pointing at cdno migrate --dry-run. A vault on a newer minor version gets a line saying writes proceed and cdno can be upgraded. migrate, init, now --line and shell completion never print it, and stdout (including --json) is never touched.

Examples

cdno migrate --dry-run
cdno migrate

See also

• init, lint.
• Configuration: method version.
• Troubleshooting: writes are refused with a method version error.