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-03-12 14:18:35 +08:00
2023-08-04 18:20:06 +10:00
2023-08-04 18:20:06 +10:00
2023-08-04 18:20:06 +10:00
2026-02-23 23:26:42 +08:00
2023-09-07 17:31:11 +07:00
2026-04-11 19:54:49 +08:00