gabriel / musehub public
refactor BREAKING task/rename-record-uuid-to-record-id #1 / 1
AI Agent gabriel · 44 days ago · May 4, 2026 · Diff

refactor: rename record_uuid → record_id, widen String(36) → String(128)

MusehubCoordRecord.record_uuid was a misnomer — the field stores sha256 genesis IDs (sha256:<64-hex>, 71 chars) and opaque run_id strings, not UUID4 (36 chars). The String(36) column width was also too narrow.

- db/coord_models.py: rename column, widen type, update UniqueConstraint and docstrings - models/coord.py: rename field in CoordRecordIn/Out, replace UUID4 validator with _SAFE_RECORD_ID_RE (accepts sha256: prefix + opaque ids) - services/musehub_coord.py: update all ORM attribute references - services/musehub_coord_server.py: update materialize function params - api/routes/coord.py: update docstrings - alembic/versions/0027: RENAME COLUMN + ALTER TYPE migration - tests/test_coord_record_id.py: TDD guard for the rename and new width

sha256:5f659985c9aaf7fb0d3e6b007b6a753aff99807c34de998900cad2019fe13787 sha
sha256:e33c113c1068372f5aefa0aafeff4cabc2d3db25cc4d226c67a688f38687ade2 parent
sha256:0a7dac217f39dd0a00ea69a5d1aff716257a66998b3a100ad68c2820f3626901 snapshot
← Older Oldest on task/rename-record-uuid-to-record-id
All commits
Newer → Latest on task/rename-record-uuid-to-record-id

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:5f659985c9aaf7fb0d3e6b007b6a753aff99807c34de998900cad2019fe13787 --body "your comment"