# RMGR-WP-0005 batch 0005 projection preflight

**Observed at:** `2026-08-22T21:46:30Z`

**Scope:** `adaptive-pricing` only

## Outcome

Batch 0005 is source-ready but **not ready for approval**. No database or
repository identifier changed.

The refreshed fleet plan is sealed as
`28cd01bdbc66c53ad5ef11b9821a74ebadd7c8cfdae4c227f37ce7f9d67cbf18`.
The adaptive-pricing unit is clean, synchronized with `origin/main`, and pinned
at `c65a2f1ff9a0b30700ee14818e36e931eb71cae3`. It contains five replacements:
`ADAPTIVE-WP-0010` and its four unfinished tasks.

The projection-aware batch manifest is sealed as
`20decab5521ea5477826d1b2a9c9670912a96c4b8245faf5d270c8d1efc988c5`.
It records `ready_for_approval: false` and `apply_authorized: false`.

## Projection evidence

| Projection | Five current UUIDs | Five derived UUIDs | Result |
| --- | --- | --- | --- |
| Workstation `:8000` | HTTP 200 | HTTP 404 | ready |
| Production tunnel `:18000` | HTTP 404 | HTTP 404 | blocked |

A governed `registrar-reconcile --repair-workplan ADAPTIVE-WP-0010` attempt
used clean source revision `c65a2f1...` and correlation id
`b708a73e-fc09-48ee-aa2d-ff8b3c642466`. State Hub retained the conservative
C-03 rule for the pre-derivation random UUID and did not create it. This is the
correct ordinary-consistency behavior, but it means the existing transactional
migration executor cannot run: that executor requires every old source row to
exist in the target repository projection.

The attempt also exposed a Repo Manager result bug: a failed exact repair could
be labeled `applied` because an empty ordinary-registration set passed
verification vacuously. The wrapper now requires repair/bootstrap mode's own
exact projection proof and does not run ordinary requested-record verification
for an empty request.

## Owner-ready resolution

`helixforge.identifiers.state-hub-sealed-projection-repair.v1` offers State Hub
a bounded repair task. It preserves the default C-03 refusal and permits old-row
restoration only from one clean source revision plus one exact sealed migration
unit, with primary confirmation, atomicity, idempotency, and a receipt. Once
adopted, repeat this batch plan against both projections; only a new manifest
with all current lookups 200 and all derived lookups 404 may be proposed for
approval.

The fleet scan found one other projection-complete candidate, `state-hub`, but
its checkout contains unrelated uncommitted owner evidence. The Git preflight
therefore excludes it until the owner publishes or dispositions that work.