What's New

Each invoice email now carries a unique identifier in its headers, preventing Gmail from collapsing multiple invoices into a single conversation thread. Customers will now see every invoice as a separate, clearly distinguishable message in their inbox instead of a single collapsed thread.

The sidak inspection workflow has been simplified by removing the draft and finalized states:

• Always-editable records: Inspection records can now be saved and updated at any time. Previously, records were created as drafts and had to go through a separate finalization step before being considered complete, and finalized records could not be edited at all.
• Simpler workflow: The separate "Finalisasi" action has been removed entirely. Inspectors only need to save their work, with no risk of getting locked out of their own records.
• Database cleanup: The status tracking columns have been removed, reducing complexity in the data layer.

A complete sidak (spot-audit) module is now available in the CRM sidebar, allowing head inspectors to evaluate field inspectors against a standardized 55-item checklist.

• 55-item checklist grouped into 15 evaluation aspects: Each item can be marked as Sesuai (compliant), Perlu Perbaikan (needs improvement), or Belum Dicek (unchecked), with a score from 1 to 10 for graded items
• Automatic grading: The system calculates an average score and assigns a grade: A (Sangat Baik), B (Baik), C (Perlu Pembinaan), or D (Teguran Resmi)
• List page: All sidak records appear in a table (desktop) or card layout (mobile) with grade badges, inspector name, customer, vehicle plate, and status
• Create flow: Pick a booking, select an inspector, set date and time, then fill the full 55-item checklist on the detail page
• Draft and finalize workflow: Records start as drafts that can be saved and revisited. Finalization locks the record permanently and requires all 55 items to be checked
• Finding notes and follow-up: Items marked "needs improvement" prompt for a written finding and a follow-up action plan

Each page in the CRM now enforces its own permission check instead of relying on a single gate at the layout level.

• Smart landing page: After login, users are redirected to the first module they have permission to access, instead of always landing on Bookings
• Users without access see a clear message: If someone has no permissions for any module, they see a message telling them to contact their administrator instead of a blank page
• Logo links to the right home: Clicking the Palapa logo in the sidebar now navigates to the user's first accessible page
• Dynamic page titles: The header now displays the correct page title (e.g., "Bookings" or "Sidak") based on the current route

Invoice generation and email sending now use prominent toast notifications instead of small spinning icons on the buttons.

• Invoice download: Clicking the invoice button shows a toast ("Membuat invoice...") that updates to a success message when the PDF is ready and automatically downloads
• Email sending: The send email button triggers a loading toast ("Mengirim invoice...") with a success or error message once the email is dispatched
• No more button state confusion: Previously, the button text and icon changed during loading, which was subtle and easy to miss. The toast approach makes the status clearly visible

The Laporan Cepat dashboard now checks permissions for each route individually, so users only see the modules they are authorized to access.

• Per-route permission checks: Review, user management, inspector management, and branch pages each require their own specific permissions instead of a blanket dashboard access
• Smart redirect after login: Users land on the first page they have access to (e.g., a user with only review permissions goes straight to the review page)
• Access denied page: Users without any module permissions see an "Akses Ditolak" screen with a message to contact the administrator
• Breadcrumb "Home" links correctly: The home breadcrumb in the header navigates to the user's first allowed page instead of always pointing to the dashboard root

Head inspectors can now create sidak records before an inspection is completed, removing a workflow bottleneck where spot audits had to wait for the full inspection to finish.

• Inspection is no longer required: The inspection link in a sidak record is now optional, so a sidak can be created while the inspector is still on-site
• Direct data entry: Customer name, vehicle details, inspection location, and inspector name are entered directly by the head inspector instead of being pulled from other database records
• Validation remains strict: All required fields (customer name, vehicle plate, vehicle unit, location, inspector name, date, and time) must still be provided before saving

Invoice emails are now sent through Resend, a dedicated email delivery service, replacing the previous self-managed SMTP connection.

• Professional sending domain: Emails are sent from cs@palapainspeksi.com through Resend's infrastructure instead of a personal Gmail SMTP connection
• Simpler configuration: The system now needs only an API key and a sender address, removing the need to manage SMTP host, port, username, and password separately
• More reliable delivery: Resend handles deliverability, bounce handling, and rate limiting, reducing the chance of invoices ending up in spam

The bookings management page now enforces role-based access control, so only authorized staff can view and manage customer bookings. Several improvements also make daily workflow smoother:

• Permission-gated access: The bookings page is now protected by user permissions. Staff without the appropriate role are blocked from viewing customer data, with a clear message directing them to log in with the right account. Menu items in the sidebar are also hidden for users who lack the required permissions.
• Real user identity in sidebar: The sidebar now displays the logged-in user's actual name and email instead of a generic "Admin" placeholder, making it easy to confirm which account is active when multiple people share the system.
• Email preview before sending: When sending an invoice to a customer via email, admins now see a preview of the full email content, including the recipient address, subject line, and body text, before confirming delivery. This prevents accidental sends with incomplete information.
• Today's bookings by default: The page now opens with today's date pre-selected as a filter, so staff immediately see the day's incoming bookings without having to manually set the date each time.

The system can now generate an invoice PDF and email it to the customer in one step, instead of requiring staff to download and forward it manually.

• Automatic email delivery: When triggered, the system generates the invoice PDF, composes a professional email with the customer's name, attaches the PDF, and sends it from the company's email address
• Professional email template: Customers receive a personalized message with Palapa's branding, complete with customer service contact info and website details
• Smart validation: The system blocks sending when no email address is on file for a booking, preventing failed deliveries

Each booking now has a one-click Invoice button right in the action row, so admins can download a finished PDF without leaving the page:

• One-click download: Clicking the Invoice button immediately generates and downloads a ready-to-send PDF, eliminating the need to navigate to a separate tool or page
• Automatic package check: The button is disabled for bookings that do not yet have a package assigned, preventing empty or broken invoices from being created
• Works on every screen size: The button appears on both the card layout (used on mobile) and the table layout (used on desktop), keeping the workflow consistent across devices

Two improvements to how pricing and invoices are handled behind the scenes:

• Fixed-price packages fill automatically: When a package has only one set price (no range), the system now fills it in without any manual input, saving time and eliminating a source of data-entry mistakes
• Variable-price packages require confirmation: Packages with a price range now demand an explicit price before the booking can be saved, preventing bookings from going through with missing or zero pricing
• Invoice generation guard: Trying to generate an invoice for a booking that has no package attached now returns a clear error instead of producing a blank or broken PDF

Write actions across the inspection review interface are now gated behind permission checks, so only authorized staff can modify data:

• Merge and delete buttons on the review header are hidden from users without the update permission, preventing unauthorized changes to inspection records
• Save button in the bottom action bar is gated behind the same permission, allowing users without access to view inspections in read-only mode
• All inspection review pages (vehicle data, inspection summary, repair estimates, feature checks, photos, paint thickness) automatically switch to read-only when the user lacks update permission
• Photo editing controls (saving label changes and deleting photos) are restricted to users with dedicated photo write access
• Blockchain minting button in the inspection table is only shown to users who have inspection update permission

A new invoice generation tool automatically creates branded PDF invoices from CRM booking records:

• Automatic invoice creation pulls customer name, address, phone, email, vehicle details, inspection schedule, and pricing directly from the booking into a formatted PDF
• Branded template uses the Palapa logo and Figtree font family, with company details (PT. Inspeksi Mobil Jogja, address, phone, email) in the header
• Auto-generated invoice numbers follow the format INV/YYMMDD/NN, sequenced daily based on booking creation time, so every invoice has a unique and traceable reference
• Complete pricing breakdown shows unit price, subtotal, discount, transport fee, and grand total, all formatted in Rupiah
• Two-column layout clearly separates the company sender details from the customer recipient details
• Payment instructions in the footer prompt customers to confirm payment with the admin

Access control across the dashboard has been upgraded from broad role-based checks to a granular permission system, making it possible to control exactly which features each user can access.

• Granular access per feature: Each page and action now checks for a specific permission (e.g., "read branches," "write users") instead of relying on broad roles. Access can be granted or revoked per feature without changing someone's overall role.
• Permission-aware menus and buttons: The sidebar only shows pages the user has permission to visit. Action buttons for adding, editing, deleting, and exporting are automatically hidden from users who lack the matching write or export permission.
• Customer Service dashboard access: Customer Service staff can now access the dashboard, matching their updated permission set in the backend.
• Cleaner sidebar design: Both the desktop and mobile sidebars have been visually refreshed with a more compact layout and smoother styling.

• Auto-paginated repair estimates: The Estimasi Perbaikan section now automatically splits across multiple pages when the content is too long for a single page, instead of overflowing. Categories are redistributed evenly so each page has a balanced amount of content.
• Descriptive navigation labels: Report preview pages now show meaningful names (Data Kendaraan, Ringkasan Inspeksi, Fitur & Mesin, Ban Test Drive & Tools Test, Ketebalan Cat - Part 1, etc.) instead of generic labels like "Halaman 1" and "Halaman 2". The page count in the sidebar and progress bar updates dynamically to reflect the actual number of pages.
• Smart grand total placement: The overall repair cost total and disclaimer footnote only appear on the final Estimasi Perbaikan page, avoiding redundant totals on intermediate split pages.

• Transparent session renewal: When a user's login session expires, the system now silently refreshes it in the background and retries the failed request. Users will not notice anything unless the refresh itself fails.
• Only redirects to login as a last resort: If the session cannot be renewed, the user is sent to the login page with a clear "session expired" message instead of encountering a cryptic error.
• Works across all actions: The refresh logic applies to both regular data requests and file downloads, so users won't lose progress mid-download due to a quietly expired session.

The admin dashboard has been rebuilt with a proper sidebar layout, matching the structure used across other Palapa products:

• Collapsible sidebar: A sidebar on the left with the Palapa CRM logo, a "Bookings" navigation link, and a user profile menu with logout at the bottom. On mobile, it opens as a slide-out sheet instead of taking up screen space.
• Top header bar: A slim header with a sidebar toggle button and "Bookings" page title replaces the old tall sticky bar that contained the title, logout button, and all filter controls.
• Inline page controls: Search bar, date filter, and items-per-page selector now sit within the page content area with proper padding, making better use of available screen space.
• Redesigned login page: The login screen now uses a clean centered layout with the Palapa CRM logo and branding, replacing the old card-based "Admin Login" design.
• Consistent theming: Colors throughout the dashboard have been updated from hardcoded gray values to semantic design tokens, improving visual consistency and enabling proper dark mode support.

The CRM admin panel now reads from and writes to the Laporan Cepat backend, replacing the old Google Sheets-based system:

• Dynamic package list: Inspection packages are loaded from the server instead of being hardcoded in the code. When a new package is added to the system, it appears in the CRM dropdown automatically with no code deployment needed
• Custom quoted price per booking: Admins can now set a specific price for each booking. Packages with a fixed price auto-fill the amount, while range-priced packages let the admin pick a value within the range
• Password visibility toggle: The login page now has an eye icon to show or hide the password, making it easier to verify credentials before submitting
• Better performance on large datasets: The booking list now uses a more efficient pagination approach, so browsing through hundreds of records feels snappier

• Customer service accounts can now authenticate: Previously, the login system only accepted admin, reviewer, and inspector head credentials. Customer service staff with valid accounts were blocked from logging in even though they had been created in the system
• Automatic CRM permissions: The customer service role now has built-in access to the dashboard, booking management, package information, and inspection records, so newly created staff accounts are ready to use immediately
• Safer user edits: Updating a user's profile now only changes the fields that were actually modified. Editing a name no longer accidentally resets the email or role if those fields were left blank
• Dashboard error recovery: If something goes wrong inside the dashboard, the page now shows a "Something went wrong" message with a retry button instead of a full-screen crash. The sidebar and navigation remain visible so users can navigate away
• Clearer login feedback: The login and registration flows now show a loading indicator with a success or error message, so users know exactly what happened instead of seeing a silent pause

The mobile app was sending a mismatched field name for the photo attention flag, causing flagged photos to not be properly highlighted on the server side.

• Corrected field name: The app now sends isAttentionNeeded to match the server's expected format, so photos flagged during inspection are properly marked
• Released as version 3.0.3 to ensure all inspectors get the fix promptly

Older versions of the inspector app send the attention flag with a different field name than the server expects. This PR makes the server handle both formats gracefully.

• Backward compatibility: Inspectors who haven't updated yet can still flag photos as needing attention, and the flag is recorded correctly
• Automatic normalization: Both isAttentionNeeded and needAttention are accepted, with the newer format taking priority when both are present
• Zero downtime migration: No forced app update required; the server works with both old and new versions simultaneously

Reviewers were previously restricted to basic summary stats on the dashboard. They can now see the complete analytics view.

• Trend charts: Reviewers can switch between bar and line charts to track inspection volume over time
• Branch distribution map: Visual breakdown of inspections across all branches is now visible to reviewers, not just admins
• Inspector performance table: Reviewers can see how each inspector is performing, helping them prioritize review work
• Loading state fix: A separate bug was also fixed where a failed data fetch would incorrectly mark the dashboard as loaded, showing a blank page instead of a proper error

Inspector-related actions (viewing, creating, editing inspectors and their PINs) previously shared the same permission as general user management. They now have their own dedicated permissions.

• Customer service gains attendance access: Staff can now clock in and out directly, instead of relying on admins to record their attendance
• Inspector heads gain attendance access: Field leaders can now record their own attendance alongside their team
• Tighter access control: Inspector heads can still manage inspector accounts and PINs, but can no longer view or edit general back-office user accounts, matching their actual responsibilities
• Admins retain full access: No changes to what admins can do; all existing capabilities are preserved

Form data entered by inspectors is now saved proactively during the inspection flow, closing a gap where work could be lost if the app was closed unexpectedly.

• Save on every step: Draft data is now saved immediately when an inspector swipes between form steps, instead of only when the app goes to the background. Previously, closing the app mid-inspection could lose everything entered on the current step.
• Crash-safe file writes: All saved data now uses atomic writes (write to a temporary file first, then rename). If the app crashes or is killed mid-save, the original data remains intact and is never corrupted.
• Automatic cleanup: Orphaned temporary files from interrupted saves are automatically cleaned up the next time the app loads that data, preventing storage bloat over time.
• Faster background saves: When the app goes to the background, all form sections now save in parallel instead of one at a time, reducing the time the app needs before it can be safely suspended.

Inspection preview reports no longer include an unnecessary blank page at the end of photo sections, producing cleaner printed and exported documents.

All icons across the application have been replaced with a new, consistent icon set, and the admin management pages have been cleaned up to remove unnecessary visual clutter.

• New icon system: Replaced two separate icon libraries (Lucide and React Icons) with a single Hugeicons set, ensuring every icon looks and behaves consistently across the login page, dashboard, sidebar, dialogs, charts, and public-facing pages.
• Cleaner management pages: The branch, inspector, and user management pages had their decorative header cards (gradient backgrounds, large icons, subtitle text) removed in favor of simple, bold page titles, giving the admin area a more professional and less cluttered appearance.
• Removed unused stats cards: The branch management page no longer shows decorative stat cards (total branches, cities) that duplicated information already visible in the table below them.

Inspectors can now record detailed tire data for each wheel position on a dedicated page, replacing the old single-line fields.

• Each of the four positions (front right, front left, rear right, rear left) captures tire size, brand, type (tube vs. tubeless), and year
• A new visual slider lets inspectors dial in tire thickness as a percentage, color-coded from red (worn) to green (good), making it quick and intuitive to enter
• All fields are validated before submission, so incomplete tire records are caught before the form is sent

This is part of the Inspector Form version 3.0 release, a major update that restructures how tire and repair data flows through the inspection workflow.

Repair cost estimates now have their own dedicated page, organized into five vehicle sections instead of a single flat list.

• Estimates are grouped by Fitur, Interior, Eksterior, Mesin, and Kaki-kaki, matching how the rest of the inspection is structured
• Each section supports multiple line items with part name and price, so inspectors can break down costs precisely
• The form checks that every line item has both a part name and a price filled in, flagging incomplete rows before submission

This is part of the Inspector Form version 3.0 release.

The inspection report preview now reflects the new data structure from the mobile app, with dedicated sections for tire data and repair estimates.

• Tire data is displayed as a structured table showing all four wheel positions with their size, brand, thickness, type, and year
• Repair estimates have been moved to their own report page, grouped by vehicle section with subtotals per category and a grand total at the bottom
• The review and edit workflow has been rebuilt with a more reliable path-based system that handles nested data (like individual tire positions) correctly

Inspectors could accidentally submit the same report twice, for example by tapping the submit button multiple times or if the app restarted mid-submission. This is now handled reliably on the server side.

• Each submission is assigned a unique key that is saved to the device, so it survives app restarts. If the same report is sent again, the server recognizes it and does not create a duplicate.
• The old approach relied on comparing form data on the device itself, which could miss duplicates after an app restart. The server is now the single source of truth for preventing repeated submissions.
• After a successful submission, the key is automatically cleared so the next inspection starts fresh.

The customer-facing inspection form now loads faster and handles errors more gracefully, especially for users on slower connections.

• The form font is now bundled directly instead of loaded from an external service. This removes three network requests on page load and ensures the form displays immediately even with poor connectivity.
• Dropdown menus and radio buttons now save and reset properly. Previously, selecting an option and then submitting again could show stale selections.
• Form fields validate as users leave each field rather than only after clicking submit, catching mistakes earlier in the process.
• Requests that take longer than 30 seconds are automatically canceled so users are not left waiting indefinitely on a stuck submission.
• If the form encounters an unexpected crash, users now see a recovery screen with a retry button instead of a blank page.

Added deduplication protection for inspection submissions so that retrying a failed request does not create a second, duplicate inspection.

• Inspectors working in areas with poor connectivity sometimes experience upload failures and tap submit again. Previously, each retry created a brand-new inspection record, leading to duplicates that had to be manually cleaned up.
• The mobile app now generates a unique key for each submission attempt. If the server receives the same key twice, it returns the original inspection instead of creating a new one.
• Duplicate prevention is scoped per inspector, so two different inspectors can still submit separate inspections simultaneously without conflict.

After an inspector submits a report, the app now navigates to the success screen immediately instead of waiting for draft data to be cleared.

• Previously, the app cleared all saved form data (vehicle info, photos, inspector identity, etc.) before showing the success page. On slower devices or large reports, this caused a noticeable delay between tapping submit and seeing the confirmation.
• Draft cleanup now runs in the background after the success page is already visible. Inspectors get instant feedback that their submission went through.
• Orphaned temporary image files are also cleaned up automatically as part of this process, freeing up device storage without any action from the user.

The "Selang" (hose) field in the engine inspection section has been renamed to "Baut Kap Mesin" (engine cap bolt) to match the updated inspection standard.

• Existing inspection data is automatically migrated — older records that still use the old field name are converted on the fly, so reports and detail views display the correct label without any manual fix
• CSV exports also use the updated field name, keeping downloaded reports consistent with what appears on screen
• A one-time backfill tool was added to permanently update all historical records in the database, ensuring long-term data consistency

Added full CRUD API endpoints for managing user roles, so admins can create, view, update, and delete roles without direct database access.

• Five new endpoints under /roles, all restricted to admin users only
• Role names are normalized to lowercase and validated for uniqueness
• Deleting a role is blocked if there are still users assigned to it
• Includes a repository layer with raw SQL queries against the existing roles table

Removed the walletAddress and whatsappNumber fields from inspector accounts throughout the entire stack.

• A new database migration drops both columns and their unique index from the users table
• All backend SQL queries, repository methods, service logic, and DTOs were cleaned up
• The frontend user management and inspector pages no longer show wallet or WhatsApp inputs
• Removed the orphaned createInspectorUser Redux thunk that was never called
• The staging data copy tool was updated to match the new schema

Replaced the Azure Face API dependency with a local InsightFace service for attendance face recognition:

• Face embeddings are now stored directly in PostgreSQL as vector arrays instead of relying on Azure's faceId references
• The system supports both InsightFace and Azure as providers, auto-detected from environment variables, making it easy to switch or fall back
• A new InsightFaceVerifier implementation calls a local Python service with /detect and /verify endpoints
• Database migration updated the user_face_profiles table to store reference_embedding (real array) instead of reference_face_id

• Inspector login no longer queries face enrollment status, speeding up the login flow
• Attendance recording now logs structured fields for every event: distance from office, face match confidence, threshold, and whether verification passed
• Fixed a bug in photo file extension handling that could produce incorrect file paths

A significant round of UI and architecture improvements to the Attendance web app:

• Added a dark/light theme toggle across all pages (login, attendance, admin dashboard)
• Attendance recording now uses a simplified action sheet flow: tapping an action button opens a bottom sheet for selfie capture, reducing visual clutter
• The camera starts and GPS is requested automatically when the action flow opens, instead of requiring manual steps
• Mobile vs web source is auto-detected from the user agent, including iPad and touch-enabled Macs
• Extracted reusable components: ThemeToggleButton, LogoutButton, and LanguageToggle are now shared across pages
• Replaced inline error banners with toast notifications for a cleaner experience
• Added a Dockerfile with multi-stage builds for containerized deployment
• Mobile sidebar now auto-closes when a navigation link is tapped
• Admin dashboard header now shows dynamic page titles based on the current route

Restructured the admin interface into a proper dashboard with a sidebar navigation:

• Attendance monitoring moved from the /admin route to a new /dashboard route with a dedicated sidebar layout
• Added reusable UI components including sidebar, breadcrumbs, user nav, and mobile-responsive drawer
• Individual user attendance detail view now lives under /dashboard/users/[userId]
• Dark mode toggle and improved overall navigation structure

Implemented a full internationalization (i18n) system so users can switch between English and Indonesian:

• Built a custom i18n provider with browser-language detection and localStorage persistence
• Added a language toggle button in the header bar next to the dark mode switch
• Translated all attendance pages: check-in/out, history, enrollment, user detail, and dashboard monitor
• Extracted shared date/time formatting into locale-aware utilities (lib/date.ts) for consistent Jakarta timezone display in both languages
• Added unit tests for the i18n provider (Vitest + Testing Library)

After logging out, the app now immediately navigates to the login page using a full page redirect, preventing stale session state from causing issues.

Pages now wait for the auth bootstrap to complete before checking authentication state, eliminating a race condition where authenticated users were briefly redirected to the login page on page load.

Added a token validation step at the start of the auth bootstrap flow, matching the main Laporan Cepat frontend's pattern of validating the access token before loading the user profile.

Three related bug fixes for the photo processing and app update pipelines:

• Duplicate APK uploads now succeed silently. Previously, uploading the same app version twice returned an error. The file is now replaced in object storage while the existing database record stays untouched.
• Fixed SIGSEGV crash in govips image compressor. Removed ClearCache and ShutdownThread calls that were corrupting thread-local state, causing the test suite to crash. Memory was already configured to not persist between operations, so these cleanup calls were unnecessary.
• Fixed unreliable compression test. The test payload was too small (10 bytes) to exceed the 75KB threshold that gates compression job enqueueing, so the test was never actually testing what it claimed to. Replaced with an 80KB payload.

Initial release of the Palapa Attendance web app built with Next.js and shadcn/ui:

• Attendance recording page where inspectors can check in/out, take lunch breaks, and submit selfies with GPS location for verification
• Face enrollment flow for new users to register their reference face photo
• Admin dashboard with a real-time overview table showing all inspectors' attendance status for the day, date picker for historical views, and per-user detail pages
• Login page with authentication, role-based access control, and automatic redirection
• Attendance history page for viewing past records

Face enrollment now uses a live camera feed directly in the browser instead of asking users to upload a photo file. This provides a smoother, more consistent enrollment experience across devices and ensures the photo is taken with the correct camera orientation on the spot.

Inspector Head is now a first-class role with the same access level as Admin across the dashboard, user management, branch management, inspections, and cleanup jobs. The role has its own distinct label and display name throughout the app while sharing admin-equivalent permission checks behind the scenes.

The camera preview now fills the full width of the screen properly on all devices.

Tap-to-focus has been added:

• Tap anywhere on the preview to focus on that area
• A visual indicator shows where the camera is focusing
• Lock focus on a specific point using the lock button, useful for tricky angles or close-ups
• Focus resets automatically when switching between cameras

Switched the server's photo compression engine from Go's built-in library to libvips, the same image processing library used by Instagram and WhatsApp. This significantly reduces peak memory usage when processing photos, which means the server can handle more concurrent uploads without running out of memory. Memory is also released immediately after each photo is processed.

Added smart checks to avoid wasting resources on photos that don't need compression:

• Small photos (under 75 KB) are kept as-is since they're typically thumbnails or already optimized
• Incompressible photos — if compression doesn't make the file any smaller, the original is kept instead

Both checks run automatically during upload, replacement, and batch processing.

User accounts can now be deactivated instead of deleted. This preserves all historical inspection data linked to the account while preventing the user from logging in. The system also records which admin performed the deactivation for accountability.

Fixed a bug where unchecking an item in the equipment checklist (like "Kunci Serep" or "BPKB") would cause that item to silently disappear from the saved inspection data. The system was incorrectly treating unchecked items as missing data and dropping them entirely. All 11 checklist items now save correctly regardless of their checked state.

Inspectors can now track two additional documents in the equipment checklist:

• Faktur (vehicle purchase invoice)
• NIK Sertifikat (certificate identity number)

The fields are tracked end-to-end from the inspection form through to the final report and CSV exports. The checklist was also refactored so new items can be added more easily in the future.

The backend now has a proper logging system that tracks every API request with full context:

• Logs automatically switch between a readable format for developers and structured data for production monitoring
• Every request is recorded with the method, endpoint, response time, and which user made it
• Failed login attempts now log the specific reason (expired token, wrong role, etc.) instead of a generic error
• Error messages identify the action that failed (e.g., "inspection update failed") instead of just "request failed"

On the frontend, the review editing workflow was also improved to handle empty data more safely.