Discovery: Add Manifest YAML as production source of truth #109
Description
Summary
We want a production mode where discovery is stable and explicitly defined. This requires a Manifest YAML that declares stable IDs, intended structure, and relations.
Manifest should allow:
- Stable IDs for Areas, Components, Apps, and optional Functions
- Explicit relations (App belongs to Component, App depends on App, Function includes Apps or Components)
- Linking runtime ROS nodes to declared Apps and Runtime processes
Proposed solution (optional)
- Design a Manifest YAML schema that represents Area, Component, App, Function and relations.
- Implement parsing and validation with clear error messages.
- Implement runtime linking logic (bind ROS node name and namespace to Manifest App entries).
- Define what happens when runtime has nodes not in Manifest
Additional context (optional)
The goal is an adoption path where dev mode can be heuristic, but production can have full control and stable IDs. Manifest should be the source of truth when it exists.