mirror of
https://github.com/multica-ai/multica.git
synced 2026-08-01 01:16:17 +02:00
926f691b5d
main is now at 104_drop_runtime_timezone; the migrator picks LatestVersion() by sorted filename, so a slot before the tail would let DBs that have already run 099–104 think they're up-to-date while the issue.metadata column is missing — runtime would then fail with column does not exist. Renumbering to 105 puts the migration at the tail and forces it to run. Also drop attempts as a positive example across docs/code comments and test fixtures — the runtime instruction prompt already lists it under "What NOT to pin" (runtime bookkeeping). Replace with pr_number, which is in the recommended-keys set, so docs/tests speak the same language as the prompt. Co-authored-by: multica-agent <github@multica.ai>