Harborlight

What you asked for 0 of 46 checked and working

• R1: Show a public timetable for 6 invented routes with sailing times, boat, duration, seat availability and vehicle availability. Not checked yet Its test passed. The judge hasn't looked yet.
• R2: Let a passenger book seats and a vehicle on a chosen sailing, save the booking so it is still there after a reload, and show a booking code. Not checked yet Its test passed. The judge hasn't looked yet.
• R3: Show and apply fares by season for every route, seat and vehicle, with the season and total clearly shown before confirming. Not checked yet Its test passed. The judge hasn't looked yet.
• R4: Let a passenger enter a booking code and see the booking, sailing, fare, status and any affecting notice. Not checked yet Its test passed. The judge hasn't looked yet.
• R5: Let a passenger cancel a booking from lookup, free the seats and vehicle space, save the cancellation after a reload and create a refund record. Not met "R5: passenger cancels from lookup, seats free and refund saved after reload" did not pass.
• R6: Show a dispatcher console as a live board of 8 boats with current sailing, crews, status, bookings and next departure. Not checked yet Its test passed. The judge hasn't looked yet.
• R7: Let a dispatcher drag a crew member to another boat or sailing to reassign crews and save the change after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R8: Let a dispatcher publish delay and weather notices that immediately update the public timetable, booking lookup and passenger assistant, to notify affected passengers. Not checked yet Its test passed. The judge hasn't looked yet.
• R9: Let a dispatcher pick a day in the dispatcher console and replay its sailings, delays, reassignments, downtime and notices in order. Not checked yet Its test passed. The judge hasn't looked yet.
• R10: Show each crew member a shift calendar by day, week and boat in the crew app. Not checked yet Its test passed. The judge hasn't looked yet.
• R11: Let crew request a shift swap and let an approver approve or decline it, saving the result so it is still there after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R12: Track crew hours, show limits and warn before a shift or approved swap would go over the limit. Not checked yet Its test passed. The judge hasn't looked yet.
• R13: Require a safety checklist before each sailing and save whether the sailing is cleared or blocked, still visible after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R14: Show parts inventory with quantities and low stock state and let mechanics adjust stock, saved after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R15: Let mechanics create, update and complete work orders for a boat and part, saved after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R16: Show a boat downtime calendar and block new bookings on sailings for a boat while it is out, saved after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R17: Show overdue alerts for work orders past their due date and for boats still out of service, saved after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R18: Show finance revenue by route and by season with filters for date range. Not checked yet Its test passed. The judge hasn't looked yet.
• R19: Show fuel cost per crossing by boat and route from saved fuel entries. Not checked yet Its test passed. The judge hasn't looked yet.
• R20: Show refunds from cancelled and downtime affected bookings in finance, linked to the booking code and route. Not checked yet Its test passed. The judge hasn't looked yet.
• R21: Let finance export the filtered report as a CSV file. Not checked yet Its test passed. The judge hasn't looked yet.
• R22: Show finance charts for revenue by route, revenue by season, fuel per crossing and refunds. Not checked yet Its test passed. The judge hasn't looked yet.
• R23: Provide a chat helper on the public site that answers passenger questions from the saved timetable and notices and shows where the answer came from. Not checked yet Its test passed. The judge hasn't looked yet.
• R24: Let the chat helper hand off and hands off to a person by creating a staff ticket with the conversation, saved so staff can see and answer it after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R25: Provide real sign-in roles for dispatcher, crew, mechanic and finance that prove who a person is. Can't be done People cannot sign in to products yet, so real role accounts cannot be enforced.
• R26: Provide a browser role picker for dispatcher, crew, mechanic and finance that limits which screens and actions each role sees in this suite, kept in the browser as the closest available option and still there after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R27: Keep an audit log of every change, including role, action, item, old value, new value and time, still there after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R28: Provide seed data with at least 90 days of made-up history for sailings, bookings, crew, maintenance, fuel and refunds, still there after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R29: Use one shared saved database for all parts of this operations suite so a booking made on the public site shows on the dispatcher board, still there after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R30: When a boat is taken out for maintenance, block new bookings for its sailings and notify affected passengers by marking affected existing bookings in lookup and the assistant, saved after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R31: Automatically send external email or text messages to affected passengers to notify them when a boat is taken out. Can't be done The product cannot send email, SMS or WhatsApp, so external passenger messages cannot be sent automatically.
• R32: As the closest option to notify passengers, create a draft passenger notice for downtime and delays that staff can copy and send themselves, and show it in booking lookup and the assistant, saved after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
• R33: Make finance see refunds from cancellations and downtime without re-entering them. Not met "R33: finance sees downtime refunds without re-entering them" did not pass.
• R34: Write automated tests for every part and run them, including booking, dispatch, crew, maintenance, finance, assistant and admin, and show the test results in the build record. Not checked yet Its test passed. The judge hasn't looked yet.
• R35: Test all the cross-part flows in a browser, including booking to dispatch, maintenance blocking bookings and cancellation to finance refund, and fix what fails before finishing, including anything that fails on phones. Not checked yet Its test passed. The judge hasn't looked yet.
• R36: Make the look distinctive and calm, like a harbor at dawn, on phones and desktops across every screen. Not checked yet Its test passed. The judge hasn't looked yet.
• R37: Build Harborlight as a complete operations suite for the invented island ferry company Saltmere Ferry Cooperative, so the whole operations product covers booking, dispatch, crew, maintenance, finance, assistant and admin together. Not checked yet Its test passed. The judge hasn't looked yet.
• R38: Make clear that all people, boats, routes and numbers are made up for this island company, and label invented numbers as invented wherever sample fares, counts and history appear. Not checked yet Its test passed. The judge hasn't looked yet.
• R39: Deliver this as a big multi-part product with all seven parts working together, not as separate disconnected pages, so data flows across the multi-part operations suite end to end. Not checked yet Its test passed. The judge hasn't looked yet.
• R40: Build the work in separate part-sized workstreams that correspond to one per part: public booking, dispatcher console, crew app, maintenance tracker, finance reports, passenger assistant and admin, each completed and tested before the whole is joined. Not checked yet Its test passed. The judge hasn't looked yet.
• R41: Split the implementation work across subagents, one per part, in the build plan and milestones, with each part owning its screens, actions and tests and integrating through the one shared database. Not checked yet Its test passed. The judge hasn't looked yet.
• R42: Take as long as the quality needs by not cutting corners: every part is finished to a usable quality standard, tested, and checked in a browser before it is marked done. Not checked yet Its test passed. The judge hasn't looked yet.
• R43: Do the whole thing, not a sketch: deliver the whole product with real saved data, complete flows, empty and error states and cross-part behavior, not a sketch, mock or partial demo. Not met No test ran for it.
• R44: Provide clear navigation between public, dispatcher console, crew, maintenance, finance, assistant handoffs and admin, with the current part easy to return from. Not met No test ran for it.
• R45: Show helpful empty states before any booking, notice, swap, work order, handoff or audit filtered result exists, with the next action to take. Not met No test ran for it.
• R46: Show plain error states when a sailing is full, a boat is down, a checklist is incomplete, hours would be exceeded or a booking code is not found, and let the person try another choice when an action fails. Not met No test ran for it.
• R47: Let staff edit and delete or close notices, work orders, inventory entries and draft alerts they no longer need, with each change written to the audit log and saved after a reload. Not met No test ran for it.
• R48: Run a daily background check for overdue maintenance and save draft alerts for the owner to confirm, without sending anything externally. Not met No test ran for it.