Tracker Version History

* Show only actual aircraft edits when reviewing uploads from current apps against older published configurations; empty new fields no longer mark every drone changed. * Keep reported RPIC callsigns visible and match member identity separately from qualification verification; show flight readiness times in local flight time with a timezone. * Include pilot-profile edits, operating-profile revisions, aircraft service reports, and flight readiness corrections in the organization audit trail, with repeatable backfill of retained history. * Recognize the BVLOS authority-details-pending flight selection without treating it as a configured waiver.

* Add organization-managed operating profiles with versioned authority documents, applicability, briefing conditions, and an explicit organization default; distribute them to compatible Android and Apple apps for offline use without changing older-device configuration compatibility. * Preserve each flight's reported operating authority and time-stamped changes, with advisory review flags and attributed records-administrator corrections using exact historical profile versions. * Add aircraft readiness, accessory and payload weights, member pilot qualifications, and service-status reporting with equipment-manager notifications and retryable offline drafts. * Let administrators review aircraft readiness fields in organization configuration changes, preserve fields older apps cannot represent, and export original flight readiness and correction history. * Retain short flights and stationary hovers, including missions with unresolved pilot details, so incomplete information does not prevent recording.

* Keep tablet coordination responsive while flight uploads wait on weather, process tracks, or write archives, using bounded workers that remain bounded when requests are cancelled. * Prevent slow tablet or browser connections from delaying healthy peers; serialize socket output, bound queued messages, and disconnect stalled clients so they can reconnect. * Keep upload serialization separate for each organization and release unused locks, so matching drone identities in different organizations do not unnecessarily block one another. * Move expired coordination-state cleanup off the sighting path into indexed, bounded scheduled batches, and recover stale pooled database connections without logging routine SQL parameters. * Add fresh-PostgreSQL automated system checks for two simulated organizations, authenticated HTTP and WebSocket interactions, isolated archives, stalled weather, retention, and database reconnection; run them in CI alongside expanded runtime regression tests. * Preserve an already-authorized tablet's organization access when RID2Caltopo 2.2.7 imports enrollment again, using its active prior device credential and matching installation identity to avoid redundant sign-in. * Continue requiring sign-in for new installations and credentials that are expired, revoked, or explicitly awaiting reauthentication.

* Support Android's on-device same-tablet confirmation after re-authentication: offer only older authorizations for the same organization member and exact device model, preserve the established tablet name, supersede the replaced authorization, transfer its stream and recording ownership, and audit the decision. * Let a re-enrolled tablet safely re-advertise an expired recording from the same organization so recordings in the selected archive folder return to the tablet Streams page without weakening live-stream ownership checks. * Use the original concise recording name for browser downloads instead of exposing tablet-private catalog identifiers or temporary-file suffixes. * Keep a visible Streams page refreshing when its browser window loses focus, so ended sessions and newly recovered recordings do not remain stale while the operator works in another window.

* Let organization administrators distinguish replacement tablet authorizations with an organization-scoped device-identity fingerprint, a live Currently connected marker, and an audited Retire authorization action that leaves the replacement usable. * Replace relay-price language on organization and tablet Streams pages with month-to-date or year-to-date viewer-hours and estimated remaining subscription capacity when an allowance is configured. * Release failed or ended browser video sessions without waiting on terminal telemetry, preventing recordings from remaining marked Video in use after playback stops or fails. * Replace passive browser stream WebSockets with bounded, focus-aware status checks, retain tablet silence retirement, and explicitly configure Cloud Run to scale to zero with CPU throttling after activity becomes idle.

* Add a dormant provider-neutral subscription catalog with a 45-day trial, $25, $50, and $100 monthly planning tiers, a 10% annual-payment discount, and a custom regional or enterprise tier; payments and paid-tier enforcement remain disabled. * Replace infrastructure-cost detail in organization management with monthly or annual viewer-hour utilization and an estimated remaining allowance when an absolute allowance has been assigned. * Keep cloud-cost allocation visible only to platform administrators for internal reconciliation and margin planning. * Release failed remote-video startup requests immediately so recordings no longer remain marked Video in use after the browser times out, and refresh the page after the failed controller becomes terminal. * Use the UAS4SAR administrator identity in current deployment guidance and local pilot setup defaults. * The guarded zero-traffic staging deployment rejected the release because the new subscription catalog module was absent from the container file list; production remained on v1.4.83.

Prepare subscription model and release video fixes

* Assign each compatible authenticated organization tablet a guaranteed-unique member-and-device-model name and return it to RID2Caltopo for consistent app, CalTopo marker, and Tracker identity. * Preserve the existing name for older organization app versions that do not report a hardware model and direct operators to upgrade instead of guessing; leave standalone device naming unchanged. * Resolve CalTopo tablet and recording links from persistent metadata, require organization video access before revealing details, and show which pilot or VO tablet holds unavailable local video.

* Retry a remote Live Feed connection once when it establishes without delivering video, preserving the approved viewing request during recovery and returning to normal failure handling if the retry also fails. * Retire an R2C tablet connection into Tracker standby after 60 seconds without any tablet message, clearing stale incident-map presence when field connectivity disappears without a clean disconnect. * Keep a completed recording's exact Streams page stable instead of repeatedly reloading it when the connected tablet advertises other recordings. * Restore the Tracker Version link on organization pages so operators can open the deployed change history without using Git. * Identify UAS4SAR LLC as the RID2Caltopo and r2c-tracker publisher and operator in managed-access terms, and use the UAS4SAR mailbox for platform, TestFlight-feedback, and security notices.

* Accept and retain the current managed-pilot acknowledgment so valid RID2Caltopo website requests no longer end on the request error page. * Email the platform contact and copy the requester with the same request details and exact accepted acknowledgment, including assumption of responsibility, developer hold-harmless terms, and the California Civil Code section 1542 waiver for counsel review.