Add Libre 3/3+

[trioneer-dev]

Summary

• Integrates the LibreLoop CGM plugin (with adaptations to work with pre next-dev LoopKit) so Trio can pair FreeStyle Libre 3 / 3+ sensors directly (no internet reliance, no external app).
• Ships as three new submodules (LibreLoop, LibreCRKit, LoopAlgorithm) wired through Trio's existing PluginManager / PluginSource path.
• Adds Libre 3 / 3+ to the CGM picker and surfaces sensor lifecycle + status highlight on the home glucose view via the shared CGM highlight pipeline.

Important

1-min readings are currently not supported
This is still experimental

Test plan

• Fresh install → CGM settings → Libre 3 / 3+ visible in picker
• Pair a new Libre 3 / 3+ sensor and complete warmup
• Glucose values arrive on a normal 5-min cadence; no gaps > 6 min under steady conditions
• Backfill on cold-start / relaunch fills the last 24 h of history
• Sensor progress bobble on home view matches remaining lifetime; flips to grace period near expiry
• Alerts from LibreLoop (sensor issue, expiring, expired) show up
• Swap between Libre 3 / 3+ and another CGM (e.g. G7) and back — no stuck state (watch out, not down Receiver ID before removing Libre)
• Loop enacts against Libre readings; no regressions vs. current Trio behaviour
• Simulator scenarios still work

[MikePlante1]

@kingst @MikePlante1 @marv-out how do we feel about adding this to Trio dev?

I’d definitely be fine with adding it as a feature branch, but I think it probably needs a little more testing before getting added to dev.

[dnzxy]

Thanks!

It‘s part of Loop next-dev and we haven’t had any reports of issues. I‘d like to keep # of feature branches to an absolute minimum, because we are actively blocking people from using it by splitting all these device drivers up into different feature branches :-/

[marv-out]

I'm okay with adding it to dev to get more testers

[MikePlante1]

Maybe at least a "(beta)" label or something if adding it straight to dev?

[dnzxy]

I suggest we just follow Loop here for once, and move it to dev. It‘s dev for a reason. Merging is only blocked by CI, need to check that.

[kingst]

I didn't test it, but LGTM based on code review. I'm fine merging this to dev

[MikePlante1]

I suggest we just follow Loop here for once, and move it to dev. It‘s dev for a reason. Merging is only blocked by CI, need to check that.

next-dev != dev, but okay

[marv-out]

Merging is only blocked by CI, need to check that.

Seems to be a type check error in Sources/LibreCRKit/Crypto/FirstPairSourceSlice.swift, especially

let cf0Source = [UInt8](repeating: 0, count: 3)
    + [0x05]
    + Array(cf0State[0..<8])
    + Array(cf0State[8..<12])
    + Array(cf0State[12..<14])
let bd0Source = [UInt8](repeating: 0, count: 3)
    + [0x03]
    + Array(bd0State[0..<8])
    + Array(bd0State[8..<12])
    + Array(bd0State[12..<14])

explicitly telling the compiler which types there are seems to fix it, but it probably needs to be PRed against loopandlearn/LibreCRKit

[dnzxy]

Moving this to draft until the 1-min handling is addressed.