Kc Wednesday Ship Rehearsal Checklist 2026 03 02

# KC Wednesday SHIP Rehearsal Checklist (2026-03-02)
 
Purpose: run and record pre-meeting validation for KnifeCenter SHIP operations flow.
 
Scope: customer-operator path from upload through claim lifecycle and reporting export.
 
## A. Automated Rehearsal Evidence (Completed)
 
Date: 2026-03-02
Runner: Codex (local repo validation)
 
1. SHIP claim/workflow contract checks
- Command:
  - `pnpm --filter @rgl8r/api test -- --runTestsByPath src/__tests__/contracts/api-contracts.test.ts --testNamePattern="SHIP claim submissions|SHIP workflow contracts|SHIP findings API contracts"`
- Result: PASS
- Evidence highlights:
  - Claim submission lifecycle contracts pass (`create`, `generate-packet`, `submit`, `acknowledge`, `confirm-credit`)
  - Required `externalReference` validation enforced (`submit`, `acknowledge` return 400 when missing)
  - Batch credit migration guard remains enforced (`400` with remediation)
 
2. SHIP claims web proxy route wiring checks
- Command:
  - `pnpm --filter @rgl8r/web test -- --runTestsByPath src/__tests__/api/ship-claims-routes.test.ts`
- Result: PASS
- Evidence highlights:
  - Proxy routes wired for submission list/detail and all lifecycle actions
  - UUID validation enforced for `submissionId` params
 
## B. Manual Staging Rehearsal (Required Before Wednesday Walkthrough)
 
Run this in staging with the KC Clerk user and synthetic data only.
 
1. Sign-in and access
- [ ] KC user can sign in.
- [ ] `/freight-audit`, `/ship/audit`, `/ship/claims`, `/reporting`, `/notifications` load successfully.
 
2. Shipment upload and findings generation
- [ ] Upload synthetic shipment CSV in `/freight-audit`.
- [ ] Job completes successfully.
- [ ] Findings appear in `/ship/audit`.
 
3. Finding lifecycle checks
- [ ] Move one finding `OPEN -> DISPUTED`.
- [ ] Move the same finding `DISPUTED -> SUBMITTED`.
- [ ] Move `SUBMITTED -> CARRIER_REVIEW`.
 
4. Claim submission lifecycle checks
- [ ] Create submission in `/ship/claims` with at least one eligible finding.
- [ ] Generate packet (`DRAFT/READY -> READY`).
- [ ] Submit claim (`READY -> SUBMITTED`) with required carrier claim/ticket `externalReference`.
- [ ] Acknowledge claim (`SUBMITTED -> ACKNOWLEDGED`) with required carrier acknowledgement `externalReference`.
- [ ] Confirm credit (`ACKNOWLEDGED -> CREDIT_CONFIRMED`) with full confirmation payload:
  - `confirmation.source`
  - `confirmation.referenceId`
  - `confirmation.confirmedAt`
  - amount > 0
 
5. Reporting and export checks
- [ ] KPI and status visibility is correct in SHIP views.
- [ ] CSV export works from `/reporting`.
 
6. Notification and navigation checks
- [ ] SHIP workflow links resolve to `/ship/audit`.
- [ ] Preferences link resolves to `/notifications`.
 
## C. Rehearsal Log (Fill During Staging Run)
 
- Date/time:
- Operator:
- Tenant/org:
- Submission ID(s):
- Finding ID(s):
- Carrier references used (`externalReference`):
- Credit confirmation reference ID(s):
- Any failures and exact error payloads:
- Escalations opened (if any):
 
## D. Go/No-Go Rule
 
Go for Wednesday walkthrough only if Sections B1-B5 pass without blocking errors.  
If any blocking error occurs, capture payloads and escalate to platform-oncall before customer session.