medre 0.1.0__tar.gz

medre-0.1.0/.github/adapter-compatibility.json

@@ -0,0 +1,59 @@
+[
+  {
+    "transport": "matrix",
+    "repository": "jeremiah-k/medre-adapter-matrix",
+    "ref": "d39212bc0c3c2e021c9427bc0e958870baaa1afa",
+    "extras": "e2e",
+    "local_integration": false,
+    "distribution": "medre-adapter-matrix",
+    "python_requires": ">=3.12"
+  },
+  {
+    "transport": "meshtastic",
+    "repository": "jeremiah-k/medre-adapter-meshtastic",
+    "ref": "8e59552cd32bc43147d873c991ded7c5f082756f",
+    "extras": "",
+    "local_integration": false,
+    "distribution": "medre-adapter-meshtastic"
+  },
+  {
+    "transport": "meshcore",
+    "repository": "jeremiah-k/medre-adapter-meshcore",
+    "ref": "7e5d5dc2eb025072de2e5ba0c48c90d3fc773d65",
+    "extras": "",
+    "local_integration": true,
+    "distribution": "medre-adapter-meshcore"
+  },
+  {
+    "transport": "lxmf",
+    "repository": "jeremiah-k/medre-adapter-lxmf",
+    "ref": "935faefd3d67be13a6fab445846338c8fc2f150d",
+    "extras": "",
+    "local_integration": true,
+    "distribution": "medre-adapter-lxmf"
+  },
+  {
+    "transport": "xmpp",
+    "repository": "jeremiah-k/medre-adapter-xmpp",
+    "ref": "9dcd854c90a453d488d7cef28e11d4e1cd80a76a",
+    "extras": "",
+    "local_integration": false,
+    "distribution": "medre-adapter-xmpp"
+  },
+  {
+    "transport": "chatmail",
+    "repository": "jeremiah-k/medre-adapter-chatmail",
+    "ref": "93d785020626751c2eb5f090751b788b15f8a409",
+    "extras": "",
+    "local_integration": false,
+    "distribution": "medre-adapter-chatmail"
+  },
+  {
+    "transport": "simplexchat",
+    "repository": "jeremiah-k/medre-adapter-simplexchat",
+    "ref": "83ab7436a669841bff5ed199302cc259ebe1ab34",
+    "extras": "",
+    "local_integration": false,
+    "distribution": "medre-adapter-simplexchat"
+  }
+]

medre-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jeremiah K.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

medre-0.1.0/MANIFEST.in

@@ -0,0 +1,2 @@
+include .github/adapter-compatibility.json
+recursive-include docs/schemas *

medre-0.1.0/PKG-INFO

@@ -0,0 +1,136 @@
+Metadata-Version: 2.4
+Name: medre
+Version: 0.1.0
+Summary: Modular event communications runtime
+License-Expression: MIT
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Communications
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: msgspec==0.22.0
+Requires-Dist: pyyaml==6.0.3
+Requires-Dist: termaid==0.12.0
+Provides-Extra: dev
+Requires-Dist: pytest==9.2.0; extra == "dev"
+Requires-Dist: pytest-asyncio==1.5.0; extra == "dev"
+Requires-Dist: pytest-timeout==2.4.0; extra == "dev"
+Requires-Dist: pytest-cov==7.1.0; extra == "dev"
+Requires-Dist: coverage==7.17.3; extra == "dev"
+Requires-Dist: build==1.6.1; extra == "dev"
+Requires-Dist: setuptools==84.2.1; extra == "dev"
+Requires-Dist: jsonschema==4.26.0; extra == "dev"
+Requires-Dist: packaging==26.3; extra == "dev"
+Requires-Dist: mypy==2.4.1; extra == "dev"
+Requires-Dist: types-PyYAML==6.0.12.20261113; extra == "dev"
+Dynamic: license-file
+
+# MEDRE
+
+**Modular Event-driven Routing Engine** — bridge conversations across Matrix,
+Meshtastic, MeshCore, LXMF, XMPP, Chatmail, and SimpleX Chat. MEDRE owns routing,
+persistence, and delivery evidence; each transport is an independently installed
+Python adapter. MEDRE began with mesh and LoRa bridges and supports messaging
+services through the same adapter, routing, and evidence contracts.
+
+> **Working pre-release — testers welcome; not production-ready.** Configuration,
+> event, and database schemas are not frozen. Expect breaking changes, test with
+> disposable state, and back up persistent state before updates. Do not delete
+> an active database to work around a schema mismatch: it may contain pending
+> messages and evidence.
+
+## Install MEDRE
+
+Install [uv](https://docs.astral.sh/uv/getting-started/installation/) and Git.
+
+**1. Install the CLI and example providers.**
+
+```bash
+uv tool install 'git+https://github.com/jeremiah-k/medre.git@main'
+medre adapters install matrix meshtastic
+medre adapters
+```
+
+On Windows, follow the printed uv command after MEDRE exits: the running
+executable cannot safely replace itself. For a reproducible, long-running
+bridge use a [locked deployment project](docs/ops/install.md#locked-deployment)
+instead of floating Git branches.
+
+**2. Verify the pipeline before connecting anything.**
+
+```bash
+medre config sample > sample.yaml
+medre config check --config sample.yaml
+medre smoke --config sample.yaml --storage-path smoke.sqlite3 --json
+```
+
+A fake `sent` receipt proves local routing and persistence, **not** remote
+delivery, RF reception, or native inbound codec decoding. The generated sample
+uses a one-way diagnostic route; build your two-way route in the next step.
+The same installation runs live bridges.
+
+**3. Create your first route.**
+
+```bash
+medre config bridge --output bridge.yaml
+```
+
+Select two adapter instances, map their conversation addresses, and inspect
+the generated route plan before saving. The builder never connects to a device
+or starts a service. See **[Getting Started](docs/ops/getting-started.md)** for
+the complete walkthrough and live setup.
+
+## Adapters
+
+All seven adapters participate in configuration, routing, persistence, diagnostics,
+and SDK-free smoke testing. Native features and delivery confirmation vary by
+transport; each [transport profile](docs/spec/transport-profiles/README.md)
+describes those boundaries.
+
+| Adapter                                                                 | Transport                                              | Setup                                            |
+| ----------------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------ |
+| [Matrix](https://github.com/jeremiah-k/medre-adapter-matrix)            | Accounts, rooms, optional E2EE                         | [Guide](docs/ops/transport-setup/matrix.md)      |
+| [Meshtastic](https://github.com/jeremiah-k/medre-adapter-meshtastic)    | Radio nodes and channels                               | [Guide](docs/ops/transport-setup/meshtastic.md)  |
+| [MeshCore](https://github.com/jeremiah-k/medre-adapter-meshcore)        | Companion nodes, contacts and channels                 | [Guide](docs/ops/transport-setup/meshcore.md)    |
+| [LXMF](https://github.com/jeremiah-k/medre-adapter-lxmf)                | Reticulum identities and destinations                  | [Guide](docs/ops/transport-setup/lxmf.md)        |
+| [XMPP](https://github.com/jeremiah-k/medre-adapter-xmpp)                | Multi-user rooms and direct conversations              | [Guide](docs/ops/transport-setup/xmpp.md)        |
+| [Chatmail](https://github.com/jeremiah-k/medre-adapter-chatmail)        | Accepted groups and direct chats through Chatmail core | [Guide](docs/ops/transport-setup/chatmail.md)    |
+| [SimpleX Chat](https://github.com/jeremiah-k/medre-adapter-simplexchat) | Allowlisted groups and direct conversations            | [Guide](docs/ops/transport-setup/simplexchat.md) |
+
+Install only the adapters you need, for example:
+
+```bash
+medre adapters install xmpp chatmail simplexchat
+```
+
+Community adapters can implement the same entry-point contracts; runtime startup
+never installs Python packages. Native libraries and account/profile preparation
+follow each provider's setup guide. See
+[package management](docs/ops/package-management.md) for persistent CLI tools
+and [adapter sources](docs/ops/adapter-installation.md) for pinned projects.
+
+## Documentation
+
+| Start here                                     | For                                                              |
+| ---------------------------------------------- | ---------------------------------------------------------------- |
+| [Getting Started](docs/ops/getting-started.md) | Install, smoke, guided bridge, native connections                |
+| [Operator guides](docs/ops/README.md)          | Package management, running, evidence, recovery, troubleshooting |
+| [Developer guides](docs/dev/README.md)         | Contributing, testing, authoring adapters                        |
+| [Technical specification](docs/spec/README.md) | Normative contracts and supported guarantees                     |
+
+New operators can optionally use [AI-assisted setup](docs/ops/ai-assisted-setup.md).
+Real-world testing and reproducible, sanitized bug reports are welcome—never
+share credentials, radio keys, identity files, or unredacted databases.
+
+## License
+
+MEDRE-owned core source is [MIT-licensed](LICENSE). Adapter source and its SDKs
+retain their respective terms, which may include GPL and the Reticulum License.
+See [dependency licensing](docs/dev/licensing.md) before redistribution.

medre-0.1.0/README.md

@@ -0,0 +1,102 @@
+# MEDRE
+
+**Modular Event-driven Routing Engine** — bridge conversations across Matrix,
+Meshtastic, MeshCore, LXMF, XMPP, Chatmail, and SimpleX Chat. MEDRE owns routing,
+persistence, and delivery evidence; each transport is an independently installed
+Python adapter. MEDRE began with mesh and LoRa bridges and supports messaging
+services through the same adapter, routing, and evidence contracts.
+
+> **Working pre-release — testers welcome; not production-ready.** Configuration,
+> event, and database schemas are not frozen. Expect breaking changes, test with
+> disposable state, and back up persistent state before updates. Do not delete
+> an active database to work around a schema mismatch: it may contain pending
+> messages and evidence.
+
+## Install MEDRE
+
+Install [uv](https://docs.astral.sh/uv/getting-started/installation/) and Git.
+
+**1. Install the CLI and example providers.**
+
+```bash
+uv tool install 'git+https://github.com/jeremiah-k/medre.git@main'
+medre adapters install matrix meshtastic
+medre adapters
+```
+
+On Windows, follow the printed uv command after MEDRE exits: the running
+executable cannot safely replace itself. For a reproducible, long-running
+bridge use a [locked deployment project](docs/ops/install.md#locked-deployment)
+instead of floating Git branches.
+
+**2. Verify the pipeline before connecting anything.**
+
+```bash
+medre config sample > sample.yaml
+medre config check --config sample.yaml
+medre smoke --config sample.yaml --storage-path smoke.sqlite3 --json
+```
+
+A fake `sent` receipt proves local routing and persistence, **not** remote
+delivery, RF reception, or native inbound codec decoding. The generated sample
+uses a one-way diagnostic route; build your two-way route in the next step.
+The same installation runs live bridges.
+
+**3. Create your first route.**
+
+```bash
+medre config bridge --output bridge.yaml
+```
+
+Select two adapter instances, map their conversation addresses, and inspect
+the generated route plan before saving. The builder never connects to a device
+or starts a service. See **[Getting Started](docs/ops/getting-started.md)** for
+the complete walkthrough and live setup.
+
+## Adapters
+
+All seven adapters participate in configuration, routing, persistence, diagnostics,
+and SDK-free smoke testing. Native features and delivery confirmation vary by
+transport; each [transport profile](docs/spec/transport-profiles/README.md)
+describes those boundaries.
+
+| Adapter                                                                 | Transport                                              | Setup                                            |
+| ----------------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------ |
+| [Matrix](https://github.com/jeremiah-k/medre-adapter-matrix)            | Accounts, rooms, optional E2EE                         | [Guide](docs/ops/transport-setup/matrix.md)      |
+| [Meshtastic](https://github.com/jeremiah-k/medre-adapter-meshtastic)    | Radio nodes and channels                               | [Guide](docs/ops/transport-setup/meshtastic.md)  |
+| [MeshCore](https://github.com/jeremiah-k/medre-adapter-meshcore)        | Companion nodes, contacts and channels                 | [Guide](docs/ops/transport-setup/meshcore.md)    |
+| [LXMF](https://github.com/jeremiah-k/medre-adapter-lxmf)                | Reticulum identities and destinations                  | [Guide](docs/ops/transport-setup/lxmf.md)        |
+| [XMPP](https://github.com/jeremiah-k/medre-adapter-xmpp)                | Multi-user rooms and direct conversations              | [Guide](docs/ops/transport-setup/xmpp.md)        |
+| [Chatmail](https://github.com/jeremiah-k/medre-adapter-chatmail)        | Accepted groups and direct chats through Chatmail core | [Guide](docs/ops/transport-setup/chatmail.md)    |
+| [SimpleX Chat](https://github.com/jeremiah-k/medre-adapter-simplexchat) | Allowlisted groups and direct conversations            | [Guide](docs/ops/transport-setup/simplexchat.md) |
+
+Install only the adapters you need, for example:
+
+```bash
+medre adapters install xmpp chatmail simplexchat
+```
+
+Community adapters can implement the same entry-point contracts; runtime startup
+never installs Python packages. Native libraries and account/profile preparation
+follow each provider's setup guide. See
+[package management](docs/ops/package-management.md) for persistent CLI tools
+and [adapter sources](docs/ops/adapter-installation.md) for pinned projects.
+
+## Documentation
+
+| Start here                                     | For                                                              |
+| ---------------------------------------------- | ---------------------------------------------------------------- |
+| [Getting Started](docs/ops/getting-started.md) | Install, smoke, guided bridge, native connections                |
+| [Operator guides](docs/ops/README.md)          | Package management, running, evidence, recovery, troubleshooting |
+| [Developer guides](docs/dev/README.md)         | Contributing, testing, authoring adapters                        |
+| [Technical specification](docs/spec/README.md) | Normative contracts and supported guarantees                     |
+
+New operators can optionally use [AI-assisted setup](docs/ops/ai-assisted-setup.md).
+Real-world testing and reproducible, sanitized bug reports are welcome—never
+share credentials, radio keys, identity files, or unredacted databases.
+
+## License
+
+MEDRE-owned core source is [MIT-licensed](LICENSE). Adapter source and its SDKs
+retain their respective terms, which may include GPL and the Reticulum License.
+See [dependency licensing](docs/dev/licensing.md) before redistribution.

medre-0.1.0/docs/schemas/README.md

@@ -0,0 +1,165 @@
+# JSON Schemas
+
+Machine-readable JSON Schema definitions for MEDRE data structures and stable
+adapter-owned serialization contracts. Core schemas mirror source models; adapter
+contract schemas mirror their projection helpers and normative specifications.
+
+Source distributions include this directory, including test examples. Wheels
+include only the manifest and frozen normative schema definitions, byte-for-byte,
+under `medre/_schemas`; examples are deliberately excluded. Installed consumers
+can read them with
+`importlib.resources.files("medre").joinpath("_schemas")` without a Git checkout.
+
+## Schema Files
+
+| Schema                                           | Source Type                                                            | Description                                                                                                                   |
+| ------------------------------------------------ | ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `readiness-report.schema.json`                   | `medre readiness --json`                                               | Versioned offline provider/configuration facts and explicit absence of runtime or recipient observations                      |
+| `canonical-event.schema.json`                    | `CanonicalEvent` (`src/medre/core/events/canonical.py`)                | Core event record flowing through the pipeline                                                                                |
+| `content-inventory.schema.json`                  | `SQLiteStorage.inspect_content_inventory`                              | Read-only logical bytes and consumers without message values                                                                  |
+| `content-retention-preview.schema.json`          | `SQLiteStorage.preview_content_retention`                              | Bounded aggregate preview with outcome counts and one optional (created_at, event_id) continuation; the CLI omits that cursor |
+| `content-retention-status.schema.json`           | `medre storage retention status`                                       | Read-only, content-free retention policy status with heartbeat observation and preview rollup                                 |
+| `content-retention-activation.schema.json`       | `medre storage retention activate`                                     | Content-free result of opening a new operator activation epoch                                                                |
+| `storage-column-classification.schema.json`      | Declared registry (`src/medre/core/storage/classification.py`)         | Versioned export of the column-level ownership classes over persistent storage tables and columns                             |
+| `event-content-release-assessment.schema.json`   | `SQLiteStorage.assess_event_content_release`                           | Metadata-only, non-authorizing per-event release assessment                                                                   |
+| `canonical-event.schema.yaml`                    | YAML mirror of `canonical-event.schema.json`                           | Same validation structure as canonical JSON (some explanatory descriptions differ); not an instance document                  |
+| `styled-text.schema.json`                        | `StyledText` / `TextSpan`                                              | Optional semantic presentation over canonical plain text                                                                      |
+| `attachment.schema.json`                         | `AttachmentDescriptor`                                                 | Retained/unavailable descriptors and retention-pending input                                                                  |
+| `delivery-receipt.schema.json`                   | `DeliveryReceipt` (`src/medre/core/events/canonical.py`)               | Append-only delivery status record                                                                                            |
+| `delivery-observation.schema.json`               | `DeliveryObservation` (`src/medre/core/events/canonical.py`)           | Append-only post-handoff transport evidence                                                                                   |
+| `delivery-result.schema.json`                    | `AdapterHandoffResult` (`src/medre/core/contracts/delivery.py`)        | Successful synchronous adapter hand-off fact                                                                                  |
+| `radio-text-plan.schema.json`                    | `RadioTextPlan` (`src/medre/core/rendering/radio_text.py`)             | Immutable multipart radio text wire plan                                                                                      |
+| `radio-local-handoff.schema.json`                | `RadioLocalHandoff` (`src/medre/core/storage/radio_handoff.py`)        | Synchronous radio local handoff reference scoped to one packet                                                                |
+| `radio-attempt-progress.schema.json`             | `StoredRadioAttempt` (`src/medre/core/storage/radio.py`)               | Attempt-bound radio handoff progress retained per outbox attempt                                                              |
+| `radio-attempt-inspection.schema.json`           | Dict shape (`medre.core.recovery.radio_assessment`)                    | Read-only exact radio attempt inspection with continuation assessment                                                         |
+| `bridge-context.schema.json`                     | Dict shape (`medre.core.rendering.bridge_context`)                     | Cross-platform relay context claims retained on canonical events                                                              |
+| `lifecycle-drill-report.schema.json`             | Dict shape (`medre.runtime.drill.run_drill`)                           | Synthetic configuration/startup drill assignment and coverage evidence                                                        |
+| `drill-step.schema.json`                         | Dict shape (`medre.runtime.drill`)                                     | Single ordered evidence step within a lifecycle drill report                                                                  |
+| `runtime-snapshot.schema.json`                   | `RuntimeSnapshot` (`src/medre/core/supervision/diagnostics.py`)        | Point-in-time runtime state snapshot                                                                                          |
+| `diagnostics.schema.json`                        | Dict shape (`capture_runtime_snapshot().to_dict()`)                    | Diagnostics collector output                                                                                                  |
+| `evidence-bundle.schema.json`                    | Dict shape                                                             | `medre evidence` bundle structure                                                                                             |
+| `native-qualification.schema.json`               | Dict shape (`scripts/ci/native_qualification.py`)                      | Content-free, revision-bound CI proof for MeshCore and LXMF core replay; not a runtime API                                    |
+| `adapter-config.schema.json`                     | Per-transport configs                                                  | Adapter configuration shapes                                                                                                  |
+| `routing-config.schema.json`                     | `RouteConfig`, `BridgePolicy`                                          | Route matching configuration shapes                                                                                           |
+| `runtime-config.schema.json`                     | `RuntimeConfig` (`src/medre/config/model.py`)                          | Shared runtime configuration across runtime, logging, storage, retry, limits, adapters, and routes                            |
+| `dev-environment.schema.json`                    | `DevEnvironment` (`src/medre/dev_environment.py`)                      | Checkout `.medre-dev.yaml` preferences for adapter selection and SDK extras                                                   |
+| `package-sources.schema.json`                    | Deployment source catalog                                              | Adapter distribution aliases and source overrides                                                                             |
+| `native-bridge-context-expectations.schema.json` | Dict shape (native campaign report)                                    | Optional bridge-context destination expectations in native campaign reports                                                   |
+| `stopped-state-inventory.schema.json`            | Dict shape (`medre.maintenance.stopped_inventory`)                     | Operator-declared stopped installation inventory for capture/verify/restore                                                   |
+| `stopped-state-snapshot.schema.json`             | Dict shape (`medre.maintenance.stopped_snapshot`)                      | Captured stopped-state snapshot manifest checked during verify and restore                                                    |
+| `operator-decision-inspection.schema.json`       | `medre inspect decisions`                                              | Versioned, read-only decision audit with unauthenticated actor provenance                                                     |
+| `inbound-pressure.schema.json`                   | `medre inspect pressure`                                               | Read-only pre-admission pressure aggregates over the closed six-outcome vocabulary; counters only, never payloads             |
+| `recovery-action.schema.json`                    | `RecoveryAction` (`medre.core.observability.recovery`)                 | Current destination ownership and read-only recovery guidance                                                                 |
+| `exact-target-preview.schema.json`               | `ExactTargetPreview` (`medre.core.observability.exact_target`)         | Typed read-only observation of one exact delivery target with a closed category vocabulary                                    |
+| `exact-target-decision.schema.json`              | `ExactTargetDecision` (`medre.core.storage.sqlite._operator_decision`) | Immutable audit acknowledgement of one exact-target operator decision; never a dispatch grant                                 |
+| `live-health.schema.json`                        | `LiveHealthSnapshot` (`medre.core.supervision.health`)                 | Current manual samples and native health notifications                                                                        |
+
+Executable SQLite fragments for typed admission routing facts, frozen outbox
+work ownership, and the durable content-retention activation epochs are
+published as `event-routing-facts.schema.sql`,
+`outbox-dispatch-snapshots.schema.sql`, and
+`content-retention-epochs.schema.sql`. Their table constraints and declared
+indexes are checked against the authoritative SQLite DDL.
+
+## Examples
+
+The `native-qualification.schema.json` entry above describes CI test evidence,
+not a runtime observation API. See
+[native qualification](../dev/native-qualification.md) for its independent
+source, SDK, and harness checks.
+
+The `examples/` directory contains representative JSON payloads validated
+against these schemas.
+
+| Example                                            | Description                        |
+| -------------------------------------------------- | ---------------------------------- |
+| `examples/matrix-native-metadata-example.json`     | Matrix native metadata payload     |
+| `examples/meshtastic-native-metadata-example.json` | Meshtastic native metadata payload |
+| `examples/meshcore-native-metadata-example.json`   | MeshCore native metadata payload   |
+| `examples/lxmf-native-metadata-example.json`       | LXMF native metadata payload       |
+| `examples/delivery-observation-example.json`       | Post-handoff delivery observation  |
+
+## Generation
+
+Schemas are hand-authored to match the current source types or adapter contract.
+When a source model or versioned adapter shape changes, update the corresponding
+schema and run the schema validation tests:
+
+```bash
+python -m pytest tests/test_docs_schema_examples.py tests/test_docs_schema_drift.py -q
+```
+
+## Drift Detection
+
+Tests validate examples against their schemas and check that schema required
+fields align with example payloads. When example payloads or schemas change,
+update both in the same commit.
+
+For stable source models (`CanonicalEvent`, `DeliveryReceipt`,
+`DeliveryObservation`, `AdapterHandoffResult`), tests also compare top-level
+schema properties against source dataclass fields. If a source model adds or
+renames a field without updating the schema, the test fails. These
+source-drift tests live in `tests/test_docs_schema_drift.py`.
+
+For built-in transport-native metadata,
+`tests/test_prerelease_contract_guards.py` compares the source schema-version
+constant with the corresponding JSON Schema `const` and example payload. Each
+transport therefore has one version authority across source, machine schema,
+and example data.
+
+`AdapterCapabilities` are checked separately by
+`tests/test_capability_conformance.py` against
+`docs/spec/transport-profiles/*-capabilities.json`.
+
+Runtime and routing schemas describe the shared configuration structure. They
+accept community transport and destination kind names. `medre config check`
+validates installed-provider availability and invokes adapter-owned native
+address validators. Static schema validation alone cannot verify which Python
+providers are installed in an operator's environment.
+
+Native metadata schemas and validated examples belong to their adapter repositories; see the [metadata ownership contract](../spec/metadata.md#3-adapter-owned-native-metadata).
+
+`content-collection-state.schema.json` defines the closed aggregate worker
+blocks emitted by `MedreApp.diagnostic_snapshot()` and
+`medre.runtime.snapshot.build_runtime_snapshot()`. These producers differ
+from `core.supervision.capture_runtime_snapshot()`, whose existing
+`runtime-snapshot.schema.json` and `diagnostics.schema.json` contracts remain
+separate. Unknown worker fields, content, and event identifiers are refused.
+
+## 0.1.0 release schema freeze
+
+`v0.1.0.freeze.json` records the SHA-256 of every exported top-level JSON,
+YAML and SQL schema artifact in this distribution at the first-release
+baseline. `tests/test_schema_freeze_010.py` rejects additions, deletions and
+content changes without a deliberate update. This is a release-review gate,
+**not** a schema-version negotiation mechanism and not a promise to migrate
+unpublished prerelease databases. The freeze covers normative schemas, not
+examples or runtime data. After the first tag, changes must follow the
+versioning policy (including independent adapter-native and SQLite versions),
+with contract tests and a documented compatibility decision; never silently
+replace a released freeze manifest.
+
+### Bounded source-native facts (proposed initial 0.1.0 contract)
+
+`bridge_context.source.native_facts` is an optional **public** source-owned
+projection: `{"namespace": "meshtastic", "fields": {"portnum": 1}}`.
+Here *facts* means **bounded, adapter-selected assertions about its native
+source**, not facts independently verified by the receiving transport. The
+namespace identifies the native producer type, not an authenticated sender; structural validation does
+not authenticate the claim. Treat these values as untrusted presentation hints
+unless an explicit, independent authorization check permits their use.
+Its namespace identifies the native producer, while the envelope remains
+independent of any destination transport. At most twelve bounded scalar facts
+can cross a bridge. The source must intentionally select these from its native
+metadata via `public_facts`; other packet data, credentials, keys and encrypted
+material are never copied automatically. An untrusted inbound projection can
+inform display only; it never authorizes a relay, overrides the actual sender,
+or binds a native reply/reaction. Core keeps a single version-1 context across
+Matrix, LXMF, and XMPP. A context may be absent without dropping message text.
+
+## Git checkout line endings
+
+A main-to-candidate Git checkout may retain unchanged CRLF files. Packaging
+MUST emit the exact frozen bytes. LF reconstruction is permitted only when
+its digest matches the freeze manifest; every other byte change MUST fail
+the build. Fresh checkouts retain the explicit `-text` attribute policy.