pelagia-portal/CHANGELOG.md

Changelog

[Unreleased]

Added

• Reports — Purchasing spend analytics (view_analytics: Manager / SuperUser / Auditor / Admin) — /reports/cost-centres and /reports/accounting-codes, each an index → drill-down → detail. KPI tiles, comparison + trend charts (one colour per item), Top-N tables, per-row sparklines, and CSV export; URL-driven filters (granularity Weekly / Monthly / Yearly, financial year, Top/Bottom-N, an "Add to graph" custom comparison). Spend = post-approval POs by approvedAt/totalAmount, allocated across each PO's line-item accounting codes. Pure, unit-tested core in lib/reports.ts.
• Email PO to vendor (issue #14) — one-click Outlook draft to the vendor's primary contact with a 7-day download link to the PO PDF. Rendered by the new PdfService microservice (Express + Playwright → headless Chromium) and stored in R2; the PDF is cached per PO, so repeat sends reuse the copy and only refresh the link.
• Microservices — EpfoService (UAN / EPFO assisted-lookup proxy; live portal nav stubbed behind EPFO_LIVE) and PdfService (PO → PDF) join GstService. All three are auto-deployed on each release tag via the root ecosystem.config.js + deploy.yml (pm2 startOrReload … --update-env).
• Unsaved-changes prompt (issue #18) — leaving the PO create/edit screen with unsaved edits offers Save as draft / Discard / Stay (in-app navigation) or the browser's native warning (refresh / close).
• Crew login on hire (crewing, feature-flagged) — onboarding, direct placement, and admin crew-create accept an explicit login email + initial password for management ranks (Rank.grantsLogin), creating the SITE_STAFF login in one step.
• Delivery Locations (issue #19) — admin-managed Company+address list backing the PO "Place of Delivery" dropdown, gated by manage_delivery_locations (Manager / SuperUser / Admin).
• Terms & Conditions catalogue (issue #11) — admin-managed, user-defined T&C categories + clauses feeding a dynamic PO terms editor; the chosen rows are a JSON snapshot on PurchaseOrder.terms.
• Advance payment on approval (issue #92) — the approving Manager sets how much is paid first; the resolved absolute amount is stored on PurchaseOrder.suggestedAdvancePayment and prefills the first Accounts payment.
• Companies (multi-company invoicing) — new Company model and /admin/companies CRUD. A PO is billed under a selected company (name, short code, GST number, address, phone/mobile, contact + invoice email, invoice address). The company's details populate the exported PO header / invoice block.
• Structured PO numbers (lib/po-number.ts) — COMPANY/VESSEL/ID/FY (e.g. PMS/HNR1/9000/2024-25); Indian financial year; system-generated IDs start at 9000. Imported POs keep their original number.
• 3-level accounting-code hierarchy — Account.parentId self-relation (Top Category → Sub-Category → Leaf), 6-digit numeric codes seeded from prisma/accounting-codes-data.ts. Only leaf codes are PO-selectable, via a searchable, portal-rendered combobox.
• Compulsory payment date — PurchaseOrder.paymentDate captured when Accounts records a payment; defaults to today, rejects future dates. Backfilled for existing POs from paidAt / the first payment action.
• Editable PO date (poDate) — the exported PO "Date" now shows poDate ?? approvedAt ?? createdAt (approval date once approved, not creation).
• Submitter vendor creation — create_vendor permission lets Technical/Manning add vendors; they are created unverified and become verified when a PO closes/pays with them, on import, or via Manager/Accounts/Admin (verifyVendor).
• Import PO → Closed — /po/import saves a parsed Excel PO directly as CLOSED, auto-detecting the company, matching the vessel by code, and auto-creating the vendor, products, and per-vendor prices.
• Inventory feature flag (NEXT_PUBLIC_INVENTORY_ENABLED) — site stock/consumption surfaces are gated; the vendor/item catalogue for PO creation stays available. Inventory is incremented at PO approval (not on close).
• Dashboards — Accounts gains a "Payments Completed This Month" card.
• Automated issue-to-deploy pipeline — end-to-end flow from a user-reported bug to a production fix without manual intervention on the developer's part:
  • Report Issue button (App/components/layout/report-issue-button.tsx) — any signed-in user can file a bug from the portal header; the server action (report-issue-actions.ts) calls the Forgejo API and attaches portal + claude-queue labels.
  • Claude issue watcher (automation/claude-issue-watcher.ps1) — a Windows Scheduled Task (PelagiaClaudeIssueWatcher) polls Forgejo every 10 minutes, picks up claude-queue issues, and runs Claude Code headlessly to implement and verify a fix. On success the watcher pushes a claude/issue-N branch and opens a PR; on failure it posts a comment and labels the issue claude-failed.
  • Tag-triggered deploy workflow (.forgejo/workflows/deploy.yml) — pushing a v* semver tag triggers the host Forgejo runner on pms1, which checks out the tag, runs pnpm install, builds the app, applies Prisma migrations, and restarts the pm2 process ppms.

Changed

• Cost centre is now a Vessel only. The earlier Vessel-or-Site cost-centre model was removed: PurchaseOrder.vesselId is required, the costCentreRef encoding is gone, and Vessel no longer links to a Site. Vessels are surfaced as "Cost Centre" throughout the UI (/admin/vessels → "Cost Centre Management").
• Closed Purchase Orders list: submitters see only their own CLOSED POs; Managers/SuperUsers see all CLOSED POs.
• Sidebar reorganised into Purchasing and Administration sections (role-aware); "Inventory" renamed to "Purchasing".
• Items: /admin/products is the editable catalogue; /inventory/items is read-only; both link to a shared item detail page.
• Profile page is reachable by every role (incl. SSO-only / no-password users, with an email fallback lookup); only approvers can upload an approval signature.
• Manager dashboard "Approved This Month" now counts by approvedAt (no longer undercounts once a PO progresses past MGR_APPROVED).

Fixed

• "Email to vendor" never rendered a real PDF (issue #14) — the auth middleware redirected PdfService's unauthenticated svc-token export fetch to /login before the route's token check ran, so the bypass never executed. /api/po/<id>/export is now allowed through when its svc token matches PDF_SERVICE_TOKEN (lib/pdf-export-auth.ts); everything else stays auth-gated.
• Reports comparison charts all rendered one colour — SERIES_COLORS lived in a "use client" module and was imported by the server-component report pages, where a plain value becomes a client-reference proxy (so SERIES_COLORS[i] was undefined and recharts fell back to its default stroke). Moved the palette to a dependency-free shared module (lib/report-colors.ts).
• Production P2022 … column does not exist after deploy — caused by shipping code whose Prisma client expected a column before migrate deploy had run. Migrations must be applied before the new build serves traffic (now documented in the README).