You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
23 lines
948 B
23 lines
948 B
# ADR 0004: Reporting v2 Replaces Legacy Dashboard Protocol
|
|
|
|
## Status
|
|
Proposed
|
|
|
|
## Context
|
|
The old dashboard/report socket has shaped parts of the current implementation and has caused operational friction. FreeDMR 1.x remains live while FreeDMR 2 is developed.
|
|
|
|
## Decision
|
|
FreeDMR 2 reporting is a new structured event contract. The old dashboard/report socket is not a compatibility constraint inside the core.
|
|
|
|
## Rationale
|
|
Reporting must be observational only. A clean event schema avoids leaking legacy `BRIDGES`/`SYSTEM` state into the new packet core.
|
|
|
|
## Consequences
|
|
The dashboard must be updated or served by an adapter. The core can emit stable v2 events without preserving legacy report names.
|
|
|
|
## Compatibility
|
|
Old dashboard support belongs in a sidecar or adapter, not in packet routing.
|
|
|
|
## Testing Requirements
|
|
Tests must assert expected v2 events for server, client, subscription, call, mesh, loop, and reporting-health changes.
|