Release v3.0.0-rc.8

Breaking change

Coordination/Timeline Entry no longer declares canonical sequence. Generic Coordination ordering and checkpoint newness use the required exact timestamp, which must increase strictly within one timeline. Provider-specific sequence, cursor, or block metadata remains ordinary event content and does not affect generic ordering.

This regeneration changes Timeline Entry and dependent BlueIds. Persisted state authored against RC7 is an explicit migration boundary: RC8 provides no implicit legacy-ID alias or dual-version matcher.

Changelog

91d2cc9 chore: release 3.0.0-rc.8
7e9a11f Merge pull request #13 from bluecontract/feat/coordination-v2-and-mandates
c76d67c test(repo): verify timestamp-ordered timeline entry
811a914 feat(repo)!: regenerate timestamp-ordered timeline entry
98e1086 fix(types): rename mandate authority document
d84307b chore: release 3.0.0-rc.7