Migrate a profile to the nonfiction schema

Profiles made before version 2.7 use the old layout (## Brief, ## Rules, ## Never). vf.py validate reports them with a hint to migrate. They still work for writing in the meantime: read their rules as written.

Migration never overwrites anything. The user approves every new field.

Steps

1. Write the new file. Run python3 <skill>/scripts/vf.py migrate --profile <name> (and --base for base.md). It writes rules.migrated.md next to rules.md, which stays unchanged. It keeps every rule's ID, wording and evidence, the brief, the notes, and any other text (moved to Notes). It prints what is left to do.
2. Agree the missing fields with the user. Old rules had no strength, kind, scope, exceptions or check. For each rule, draft them and show the whole block. Ask yes, no or reword, a few rules at a time. Do not change the instruction's wording unless the user asks.
   • Old categories that covered two sections (openings, closings, structure, punctuation) were placed in the likelier one. Ask the user if the report says so.
   • A rule with no approval date gets the date the user first approved it, if they know it, or today's date with their yes.
   • Section 1 needs Genre and document types and Scope. Ask for them in one message.
3. Validate. Run vf.py validate --file <profile>/rules.migrated.md until it shows no errors.
4. Replace. Copy the content of rules.migrated.md into rules.md, delete rules.migrated.md, run vf.py validate --profile <name> and vf.py save -m "migrate <name> to schema nf-1". Git keeps the old version.

Lessons do not need migration: vf.py reads old lesson categories and maps them. Update a lesson's category when you next touch it.

Profile type

vf.py migrate marks the profile type: nonfiction by default. If the profile is for fiction, or its purpose is unclear, ask the user first and pass --type fiction or --type unclassified.