G2.5-A2.1: command-bound high-speed stimulus witness

[masarray]

Status

G2.5-A2.1 is CODE/CI READY and PHYSICAL-A2.1 PENDING. It is stacked on exact physical A2 candidate 6be89d0ead77d8b6cc97665d47e0eb3abe1f6876.

Physical A2 proved the MMS association/sampler healthy (1280 cycles, 0 read failures) but observed zero transitions because its 24-candidate set was global across multiple logical devices. A2.1 removes that ambiguity by binding the witness to the exact existing ARSAS command object.

Exact A2.1 field candidate: f3100b3588cc9da78569ce1a9479b14e4437165b.
ARIEC61850 remains pinned to physical-proven 26c85400a4da230c4429e6302847f230385b6687.

Contract

• identity-compatible InformationReportProven profile required;
• one isolated read-only MMS association;
• report attribute probing disabled;
• pre-command baseline captured before the operator command from resolved ControlStatusReference points plus bounded position/command-correlation status points;
• service subscribes only to existing SignalDefinition.PropertyChanged and captures the exact signal when ControlCommandBusy=true;
• existing SBO/Operate/control executor is untouched and is not delayed, wrapped or re-issued;
• after command capture, sampling narrows to at most 6 points around the exact ControlStatusReference;
• focused observation window <=5 s with <=1 ms inter-cycle delay;
• output classifies persistent/latched vs momentary/pulse transitions and ranks exact candidates for narrow A3 dchg qualification.

Operator flow

1. Ctrl+Shift+F arms A2.1.
2. Wait for G2.5-A2.1 READY — ISSUE ONE ARSAS COMMAND.
3. Issue exactly ONE already-proven safe OPEN/CLOSE from the normal ARSAS Command Panel.
4. After G2.5-A2.1 COMMAND CAPTURED, do not issue another command.
5. Copy full evidence.

Safety

The witness itself performs zero control/report mutation:

• no change to existing control transaction source;
• no RCB attribute access or write;
• no RptEna/Resv/DatSet/TrgOps/OptFlds mutation;
• no GI;
• no Define/DeleteNamedVariableList;
• no report monitor;
• no profile save/advance;
• no ProductionEligible change;
• production automatic dynamic reporting remains OFF.

The one OPEN/CLOSE is the operator-requested existing ARSAS control action, not a command generated by the witness.

Scope relative to physical A2

Exactly 5 changed files:

• App.xaml.cs — one added install line only;
• DynamicReportCommandBoundWitnessUiBehavior.cs — new;
• DynamicReportQualificationResultWindow.G25A21.cs — new;
• Services/DynamicReportCommandBoundStimulusWitnessService.cs — new;
• tests/ARSAS.Tests/DynamicReportCommandBoundStimulusWitnessServiceTests.cs — new.

No engine changes. No changes to MainWindow control executor, SignalDefinition, G2.5-A/A1/A2 service, or production runtime.

CI — exact head f3100b35...

• Build ARSAS #1386 — run 32467297460 — PASS
  • source/license invariants PASS
  • premium/release invariants PASS
  • exact engine checkout/API verification PASS
  • full solution build PASS
  • full ARSAS regression PASS
  • portable publish PASS
  • portable single-EXE smoke PASS
• Validate SV evidence bundles #498 — run 32467297503 — PASS
  • focused restore/build PASS
  • focused regression PASS

Artifacts

• portable artifact 9441269477, SHA-256 3d6518fec0e9036688c86419a2b4c94d3a562ee2d4bec71c132c25b1ff052c65
• test evidence artifact 9441251361, SHA-256 76f8c63fed8c7d3e36730970701e4f6af9027c286cc65ff19689b48fd32c18de
• source snapshot artifact 9441208633, SHA-256 0500de5da36e4ae99163847c623ece5bee29b7b48adce8f73961bc17de39fe0e

Merge gate

Do not merge yet. Physical A2.1 must capture the exact ARSAS command and identify at least one command-bound status transition with association healthy. A2.1 PASS only identifies the exact physical MMS candidate; it does not yet prove spontaneous dchg reporting. Production automatic dynamic reporting remains OFF.