Files
meshcore-analyzer/docs
199df07c21 docs(proto): correct route_type values to match the decoder (#2363) (#2367)
Fixes #2363.

The published contract described `route_type` as `0=DIRECT, 1=FLOOD,
2=reserved, 3=TRANSPORT`. Both decoders (`cmd/ingestor/decoder.go`,
`cmd/server/decoder.go` — `routeTypeNames`) and MeshCore's
`docs/packet_format.md` use:

```
0 = TRANSPORT_FLOOD, 1 = FLOOD, 2 = DIRECT, 3 = TRANSPORT_DIRECT
```

Updated:
- `proto/decoded.proto` — `DecodedHeader.route_type` and the
`route_type_name` value list
- `proto/packet.proto` — `Transmission.route_type` (same stale comment)
- `docs/api-spec.md` — Packet Object `route_type` line (same stale
comment)

Comment/doc-only; no generated code in-tree, no behaviour change.

Co-Authored-By: Claude <noreply@anthropic.com>

Co-authored-by: SaarMesh-Bot <300107934+SaarMesh-Bot@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
2026-11-08 17:12:37 +01:00
..