Repository navigation
docs: supported-sensor matrix and corrected cgm_cbio status for 0.4.0 - #218
Open
shroominic wants to merge 1 commit into
Open
shroominic wants to merge 1 commit into
shroominic wants to merge 1 commit into
Conversation
This was referenced Sep 18, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Docs only. Two files, no code path touched.
docs/supported-sensors.md(92 lines): what each family can do in a 0.4.0 build, and what is explicitly provisional or unsupported.cbio): discovery, authenticated session, live values, stored history; candidate-only model identification (GS1 and GS3 shareFF30); bounded writes (device info,19 01, one clock set,06 0A,06 08); declined scans reported as unavailable, never as an absent sensor.docs/compatibility.md: thecgm_cbioparagraph said "0.0.1 ... scaffold ... It is not registered in any app build". The package is0.1.0and the driver is registered ascbionext toaidexinopenhealth/lib/src/driver_factory_io.dartfor any build that injects vendor link material. The paragraph and the public-API bullet now say that.Why it matters for the release
.github/workflows/release-android.ymlbuilds withflutter build apk --release --no-puband no credential defines, so the registry leavescbioout of the shipped APK. That is deliberate fail-closed behavior, and until now nothing user-facing said so.Safety posture
raw / 10provisional marker, statesisUnitVerifiedis always false, and says no GS1 surface publishes mg/dL or mmol/L.docs/product-safety.md, unchanged and not weakened.Refs #216. Verified:
make format-check(0 changed),make lint,make tooling-check,make vendor-material-guardon this head; CI runs on the pushed head SHA.