[jeremydmiller]

What

Documentation only. Fisher's docs already said db-apply and resources setup migrate under AutoCreate.None, but never said how to enable those commands or what the rest of them do. This links every mention to the Weasel reference and the JasperFx stateful resource model, and lays out the options.

• docs/schema/index.md: Weasel link to the docs site; a table of the four approaches (lazy, startup, deployment step, reviewed SQL) with db-assert as the gate; a new From the command line section: RunJasperFxCommands(args), the five db-* commands and resources list/check/setup, which are Weasel's and which JasperFx's, that the explicit applies migrate under None, and that db-apply against a path that does not exist yet creates the file. The None tip links the commands.
• docs/schema/migrations.md: Production migrations now names db-dump / db-patch as the command-line forms and the db-apply / resources setup deployment-step alternative; db-patch linked where WriteMigrationFileAsync is described.
• docs/configuration/storeoptions.md, docs/schema/exporting.md, docs/getting-started.md: link the commands and the options.

Checked

• vitepress build docs passes (no dead internal links); all external links checked live.
• Part of a sweep across Marten, Polecat, Fisher, Wolverine, CritterWatch and Weasel itself (the Weasel docs PR adds a canonical "Choosing a Schema Management Approach" page these pages can link to once redeployed).

🤖 Generated with Claude Code