YueGuobin 3f15ac38f6
feat(marker): add optional color field to marker data model
Add a user-chosen hex color (e.g. '#ff5722') to each marker, stored in
Link._markers alongside bpf/tag/enabled. The color:

- Is serialized with the link (asdict) and persisted in the topology, so
  it survives project reload and is consistent across devices.
- Never reaches uBridge (compute ignores it) — it is purely a Web UI
  concern.
- Can be updated independently of the BPF (color-only changes skip the
  ubridge round-trip).

MarkerCreate schema gains color: Optional[str]; start_marker and
update_marker carry it through; REST create/update endpoints pass it.

The marker.match WebSocket event stays lean (no color) — the Web UI maps
filter -> color from the link state it already holds.
2026-07-16 00:39:51 +08:00
..
2026-06-16 23:04:05 +08:00
2026-04-11 19:22:05 +08:00
2026-05-09 18:23:00 +08:00
2026-06-16 00:34:11 +08:00
2026-05-09 18:23:00 +08:00
2024-04-22 19:08:45 +07:00
2026-03-11 18:51:32 +01:00