Pier acceptance record

Status: all twelve first-release flows are LOCAL PROVEN. The first target in each row is the corresponding subtest in tests/api/flows.test.mjs; additional targets name their test files or focused probes. Each row is supported by Worker/D1 API coverage and the owner-facing browser journey at 1440px and 390px. This status covers the local first-release scope only; it does not claim hosted operation, provider behavior or physical stock accuracy.

# What a person must be able to do Current test target(s) Status
1 Define an item, unit and pack conversion, set up locations and stock statuses, keep unit/pack semantics fixed after count or other references exist, keep a used location's bin/transit kind fixed, and archive used items without erasing history. 01 item definitions and archive preserve used history; focused item/count and location/count immutability probes passed LOCAL PROVEN
2 Link customers and suppliers, keep one versioned supplier-item record per pair, and use exact terms on a purchase without rewriting an existing commitment. 02 supplier terms are exact snapshots; focused duplicate-pair/versioned-update probe passed LOCAL PROVEN
3 Preview native CSV opening inventory, group open-document lines, retain originals, revise changed rows explicitly, reject ambiguous openings, and either allocate every affected order line by bin (including explicit zero backorders) or use the six-kind automatic reservation behavior. 03 CSV preview review opening inventory and original custody; tests/api/security-import.test.mjs: native import graph revisions, grouped lines, frontier and safe undo; tests/api/native-exit.test.mjs: native exit preserves approved allocation and explicit backorders across a fresh cutover; focused strict-parser and duplicate-opening probes passed LOCAL PROVEN
4 Enter simultaneous orders against the last fractional units, reserve no more than available stock, show the remainder as backorder and recover the same result on retry. 04 simultaneous sales reserve last fractional units with durable outcomes LOCAL PROVEN
5 Review replenishment, draft and approve an exact purchase commitment, and keep expected stock separate from on-hand while an agent prepares evidence. 05 exact purchase approval and agent preparation leave expected separate LOCAL PROVEN
6 Receive a purchase partially into a named bin, record exact cost, retry safely and reject a bad multi-line receipt without partial posting. 06 partial receipts and failed multi-line receipt are atomic LOCAL PROVEN
7 Reverse a receipt safely or use a captured, approved physical count to post a receipt-linked correction when downstream movements exist. 07 receipt reversal preserves original evidence and guards reservations LOCAL PROVEN
8 Transfer stock through transit, keep transit unavailable, receive it at the destination and conserve the quantity. 08 transfer conserves stock and transit cannot be sold LOCAL PROVEN
9 Dispatch part of an order using only that order's reservations, retain shipment links and retry without a second stock decrement. 09 partial dispatch consumes only owned reservations and retries once LOCAL PROVEN
10 Cancel only unshipped demand, preserve shipment history and receive returns into quarantine until separately reviewed restocking. 10 cancellation preserves shipment and returns remain quarantine until review LOCAL PROVEN
11 Count against a captured movement frontier and require a new review when an intervening movement makes the count stale. 11 count frontier prevents overwriting intervening movement LOCAL PROVEN
12 Investigate balances through movement and review history, export records and costs, and restore the complete installation into a fresh local D1 while requiring a new native session for the retained owner. 12 investigation export preserves every ledger and review link; tests/api/security-import.test.mjs: empty downstream import undo restores native snapshot and retains custody; tests/portable.mjs: fresh-install archive restore preserves journals and command outcomes, replays an unchanged import as a no-op, and accepts a new transaction LOCAL PROVEN

Local proof includes rer check and the current rer verify wall (build, typecheck, the 18-test Worker/D1 API suite, native email-flow checks and independent-dependencies portability), focused API and repair probes, and both owner browser journeys in tests/browser/journey.spec.ts at 1440px and 390px. tests/portable.mjs verifies a fresh-install archive restore, an unchanged import replay and a new transaction. Focused probes cover item/location and supplier-term immutability, strict CSV parsing, duplicate opening rejection, import capacity admission, dependency-safe undo and count frontiers. Capacity receipts include a 482,065-byte, 375-item catalogue that committed and undid successfully, and 514,215-byte and 905,215-byte imports rejected with IMPORT_SIZE without changing state or posting business effects.

Scope and boundaries

The local tests exercise authenticated HTTP in the real Worker with D1, empty first run, persistence, current-session role checks inside atomic admission, exact arithmetic and failed-admission atomicity. Browser tests cover the owner-facing desktop and mobile journeys. The four agent preparations—replenishment, shortage reallocation, count drift and migration—retain assumptions, evidence and exact versions; the relevant buyer, operator, warehouse person or owner must approve each exact consequence. An agent cannot self-approve, write stock, reprioritize reservations or send to suppliers.

Native CSV preview, row-group review, unchanged reimport, changed-row revision, strict parsing, duplicate opening rejection, exact reservations.csv allocation, safe undo and dependency-preserving correction are locally proven against the contract in IMPORT.md. Native exit/import behavior preserves approved per-line/bin allocation and explicit zero backorders; the native snapshot does not restore complete movement, shipment, receipt-cost or transit history. Synthetic fixtures in tests/api/security-import.test.mjs are authored examples of Pier's native CSV contract, not external-provider exports or provider-mapping verification. Complete installation archive restore is a separate, locally proven path from business JSON export and CSV migration. This local acceptance does not establish hosted deployment, provider integration, owner-export completeness, physical counts or legal name clearance. No hosted deployment was accepted this round.

The 14 October 2026 style pass changed presentation only: both browser journeys passed again on the restyled screens at 1440px and 390px, every journey label and route unchanged, and CI builds the run site (rer build --site), which refuses broken, instance-only or other-origin links. A LOCAL PROVEN status means the local behavior was exercised through its named API, browser or portability path; preserve hosted, provider, owner-export, legal and physical-stock boundaries separately.