Add HistorianGrpcStoreForwardStatusProbe and the `grpc-sf-status-probe` CLI
command. The idle-baseline run against the live 2023 R2 server resolves the
plan's §9.3 handle question: the direct StorageService SF pull RPCs
(GetSFParameter / GetRemainingSnapshotsSize) require the OpenStorageConnection
console handle and are D2-gated (err 132, identical under read-only and
write-enabled sessions), while StatusService.GetHistorianConsoleStatus IS
reachable on the session string handle (=3 at idle).
Records the gRPC re-scope and the idle-baseline findings in
docs/plans/store-forward-cache-reverse-engineering.md §9. The probe writes
nothing and releases any console session immediately.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6mcaT2PjRFKcogzp9UkfC
docs/plans/write-commands-reverse-engineering.md (425 lines):
Plan for adding WriteValueAsync (AddS2 stream values), EnsureTags2 for
analog/discrete/string tags, and DelT for sandbox cleanup. Hard safety
rules center on a dedicated sandbox tag gated by env var, time-bounded
writes, SQL ground-truth verification per session, explicit rollback.
Five-step RE workflow mirrors the read/event decode (static IL discovery
-> instrument-wcf-writemessage capture -> instrument-wcf-readmessage
capture -> byte/IL alignment -> managed serializer + golden-byte tests).
Risks call out auth-chain unknowns, parameter-name-mismatch class,
silent-success failure modes, History-vs-Storage service question.
docs/plans/store-forward-cache-reverse-engineering.md (501 lines):
Plan for replacing the synthesized GetStoreForwardStatusAsync with a
real implementation. Architecture investigation already partially
answered via IL inspection during planning: ArchestrA.HistorianAccess.
GetStoreForwardStatus (token 0x06006187) reads an in-process C struct
via calli to mdas_GetStorageStatus, kept current by server-pushed WCF
callbacks (IStatusServiceContract2.SetStoreForwardEvent). CSFConnection.
GetSFPipeName indicates a separate Named Pipe sidecar exists when SF
is configured. Five parallelizable discovery workstreams, six concrete
RE steps with cited tokens, eight risks, eight success criteria.
Both plans deliberately produce no code changes and no captures. They
exist so the next implementer can start with full context.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Joseph Doherty