glossy-msp430

Use the C# UnitTest console tool (UnitTest/UnitTest.csproj) to exercise the glossy-msp430 GDB RSP firmware against real MSP430 hardware over a serial port. Use whenever asked to "test the firmware", "try it on hardware", "run the unittest tool", or to validate a firmware change end-to-end on a physical probe. Covers the COM-port map per probe board, the full build (meson) -> flash (arm-none-eabi-gdb + UnitTest/batch scripts) -> TRACESWO workflow, safe vs. destructive test numbers, the chip-identity prerequisite gate, and how to send one-off raw `monitor` commands without extending the C# tool.

Evaluate a logic-analyzer (LA) capture of the 4-wire JTAG bus (TMS/TCK/TDI/ TDO/TRST) exported as a Saleae-style transition CSV. Use whenever asked to look at, decode, or check timing/alignment in a JTAG LA capture — e.g. "check the LA capture", "is TMS centered on the clock", "decode this jtag_scan capture", "what does the logic analyzer show for frame N", cnt_offset/TMS-phase tuning work, or verifying a fix against a fresh capture. Covers the fixed CSV column mapping, the existing TAP-FSM decoder script, how to segment individual JTAG frames out of a transition export, and the recipe for measuring TMS-to-TCK phase/setup-margin used for DtrigJtag `cnt_offset` calibration. Does NOT apply to Spy-Bi-Wire (SBW) captures — see the `decode_sbw*.py` scripts for that instead.

Add, remove, or rename a firmware source/header/resource file in glossy-msp430 while keeping BOTH build systems (Visual Studio/VisualGDB .vcxproj/.vcxitems AND the Meson CLI meson.build) in sync. Use whenever you create, delete, or rename a .cpp/.h/.c/.bin under Firmware.shared/, target.*/, or Funclets/. Covers the shared-vs-target scope rules, case-only renames, CRLF/BOM preservation, the drift-check script, and the headless verification build.