v0.12.0

Full Changelog: v0.11.3...v0.12.0

Full Changelog: v0.11.3...v0.12.0

v0.11.3

Full Changelog: v0.11.2...v0.11.3

Full Changelog: v0.11.2...v0.11.3

FlightLens 0.11.2

FlightLens 0.11.2

Optional AI summaries are available for Inspector and two- or three-backup
Compare views. Settings support Gemini, OpenAI, OpenRouter and custom
OpenAI-compatible endpoints, including local models. The feature is off by
default. Every summary, regeneration and connection test requires an explicit
Send after reviewing the destination and exact payload. Only a bounded,
redacted structured digest is sent; raw CLI backup text is excluded.

Results are plain text with model attribution and a disclaimer. They can be
copied or saved as Markdown with backup hashes, selected profiles and comparison
baseline provenance. Keys use the OS credential store or explicitly selected
session-only storage. Summary caches exist only in memory.

Upgrade and compatibility

No breaking changes are known and no migration is required. Existing settings,
automatic restore and version-1 reference-only .flightlens sessions remain
compatible. AI settings live separately; keys and summaries are never saved in
sessions. Bundled firmware schemas and supported Betaflight boundaries are
unchanged. iNav and ArduPilot remain recognition-only. Existing configuration
exports are unchanged; Markdown AI summary export is a separate operation.
Inspection, comparison, audits and configuration exports remain offline, and
source backups remain read-only. Model output never changes analysis results.

This delivers configuration/comparison summaries ahead of the Phase 3 telemetry
pipeline; it does not complete Phase 3.

Known limitations

• Live cloud-provider and installed Ollama smoke checks remain pending. Provider
  wire-format tests do not establish account or model availability.
• Tagged Windows/macOS workflows build the installers with the locked dependencies.
  Packaged credential-store, save-dialog, clipboard and license/corresponding-source
  bundle smoke checks remain pending.
• Responses are non-streaming. Token/cost reporting, telemetry summaries,
  user-editable prompts and summary persistence in sessions are deferred.
• Unknown or non-comparable settings remain explicitly uncertain. A summary is
  model-generated commentary, not a flight-performance finding or tuning advice.
• Model overrides may reject the configured request parameters. Native credential
  services may be unavailable; session-only storage must be selected explicitly.
• Installers remain unsigned and macOS notarization is absent.

The milestone notes are published after both tagged installer workflows pass.

Local validation on 2026-09-17 passed ./test.sh (including 27 shell, 94
frontend and 37 browser tests and the real-backup corpus gate), all six
pnpm screenshots:check scenarios, the production build and formatting checks.

Version 0.11.1 fixes the case-insensitive module-resolution collision that
blocked 0.11.0 installer builds. The original tag is retained unchanged.

Version 0.11.2 also fixes the macOS synthetic HTTP test server socket mode;
all transport checks remain enabled. App transport behavior is unchanged.

v0.10.2

Full Changelog: v0.10.1...v0.10.2

Full Changelog: v0.10.1...v0.10.2

v0.10.1

Full Changelog: v0.10.0...v0.10.1

Full Changelog: v0.10.0...v0.10.1

v0.10.0

FlightLens 0.10.0

Throttle previews now support ProSpec backups on 4.5.3.KAACK_V19 and
ProSpec2 backups on 2025.12.3-alpha.KAACK_V19. The latter uses its own
hover-dependent calculation and shows the imported hover setting with source
navigation. Official Betaflight 4.3.2 throttle previews are also supported.
Calculations were checked against C from the exact public firmware revisions,
and both current ProSpec backups were verified locally without changing them.

Phase 2 is complete within the revised items 1–6 scope. Native file routing and
packaged platform smoke validation are deferred, not completed. The roadmap,
README and TODO now state that boundary consistently.

Upgrade and compatibility

No breaking changes are known and no migration is required. Existing settings,
automatic restore and version-1 reference-only .flightlens sessions remain
compatible. The session format, bundled firmware schemas and documented exports
are unchanged. Bundled schema lines remain Betaflight 4.2, 4.3, 4.4, 4.5 and
2025.12; throttle support expands only to the exact releases listed above.
Other vendor suffixes are not automatically certified. iNav and ArduPilot text
backups remain recognition-only. Inspection stays offline and backups read-only.

Known limitations

• Throttle previews require explicit valid settings in the selected rate profile.
  Older diff backups with omitted defaults can still have unavailable graphs.
• Official 2025.12 throttle previews remain unavailable pending separate release
  verification. Legacy MID=100 remains unavailable; the supported hover model
  follows its distinct firmware behavior at that midpoint.
• Charts represent configured throttle commands, excluding runtime mixer effects.
• Portable sessions exclude pasted inputs and Blackbox imports; relinking requires
  identical backup contents.
• Native file routing and packaged Windows/macOS smoke checks remain deferred.
  Installers are unsigned and macOS notarization is absent.

Validation includes compiled firmware C differential fixtures, the full local
./test.sh suite, and light/dark README screenshot checks. Tagged workflows build
and publish Windows and macOS installers.

v0.9.0

FlightLens 0.9.0

Compare two or three backups with shared angular-velocity and throttle graphs,
independent rate/PID profiles, and an explicit baseline for three-way parameter
and collection comparisons. Unknown values and compatibility limits remain visible.

Browse a selected backup folder recursively with searchable, paginated metadata
indexing, cancellation, and refresh after files move or drives reconnect.

Save and open reference-only .flightlens sessions with workspace locations,
active backup, tab/theme, profile selections, comparison order and baseline.
Retry and hash-checked relinking recover moved backups. Save As preserves
unavailable references and selections without overwriting backups or existing files.

Phase 2 items 4–6 are implemented. Native OS file routing (item 7) and packaged
platform validation (item 8) remain outstanding.

Upgrade and compatibility

No breaking changes are known. No migration is required. Automatic saved paths
and existing settings remain compatible. Portable sessions introduce a new
version-1 format; releases before 0.9.0 cannot open these manifests. Unsupported
manifest versions are rejected, and no backup contents are embedded.

Bundled schemas continue to cover Betaflight 4.2, 4.3, 4.4, 4.5 and 2025.12.
Certified mappings, throttle-model version restrictions, and validated exports
are unchanged. File-backed iNav/ArduPilot text backups remain recognition-only.
All inspection stays offline and source backups remain read-only.

Known limitations

• Portable sessions exclude pasted inputs and header-only Blackbox imports.
  Save pasted backups separately and reopen the files before including them.
• Relinking requires identical contents; inspect changed files separately.
  Save As creates a new manifest; open it to establish the new retry target.
• Comparison requires distinct supported configurations. Missing profiles and
  unavailable comparisons produce explicit messages.
• Indexing skips links and is bounded to 10,000 backups, 100,000 directory
  entries and 64 levels. Text reads are limited to 16 MiB; sessions to 32
  references and 256 KiB.
• Native Windows/macOS picking, recovery, disconnected-drive and other desktop
  smoke checks remain pending. Installer builds do not replace those checks.
• Installers remain unsigned and macOS notarization is absent. Relicensing and
  installer-signing tasks have been removed; GPL-3.0-or-later remains in effect.

Release checks include the full local suite, native session tests, and both
README screenshot themes. Tagged workflows build and publish Windows and macOS
installers.

v0.8.0

FlightLens 0.8.0

The Rates tab now includes a read-only Throttle Curve Preview alongside angular
velocity. It shows the selected profile's imported MID, EXPO and throttle limit
settings with source-line links, and plots normalized throttle input against
throttle command in percent.

The calculation follows verified legacy Betaflight integer lookup behavior and
applies the configured OFF, SCALE or CLIP limit afterward. Differential tests
compare 28,512 vectors against compiled, pinned upstream C code.

Phase 2.5 implementation is complete. The next roadmap unit is Phase 2 item 4:
three-backup comparison with an explicit baseline.

Upgrade and compatibility

No breaking changes are known. No migration or other user action is required.
Saved paths and settings retain their existing format; portable .flightlens
sessions are not yet supported. Source backups remain read-only, and inspection
and comparison remain offline. Existing exports and their validation are preserved.

Bundled schemas continue to cover Betaflight 4.2, 4.3, 4.4, 4.5 and 2025.12.
The new throttle preview requires exact official releases 4.2.0, 4.3.0, 4.4.0 or
4.5.0–4.5.5, a matching schema pack, and four explicit valid settings in the
selected rate profile. Missing values are not filled from defaults. Existing
angular-velocity default recovery is unchanged.

Known limitations

• Vendor builds, other releases and the separate 2025.12 hover-dependent model
  report the throttle preview as unavailable.
• MID=100 remains a valid CLI setting but is unavailable in the preview because
  the upstream extra lookup knot has a zero divisor.
• The chart represents the static configured curve and ordinary limit path,
  excluding smoothing, boost, RPM-limit bypass and other runtime effects. It
  does not predict motor output or thrust.
• Packaged Windows/macOS native integration and feedback hand-off still require
  manual validation. Installers remain unsigned; macOS notarization is absent.
• Three-backup comparison, workspace indexing, portable sessions and native file
  associations remain outstanding.

Release validation covers Rust and frontend tests, parser-to-renderer browser
behavior, the local backup corpus and README screenshots. GitHub workflows build
and publish Windows and macOS installers.

v0.7.0

FlightLens 0.7.0

FlightLens adds comparison of VTX activation slots on matching official Betaflight
4.5.0–4.5.5 versions, and adjustment-range declarations on matching official
4.5.0–4.5.5 and 2025.12.1–2025.12.5 versions. These comparisons account for command
ordering, normalized ranges, invalidated declarations, and source lines.

Seven additional global parameter mappings bring certified cross-version coverage
to eleven settings across those releases: battery capacity, forced cell count,
voltage divider and multiplier, ADC current offset, and virtual-current scale and
offset join motor poles and the three battery cell-voltage thresholds. Bounds and
exact firmware identities gate comparisons; missing values remain unknown.
Bundled evidence and developer verification scripts document the supported scope.

The feedback form now states that submitting an issue requires a GitHub account
and labels its browser hand-off “Continue to GitHub”.

Phase 2 item 3 is complete within its documented comparison coverage boundary.
Broader equivalence research is deferred; three-backup comparison is next.
Phase 2 as a whole remains in progress.

Upgrade and compatibility

No breaking changes are known. No migration or other user action is required.
Saved paths and settings retain their existing format. Portable .flightlens
sessions are not yet supported. Source backups remain read-only, and inspection
and comparison remain offline.

Bundled schemas continue to cover Betaflight 4.2, 4.3, 4.4, 4.5 and 2025.12.
New equivalence mappings require exact verified official releases and compatible
packs; vendor builds and other versions do not inherit certification. Existing
export formats and validation requirements are preserved. Collection comparison
does not add collection export.

Known limitations

• Equal declarations do not certify equal flight behavior, measured current,
  consumption estimates, RF output, or build/runtime activation.
• VTX activation comparison for 2025.12 requires additional build evidence.
  Cross-version collection equivalence and broader parameter mappings are deferred.
• Three-backup comparison, workspace indexing, portable sessions and native file
  associations remain outstanding.
• Twelve 2025.12 settings have unresolved bounds; hardware-specific schemas,
  arrays and full unsigned 32-bit values still need additional coverage.
• Packaged Windows/macOS native integration and feedback hand-off require manual
  verification. Installers remain unsigned and macOS notarization is absent.

Release checks cover Rust and frontend tests, parser-to-renderer behavior, the
local backup corpus, and README screenshots. GitHub workflows build and publish
Windows and macOS installers.

v0.6.0

FlightLens 0.6.0

FlightLens expands backup comparison with explicit feature, serial-port and mode
assignments, receiver ranges and failsafes, and VTX tables. Filters and source
lines make differences traceable; missing or invalidated declarations remain
unknown. Preserved CLI collection text is also available for comparison.

Four parameter mappings—motor poles and three battery cell-voltage thresholds—
now support certified cross-version comparison between official Betaflight
4.5.0–4.5.5 and 2025.12.1–2025.12.5. The firmware-family gate now works with actual
parser output. Other cross-version settings remain uncertified.

The new feedback button prepares a report for review, opens a prefilled GitHub
issue in the browser, and optionally copies a redacted configuration for the user
to submit. FlightLens does not send it itself. Preview consent and attachment-size
checks protect against submitting stale previews or oversized issue text.

GPS rescue bounds for Betaflight 4.4 and LED STATUS lookup handling are corrected.

Upgrade and compatibility

No breaking changes are known. No migration or other user action is required.
Saved workspace paths and settings retain their existing format; portable
.flightlens sessions are not yet supported. Source backups remain read-only,
and inspection and comparison remain offline. Submitting feedback uses the
user's browser and GitHub account.

Bundled schemas continue to cover Betaflight 4.2, 4.3, 4.4, 4.5 and 2025.12.
Receiver-range, receiver-failsafe and VTX-table semantic comparisons require
matching verified official versions in 4.5.0–4.5.5 or 2025.12.1–2025.12.5.
Vendor and cross-version collection comparisons remain uncertified. Existing
export formats and explicit-input validation requirements are preserved; these
new semantic collection comparisons do not add collection export.

Known limitations

• VTX activation and adjustment-range semantic comparison remain outstanding.
  The initial official 4.5 activation scope is documented; 2025.12 needs verified
  build-capacity evidence. Equal VTX declarations do not establish equal RF output.
• Three-backup comparison, saved comparison selections and broader cross-version
  equivalence remain outstanding.
• Twelve 2025.12 settings still have unresolved bounds. Hardware-specific schema
  entries, arrays and full unsigned 32-bit values need additional coverage.
• Packaged Windows/macOS native integration and feedback hand-off still need
  manual verification. Installers remain unsigned; macOS notarization is absent.

Release validation includes the full local test suite, parser corpus checks and
README screenshot checks. GitHub workflows build and publish both desktop installers.