docs: MeshCore bearer shipped — refresh connect guide, status, glossary - #170
Merged
Conversation
The user-facing docs still described MeshCore as "planned, not yet implemented" with placeholder config (DAPPS_MESHCORE_COMPANION_*), long after the Companion bearer shipped across eight PRs. Bring the docs to match reality: - Rewrite docs/connect/meshcore.md: status shipped (Companion-over-USB, off by default); the real feature set (binary transport + versioned-dictionary compression, airtime governor + adaptive controls, datagram reliability, passive discovery, watchdog, device control); real DAPPS_MESH_CORE_* config + the /MeshCore status/reset endpoints; the A/B/C deployment models (privacy vs containment); how it's been validated (on-air 2-radio + multi-hop sim) and what isn't (repeater flood-drop needs hardware); KISS + firmware-flash as future. - Flip status signals in docs/connect/index.md, docs/index.md, docs/glossary.md from "planned" to "shipped (Companion; KISS planned)". - Add discovery + deployment-models bullets and a sim pointer to the library README's feature list; note dictionary versioning in configure.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KLbwvhE2cKCe8WPZNg8k17
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
1 participant
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.
The user-facing docs still described MeshCore as planned, not yet implemented (with placeholder
DAPPS_MESHCORE_COMPANION_*config), long after the Companion bearer shipped across eight PRs. This brings the docs to match reality.docs/connect/meshcore.md— rewritten: status shipped (Companion-over-USB, off by default); the real feature set (binary transport + versioned-dictionary compression, airtime governor + adaptive controls, datagram reliability, passive discovery, watchdog, device control); realDAPPS_MESH_CORE_*config + the/MeshCorestatus/reset endpoints; the A/B/C deployment models (privacy vs containment); how it's been validated (on-air 2-radio + multi-hop sim) and what isn't (repeater flood-drop needs hardware); KISS + firmware-flash as future.docs/connect/index.md,docs/index.md,docs/glossary.mdfrom "planned" to "shipped (Companion; KISS planned)".configure.md.Docs-only; no code changed.
🤖 Generated with Claude Code