joshsiv-mulga 53697bc762 refactor: move viperblockd fence, abandon and dirty-marker vocabulary to contracts ...

Move the fence and abandon subjects/DTOs, the dirty bucket name,
DirtyRecord and the shared volume-key pattern out of vbwire and into
contracts/viperblockd/legacy/v1, alongside the package's existing
mount/unmount/delete/sync/config-update routes. vbwire keeps only the
I/O helpers (BindDirtyBucket, ListUnsealedVolumes), now built on the
contract vocabulary instead of defining it.

Record the approved dirty-marker ownership boundary in the contract
README: the Viperblock adapter is the sole producer, viperblockd was
only its transitional custodian. Document the fence and abandon routes
and the dirty bucket in docs/service-interfaces.yaml.

2026-10-09 15:09:22 +10:00

..

cluster/v1

refactor: establish node status contract

2026-10-01 08:22:26 +10:00

ec2/v1

refactor: move the default-VPC subject into contracts/ec2/v1

2026-10-09 13:07:40 +10:00

eks/v1

test: characterize EKS add-on v1 compatibility with added fields

2026-10-09 08:37:42 +10:00

operator/v1

refactor: establish operator storage contract

2026-09-30 15:56:13 +10:00

telemetry/v1

refactor: move telemetry file naming to contract

2026-10-02 14:17:21 +10:00

viperblockd/legacy/v1

refactor: move viperblockd fence, abandon and dirty-marker vocabulary to contracts

2026-10-09 15:09:22 +10:00