Skip to content

Latest commit

 

History

History
16 lines (15 loc) · 1.45 KB

File metadata and controls

16 lines (15 loc) · 1.45 KB

Repository Guidelines

  • Follow the existing C coding style when editing files in src/: 4-space indents, no tabs, braces on the same line as the control statement, and keep lines under 120 characters when practical.
  • Keep the documentation (README.md, configs/, handler_contract.txt) in sync with any changes to build steps, configuration keys, or HTTP/CLI interfaces you introduce.
  • Prefer updating or adding unit tests or sample configuration snippets when you change execution or networking behavior.
  • Use the top-level Makefile targets instead of ad-hoc compiler invocations so build instructions stay accurate.
  • When editing any scripts/**/exec-handler.sh, ensure the /sys/help payload enumerates every available help endpoint so clients can discover them consistently (see scripts/vtx/sys_help.msg for the expected structure).
  • Prefer exposing configurable knobs through paired get/set commands plus a settings array in the help payload so the UI can auto-generate typed controls (select/range/toggle/text) and refresh values without manual wiring.
  • UI screenshots are not required unless explicitly requested.
  • When touching anything under html/, especially the segmented web UI assets, audit related HTML, CSS, and JS files in the same feature bundle so the views stay in sync. Treat the VRX/VTX bundles and shared assets as a unit: ensure new resources are referenced, installed, and served correctly before submitting changes.