- User guide: the connection status (red top bar, the ring), a weak
signal counting as none for flights and squawks, the offline page for
any other page, PDFs on phones, the activity log loading as you scroll,
What's new on About, Aircraft access on Admin → Users, and grounding
squawks notifying everyone on the aircraft.
- README: the configurable roles table, feature rows for phones and
offline and the REST API, and rows that said "Owners can…".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What people can do on an aircraft now comes from their role there, and
administrators set what each role allows (Admin → Roles).
- Roles are installation-wide sets of permissions (31, grouped as flying,
squawks and notes, maintenance records, imports and exports, the
aircraft, notifications). Seeing an aircraft's records needs none.
- Built in: Owner (always every permission, so an aircraft can always be
managed), Mechanic (shop maintenance: logbook, signing, components,
inspections, ADs, squawks, reminders), Pilot (what pilots could do
before) and Viewer (view only). Administrators can change all but
Owner's, and add their own; a role can be deleted once nobody has it.
- Existing owners and pilots keep exactly what they could do.
- Admin → Users → a user lists their role on every aircraft, to change,
remove or add. On the aircraft's Access page, anyone who manages people
hands out roles, but only an Owner can give or take away Owner, nobody
changes their own (except administrators), and an aircraft always
keeps an Owner (AircraftAccess).
- Controllers declare the permission each action needs; a request that
changes something with none declared is refused (and raises in
development and tests), and a test walks every route to check.
- Weekly reminders and overdue alerts go to roles that get reminders;
the DRS reminder also needs Manage ADs. The API follows the person's
role; its owners_only error is now not_permitted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Edit on a flight: owners can correct any flight; a pilot, the flights
they logged (the same rule as its engine data).
- Date, airports, route, notes, oil and fuel (its oil and fuel records
follow) and the attached files can always be changed.
- The meter readings only on the latest flight, while its tach in is
still the aircraft's tach: the aircraft and installed components move
by the difference, and with both readings the duration is worked out
from them. On earlier flights they're locked (later flights started
from them), pointing to Update Hours; the server ignores them too.
- Each correction is in the activity log with what changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Offline
- Flights and squawks saved offline are tagged with their user and only sent
while that user is signed in; storage is made persistent; Background Sync
sends them with the app closed (Chromium); unsent count on the app badge
- Report Squawk works offline (photos included, one-time key like flights)
- The Fleet page and, for each of your aircraft, the Overview, W&B, Log
Flight and Report Squawk pages and photo are saved ahead of time, so the
app opens and works without signal; copies say when they were saved
- Sign-out clears saved forms, pages and photos (asks first if items wait)
- Offline page rendered by Rails (localized, follows the theme, no inline
script); service worker version follows the build
Install and notify
- Web Push (web-push gem, VAPID keys from env or storage/vapid_keys.json):
grounding squawks, newly overdue items (daily, once each), signing
requests; per-device on/off and test in Profile -> This device; only
browser push service endpoints accepted
- Manifest shortcuts (Log Flight, Report Squawk via /go/...), lang and
localized description; install help on Profile; reload notice after a
release
Also
- Dockerfile: libssl-dev in the build stage (openssl gem); lockfile checksums
- Leftover English and %{_} interpolation names from the localization pass
- Guide and README updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- more_menu helper (menu / menu-item styles): each section keeps its main
action as a button; imports, exports, printing and tools move under More
(flights, logbook, logbook entry, documents, inspections, fleet)
- Aircraft header: More with status report and, for owners, access &
sharing, edit, .sam.zip and records package; Access & Sharing and Oil
Analysis tabs removed (oil analysis is under Oil & Fuel with a switch)
- Logbook: Print selected appears once an entry is ticked; filters apply on
change; dates use fmt_date (also AirTrail, notes, audits, About)
- Header shows the role on the aircraft and hides the usual Available badge;
no second Grounded badge on the Overview; AD DRS import listed once
- Flights: stat cards 2x2 on phones; By year opens visibly, only with more
than one year; duplicate + Log Flight removed
- Remove unused hello_controller.js; guide and README updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 16 Markdown pages covering every area for pilots, owners, mechanics
and admins, readable on GitHub
- /help renders them with a page list; links between pages work in both
places; only listed pages can be opened
- The electronic records instructions (AC 120-78B user instructions) are
now the guide's records page, also used as the procedures appendix
- Help link in the main menu
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>