Task-note Migration Operator

Legacy per-note migration operator retained only for pre-native recovery; superseded by the native task importer and cutover.

MCP name: task_note_migration_operator

Category: tasks

Mutates state (retry policy: manual)

Parameters

Name	Type	Required	Description
action	string	Yes	One of inventory, shadow_import, validate_parity, set_gate, cutover, rollback, or recover.
enabled	bool	No	Desired gate state for set_gate.
gate	string	No	task_note_cutover_gate for set_gate. Journal exit is derived from durable Journal migration evidence.
limit	int	No	Maximum pending source-backed changes to recover (1-100, default 25).
note_uuid	string	No	Stable task-note UUID for a one-note action.
rollback_deadline	string	No	Future ISO-8601 deadline required for cutover.

Details

This capability belongs to the superseded per-note Markdown migration. It is retained for inspection and recovery of pre-native receipts and must not be used as the native task cutover path or invoked after native authority activates.

For a pre-cutover recovery run, it migrates only the Markdown body identified by note_uuid. It never moves task-master, status, scheduling, or link authority. Inventory is content-free. Shadow import captures the exact Markdown file as a Source with unknown authorship and persists the managed-copy dependency before Source acknowledgement. Parity uses newline/BOM normalization only.

The task-note cutover gate is closed when the migration store is created. Journal readiness is not a second mutable Boolean: cutover calls the Journal domain's current exit-evidence verifier and requires its persisted cohort and production-callsite digests to still match. This capability cannot manufacture that evidence. Gate changes, cutover, and rollback carry a separate high-risk consent gate. Cutover is per note and additionally requires recorded parity plus a future rollback deadline. After cutover, whole-document writes are captured as exact Sources, reserved and rechecked before a durable document change, acknowledged only after the reverse dependency is durable, and projected without clobbering an unexpected file base. Recovery resumes receipts by idempotency key.

Source redaction scrubs automatically only while the exact Source-produced document head remains current and has no direct edits. A changed/mixed head is marked for review; Hindsight, projections, and compatibility Markdown never become content authority. The whole-system backup, deterministic legacy import, recovery catalog, durable authority latch, and guarded activation are documented at tasks/native-task-system.