Task: Remove the migration scripts

No migration scripts and no policy that invites them: a schema change edits the create scripts and is verified by recreating the database.

• projects/ores.sql/migration holds no scripts.
• The ores.sql schema upgrade policy says the database is recreated, never migrated.

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

On the operator's instruction (2026-10-03: no migrations, trash and recreate, no backwards compatibility code), the twenty-seven migration scripts other work had left under projects/ores.sql/migration are deleted. The thirteen this story had added went with Rename the curve configuration tables with a _config suffix, so the directory is gone. No tool executed those files; a database recreate reads only the create and populate scripts.

The schema upgrade policy in projects/ores.sql/modeling/component_overview.org no longer allows one-shot scripts: a schema change edits the create/ scripts and the database is recreated. The rule is also a project memory, doc/llm/memory/no_migrations_trash_and_recreate.org.