# Live Daily Price Review Rollout And `0805.XML` Acceptance

## Metadata

- Date: 2026-08-06
- Status: Historical initial-review rollout; superseded for latest runtime state by the integer/finalization repair topic
- Scope: controlled `booking_test`, local authenticated Web on port 8766, exact desktop `0805.XML`
- Acceptance job: `arrjob-dddc27119bea43b19588c78eac087763` (run 65)
- Review case: `dailyreview-878e45ae132b73c131560299b3b2dcb3`

## Rollout evidence

- The privacy-minimized pre-017 checkpoint is
  `runtime/backups/booking_test_pre_017_20260806T192026+0800/manifest.json`, SHA-256
  `d66cc4341db42420b9382fa78c90214f5ecb3c200062c0ac4bb8d275a7123b17`. It excludes credentials, XML bytes,
  guest rows and raw delivery/outbox payloads.
- The first up/down probe failed closed and rolled back because 017 had simplified the migration-010
  `artifact_callback`/`direct_mcp` terminal constraint. Corrected up/down preserve that legacy split and add only the
  `awaiting_review` branch. The corrected probe restores the exact pre-migration fingerprint and leaves no row/schema
  residue; its evidence SHA-256 is `c62e07f60b4f2b481fb6fcb72a6aeaeccc3e73b87f36f87af1478f63027eb971`.
- Live migration-016 function/comment semantics were already exact before the rollout; 016 was not rerun. Corrected
  migration 017 SHA-256 `22a0578e8748573d29ff2c15dbc687aaea14d7dc0c34cf8fe1faa2ef56067b5b` was formally applied under an advisory lock.
  All new relations, columns, indexes, triggers and lifecycle/pricing values passed post-commit checks while original
  business table counts stayed unchanged. Formal evidence SHA-256 is
  `9837fce88d5bd18ff58b5575375af9f31fec89252123b7cf44d3a3fb991bd83a`.
- Runs 61–63 were closed through the normal repository transition as
  `REVIEW_SCHEMA_MIGRATION_MISSING`. Their three private source artifacts remain intact; only three
  `arr.processing_failed` audit events were added. No delivery, review case, Finance version or daily-commit event was
  created for those shells. Cleanup evidence SHA-256 is
  `ad0d4ce01644d6adc5e58fc0c5182240398568ed4b6546be1a3b15a4dbb273a1`.

## Runtime correction and real acceptance

- The first post-migration upload became run 64 and failed safely as `DATABASE_WRITE_FAILED`. Source artifact 173 and
  failure event 45 were retained, with no delivery/review/Finance fact. Diagnosis found a 16-value/15-placeholder
  mismatch in the newly extended `processing_deliveries` INSERT. The missing placeholder and a regression assertion
  were added; 18 focused migration/PostgreSQL tests, compilation and whitespace checks pass, and PostgreSQL plans the
  exact 16-parameter INSERT.
- Final repository discovery passes all 384 tests with three intentional skips for private booking fixtures. Package
  checksums, Python/JavaScript syntax, diff whitespace and project-document gates also pass.
- Web was restarted as PID 24225. Authenticated health reports database, processing, monthly, download, company report
  and company source upload readiness all true.
- One subsequent exact-hash upload reached run 65 and automatically opened the live review panel. PostgreSQL records
  `awaiting_review` / `review_required` / `recorded_review`, one open revision-0 case, one
  `PRICE_REVIEW_REQUIRED` event and exactly two unset items:
  - `LIAN TAI / GRP1 / 1150.00`, impact 1 record / 1 room / 1 room-night;
  - `LIAN TAI / LBLT / 0.00`, impact 1 record / 1 room / 0 room-nights.
- The page shows both fixed-price candidate lists, `复核 0 / 2`, and a disabled `确认并生成日报` button. No employee
  price was entered and the case was not finalized or cancelled.
- Only source XML, result JSON and structured-result JSON are registered. The run has no daily XLSX, exception XLSX,
  manual manifest, Finance version or outbox event. Total `arr.daily_version_committed` remains 20, monthly-run count
  remains 14, and historical daily version 28 remains rejected with no review lineage.
- The complete acceptance snapshot is
  `runtime/backups/booking_test_pre_017_20260806T192026+0800/live-0805-review-acceptance.json`, SHA-256
  `a8994ada1644e039dac7ea888cdba5143bca72cbc6d47c5bf7c4e09d5d6fa315`.

## Remaining boundary

Finance must supply the two approved prices in the open panel. Only after both revision-locked saves should an
authorized employee invoke finalization and verify the expected final 153 retained rows, two `manual_review` rows,
one active Finance version and exactly one new daily-commit/monthly event. Historical version 28 must remain unchanged.

This was the exact run-65 state at rollout time. Subsequent employee interactions created runs 66/67 and exposed two
finalization defects now repaired by migration 018 plus an SQL-bind correction. Use
`2026-08-06-integer-review-finalize-repair.md` for the current retry boundary; do not act on this historical run-65
instruction.
