Hardik
8982118eee
First slice of Phase 5 (verification + appraisal). The office queue for verifying site-entered records, per Crewing-Implementation-Spec §8.11/R11. Stacks on 4c. Behind NEXT_PUBLIC_CREWING_ENABLED. What's in - Schema: CrewActionType += RECORD_VERIFIED/RECORD_REJECTED (migration crewing_verification_actions). No model changes — SeafarerDocument/BankDetail/ EpfDetail already carry verificationStatus + verifiedById (3b/4a). - Actions (crewing/verification/actions.ts): verifyDocument (verify_site_records — MPO/Manager) and verifyBankEpf (verify_bank_epf — Accounts) set verificationStatus VERIFIED/REJECTED + verifiedById; rejection requires remarks; each writes a CrewAction. Already-decided records are guarded. - Screen: /crewing/verification — role-aware (MPO: pending documents with expiry flags; Accounts: pending bank/EPF), Verify / Reject-with-remarks. Leave is not here (Manager approval, R11). Verification added to nav (MPO + Accounts + SU, §7). Tests & docs - Integration: verification.test.ts (6) — doc verify/reject + already-decided guard, bank/EPF verify, permission gating (Accounts can't verify docs, MPO can't verify bank/EPF). type-check clean; full unit (241) + integration (201) green (verified with RESEND_API_KEY unset, mimicking CI). - CLAUDE.md updated. Deferred (per decision): PPE / next-of-kin verification gates. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
10 lines
390 B
SQL
10 lines
390 B
SQL
-- AlterEnum
|
|
-- This migration adds more than one value to an enum.
|
|
-- With PostgreSQL versions 11 and earlier, this is not possible
|
|
-- in a single migration. This can be worked around by creating
|
|
-- multiple migrations, each migration adding only one value to
|
|
-- the enum.
|
|
|
|
|
|
ALTER TYPE "CrewActionType" ADD VALUE 'RECORD_VERIFIED';
|
|
ALTER TYPE "CrewActionType" ADD VALUE 'RECORD_REJECTED';
|