anchors migrate

Bring the Anchors files up to the current format.

Rewrites the `anchors.graph.yaml` and the `anchors.yaml` into the format
that this binary reads.

The format goes up when a change makes the file UNREADABLE for the previous
version — a renamed key, a value that changed shape. It does not go up for a new
optional field: an old binary simply ignores it.

The migration runs ONCE and leaves the project ready to commit. It is idempotent:
running it again changes nothing.

    anchors migrate              # migrates
    anchors migrate --dry-run    # says what it would do, without writing

Usage

anchors migrate [flags]

Flags

Flag	Default	What it does
--dry-run		say what it would do, without writing
--root	.	project root

Setup and artifacts — family

Commands of the same family — what tells each apart:

Command	What it does
anchors init	Configure the project (anchors.yaml) through questions and answers
anchors new	Emit the skeleton of an artifact (spec, feature, test, plan…) per the ruler
anchors code	Generate a unique identity code for a new unit
anchors guide	Print the Anchors guides for AI agents
anchors docs	Compile the documentation from the templates in doct/
anchors install-hooks	Install the git pre-commit that runs the gates over staged files
anchors migrate	Bring the Anchors files up to the current format
anchors settings	This agent’s LOCAL configuration — what is its own, not the project’s
anchors touch	Bump updated_at in the @anchors header of the files that changed