coulomb/repo-manager
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

prepare fleet identifier completion batch

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
This commit is contained in:
tegwick 2026-08-31 17:02:19 +02:00
parent c52d222cc6
commit 8f3b8ac2f6
8 changed files with 4691 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/work-record-uuid-derivation_v1.md
View file

@ -80,10 +80,13 @@ origin. The batch records these facts and its own SHA-256 seal, but always emits
`apply_authorized: false`. An explicit decision must cite that batch hash before
any database or file mutation. Repeat `--projection-api-base` for every hub in
the cutover. Each replacement is classified as `legacy_source`,
`derived_target`, `both_present`, or `neither_present`. The first two may coexist
inside one repository-atomic migration: State Hub migrates legacy rows, verifies
already-derived rows against their canonical record identity, and records the
same durable aliases for both. The latter two states are refused. Saved
`derived_target`, `duplicate_target`, `both_present`, or `neither_present`. The
first three may coexist inside one repository-atomic migration: State Hub
migrates legacy rows, verifies already-derived rows against their canonical
record identity, and may coalesce a `duplicate_target` task only when both
business payloads are equal and the legacy row has zero inbound references.
Other both-present and all neither-present states are refused. Durable aliases
are recorded for every converged replacement. Saved
projection endpoints are rechecked by `migration-batch-verify`; omitting the
option retains the offline source/Git-only planning mode. A projection-aware
batch containing UUID assignments fails closed until an assignment-specific