[MOR-1630] capture FTX-1 TX-time command acceptance evidence

[morozsm]

Linear: MOR-1630
Parent GitHub: #2541

Parent: MOR-1500
Source authority: origin/main f016380

Outcome
Produce the owner-required hardware evidence for FTX-1 command acceptance while keyed, especially modulation-input source changes, without changing code or profile data in this issue.

Owned paths
None. Evidence is recorded in the issue using the existing validation/logging workflow.

Acceptance criteria

• With safe station setup and explicit operator confirmation, exercise the bounded FTX-1 matrix for modulation-input source and representative TX-SAFE controls while keyed.
• Record exact candidate SHA, physical safety state, command/ACK/readback evidence, timeouts/rejections, and restoration to baseline.
• Do not infer CAT acceptance from disabled front-panel controls.
• Distinguish accepted, ignored, rejected, and unconfirmed outcomes; never call an ignored command applied.
• If any family is not accepted, open a separate <=3-file profile-tightening child; do not edit profiles in this evidence issue.
• Parent MOR-1500 remains incomplete until this evidence and any resulting tightening child are resolved.

Dependencies
The evidence procedure may be prepared now. Actuation requires the owner at the FTX-1 bench and a candidate containing B2; run after MOR-1500 B2 is available.

Scope guardrails

• No repository, profile, code, fixture, branch, worktree, or PR changes.
• Actuation begins only with the owner present and an explicit physical safety-state confirmation.
• Use only the bounded matrix in this issue; no unrelated radio commands or exploratory TX.
• Pin the exact B2-containing candidate SHA and preserve foreground logs/evidence.
• Stop and create a separate bounded implementation child for any required profile tightening.

Project fields
Priority=P1; Risk=high; Size=S; Phase=stable; Owner=mixed; WorkType=spike.