Repository navigation
Conversation
This was referenced Oct 21, 2026
Draft
This was referenced Oct 21, 2026
Add optional attributed repeater telemetry and availability filtering
MeshCore-Beacon/beacon-web#184
Draft
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.
This is the optional companion-telemetry layer above the consolidated core in #266/#267. It integrates #263 without replacing the current config/read-model, scope-catalogue, build-identity or retry behavior. Basic Atlas and Topology remain in the core candidate and require no intake service.
An explicitly configured gateway enables automatic signed companion/client enrollment, report submission, retained history and availability through bounded, whitelisted API routes. The core does not acquire collector tables or radio polling code. It strips caller credentials/forwarding headers, limits request/response sizes and deadlines, disables redirects, and advertises the capability separately from service health.
Focused config/router/handler/startup checks passed. Full native CI and combined Canadaverse preview qualification passed. The matching web draft preserves attribution, sensor channels, gaps and history caps. Flutter #11 is the opt-in BLE/Wi-Fi client; the separately packaged intake and optional headless client retain their own lifecycle and database.
This dependent branch includes core ancestry until core is accepted; review the telemetry-only delta against
codex/release-core-20261021. No main merge, production deployment or reviewer request is made by this draft.Current qualification and promotion gates - 23 October
The full project roadmap, issue/PR disposition and staged promotion plan are in docs #43, tracked by docs #45. Core server #266/#267 and web #182/#183 are one paired candidate; optional server #268/#269, web #184/#185, docs #44 and Flutter #11 remain a separate rollout.
Current application heads pass native CI. Canadaverse now runs server
054e08de7d7fd581e55544e0326ca92596b9a990and web8dcb7f2f233c8ac4086c1ebe02f81d348630321b(2.5.1-n30nex.1), including preview extras. Its complete native frontend suite passed 1,560 tests in 172 files. Public verification matched all 34 assets and both source archives, with both MQTT brokers connected, six retained telemetry histories, and invalid-signature/unenrolled submission rejection. Preview artifacts are local builds of exact clean native-CI-qualified source; this is not a stable release.On a restored snapshot, the committed global Topology query median improved from 1.3691 s to 0.9836 s (28.2%), with the same 9,975 edges. All six unique-traffic raster cases retained identical pixels. These are query/CPU-raster checks, not browser/GPU FPS or production throughput measurements. The later public 24h sample returned the same 9,346 links in 5.619 s cold and 0.191 s warm; earlier severe shared-host I/O pressure caused timeouts. Cold-load capacity, target-browser/device checks and production-shaped migration/recovery soak remain acceptance gates.
Production/dev/dev1 were inspected read-only. Dev1 services are stopped. This preview update changed no schema, retention, intake/worker, credentials or radio ownership. Prior restored-database qualification is recorded separately; no fresh browser or physical mobile/background qualification is claimed here. Dependency advisories and the separate Vite #186 candidate still need their own resolution and qualification. No org merge or release approval is implied.
Review the optional-only delta: codex/release-core-20261021...codex/release-telemetry-20261021 . This PR retains its requested
devtarget.