oficina / sheets Public

fix(migrations): renumber to 0009 — core landed its own 0008

Four commits landed on core while this branch was in flight, and one of
them added 0008_alter_sheets.sql. This branch had already added
0008_alter_formats_ink_intent.sql, so the rebase produced two migrations
claiming the same number — cleanly, because they are different filenames
that touch no common line.

migrate.Apply is not harmed: its ledger keys on the migration ID, so
both apply once and the checksum guard still holds. What breaks is the
meaning of the number and the order between them, which falls out of
filename sort rather than out of anyone's intent.

Renumbered rather than left, and now rather than later: apply.go's own
error says migrations are immutable once applied, so this was free only
because this branch has never been deployed. Had it shipped first the
rename would have been unavailable and the duplicate permanent — the
window where this is cheap to fix is exactly the window where nothing
tells you about it. Filed upstream as rastrillo/rastrillo discussion 13,
asking that `migration check` refuse a duplicate number.

Also: a comment of mine named createSheet, which core renamed to
newSheet when it taught the function about half-imported sheets.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182f7QfojuuqdS4Xd2fYFaL