Discovery: Add Beacon data as additional discovery mechanism #111
Description
Summary
Beacon is an optional mechanism where Apps announce runtime hints to make discovery more accurate without requiring a full Manifest.
Examples of hints:
- App identity and stable ID binding
- Function membership
- Dependencies
- Extra metadata useful for diagnostics UX
Beacon is valuable for dynamic systems (nodes joining mid-session, OTA updates), but it is also requires changes in the whole system.
Proposed solution (optional)
Implement Beacon as an enrichment provider that plugs into the merge pipeline:
- Choose a Beacon transport (topic publication or parameter based, or both)
- Define a small Beacon message format
- Define TTL and expiry rules if using topic based announcements
- Define polling strategy if using parameters
- Merge rules should never redefine structure, only enrich declared or discovered entities