Add commercial evidence file verification command plan

Author: ammarheidari

README.md

@@ -74,7 +74,7 @@ The first production milestone is M3UA over a transport abstraction. SCCP, TCAP,
 | Commercial evidence readiness lockdown | Phase 36 foundation-complete: release target locking, protected secret readiness, evidence retention mapping, commercial evidence checklist, release preflight, protected release environments, dossier handoff, go/no-go gating, status reporting, and final validation are available; RC and stable publication remain blocked until retained commercial release evidence is complete |
 | Commercial evidence execution orchestration | Phase 37 foundation-complete: evidence execution run identity, stage catalog, operator command plan, execution environment contract, artifact collection manifest, digest/redaction verification, blocker classification, retry/resume policy, status reporting, and final validation are available; real retained execution artifacts are still required before commercial publication |
 | Commercial evidence artifact intake | Phase 38 foundation-complete: artifact intake target identity, artifact source registration, SHA-256 digest coverage, redaction review, completeness evaluation, dossier reporting, promotion handoff, execution-to-dossier bridge, status reporting, and final validation are available, binding a stable intake id, reviewer identity, UTC receipt time, run-scoped dossier root, concrete source paths, unique retained dossier paths, retained digests, trace-bearing artifact approvals, explicit intake blockers, retained Markdown summary, digest-covered handoff, end-to-end intake assembly, and intake readiness status to a governed execution run; real artifact files are still required before commercial publication |
-| Commercial evidence file verification | Phase 39 in progress: retained file evidence item verification, retained file manifest coverage, file verification blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, and verified promotion gating are available, checking file existence, non-empty size, SHA-256 validity, digest match, UTC observation time, unique retained paths, promotion-required handoff coverage, explicit verification blockers, reviewer identity, immutable retention, UTC retention windows, minimum duration, deterministic aggregate ledger digests, sealed ledger attachment coverage, trace-bearing redaction approval, commercial readiness report presence, and explicit promotion approval; command plan, status reporting, and final validation remain |
+| Commercial evidence file verification | Phase 39 in progress: retained file evidence item verification, retained file manifest coverage, file verification blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, verified promotion gating, and command planning are available, checking file existence, non-empty size, SHA-256 validity, digest match, UTC observation time, unique retained paths, promotion-required handoff coverage, explicit verification blockers, reviewer identity, immutable retention, UTC retention windows, minimum duration, deterministic aggregate ledger digests, sealed ledger attachment coverage, trace-bearing redaction approval, commercial readiness report presence, explicit promotion approval, and workflow-ready verification command order; status reporting and final validation remain |
 
 ## Requirements
 

docs/PHASE39_COMMERCIAL_EVIDENCE_FILE_VERIFICATION.md

@@ -93,6 +93,21 @@ Publication attachment readiness does not publish anything. It only proves that
 
 The gate returns concrete blocker labels. It does not publish a package; it only allows the release workflow to consider the verified evidence set.
 
+## Unit 8 - File Verification Command Plan
+
+`SigtranCommercialEvidenceFileVerificationCommandPlan` defines the workflow-ready execution order:
+
+1. Observe retained files.
+2. Compute retained file digests.
+3. Compare observed digests with promotion handoff digests.
+4. Write the file verification report.
+5. Write the retention ledger.
+6. Create the integrity seal.
+7. Create the publication attachment manifest.
+8. Evaluate the promotion gate.
+
+The plan is package-neutral and shell-neutral. It describes the expected workflow contract so CI, a CLI, or a release operator can materialize equivalent commands without changing SDK domain APIs.
+
 ## Validation
 
 Each unit in this phase is validated with:

docs/PHASE39_SUMMARY.md

@@ -11,7 +11,8 @@ Phase 39 prepares the SDK to verify retained commercial evidence files after art
 - Integrity seal that computes a deterministic aggregate SHA-256 digest over the retention ledger.
 - Publication attachment manifest that covers sealed ledger entries and protects trace-bearing artifacts through redaction approval.
 - Verified promotion gate that requires ready attachments, ready integrity seal, ready retention ledger, verified file report, commercial readiness report, and explicit approval.
+- File verification command plan that orders observation, digest computation, comparison, report, ledger, seal, attachment, and promotion-gate steps.
 
 ## Readiness Position
 
-The phase is in progress. Retained file evidence item verification, retained file manifest coverage, blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, and verified promotion gating are available. Command plan, status reporting, and final validation remain.
+The phase is in progress. Retained file evidence item verification, retained file manifest coverage, blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, verified promotion gating, and command planning are available. Status reporting and final validation remain.

docs/PHASE_INDEX.md

@@ -43,7 +43,7 @@ This index is the complete phase map for Sigtran.NET. It links each phase to the
 | 36 | Commercial evidence readiness lockdown | [Phase 36 Commercial Evidence Readiness Lockdown](PHASE36_COMMERCIAL_EVIDENCE_READINESS_LOCKDOWN.md), [Phase 36 Summary](PHASE36_SUMMARY.md) | Foundation complete; real commercial evidence still required |
 | 37 | Commercial evidence execution orchestration | [Phase 37 Commercial Evidence Execution Orchestration](PHASE37_COMMERCIAL_EVIDENCE_EXECUTION_ORCHESTRATION.md), [Phase 37 Summary](PHASE37_SUMMARY.md) | Foundation complete; real execution artifacts still required |
 | 38 | Commercial evidence artifact intake | [Phase 38 Commercial Evidence Artifact Intake](PHASE38_COMMERCIAL_EVIDENCE_ARTIFACT_INTAKE.md), [Phase 38 Summary](PHASE38_SUMMARY.md) | Foundation complete; real artifact files still required |
-| 39 | Commercial evidence file verification | [Phase 39 Commercial Evidence File Verification](PHASE39_COMMERCIAL_EVIDENCE_FILE_VERIFICATION.md), [Phase 39 Summary](PHASE39_SUMMARY.md) | In progress; promotion gate complete |
+| 39 | Commercial evidence file verification | [Phase 39 Commercial Evidence File Verification](PHASE39_COMMERCIAL_EVIDENCE_FILE_VERIFICATION.md), [Phase 39 Summary](PHASE39_SUMMARY.md) | In progress; command plan complete |
 
 ## Current Commercial Gate
 

docs/SDK_ROADMAP.md

@@ -347,7 +347,7 @@ Status: Phase 38 is foundation-complete. Artifact intake target identity binds a
 - Track file existence, size, observation time, digest match, retention, integrity sealing, publication attachment, promotion gate, and operator command contracts.
 - Keep file verification separate from real lab execution: verification contracts can evaluate retained files, but publication remains blocked until real files are present and approved.
 
-Status: Phase 39 is in progress. Retained file evidence item verification now checks existence, non-empty size, SHA-256 validity, digest match, and UTC observation time. Retained file manifest coverage now verifies that every promotion-required handoff item has a unique verified retained file. File verification reporting now exposes missing, empty, invalid digest, digest mismatch, non-UTC observation, duplicate path, and incomplete handoff blockers. Retention ledger modeling now binds verified files to reviewer identity, immutable retention, UTC retention windows, and minimum duration checks. Integrity sealing now computes and validates a deterministic aggregate SHA-256 digest over the ledger. Publication attachment planning now covers sealed ledger entries, validates attachment digests, includes the commercial readiness report, and blocks trace-bearing attachments without redaction approval. Verified promotion gating now requires ready attachments, ready integrity seal, ready retention ledger, verified file report, commercial readiness report presence, and explicit approval before evidence can move into release publication decisions. Command plan, status reporting, and final validation remain in progress.
+Status: Phase 39 is in progress. Retained file evidence item verification now checks existence, non-empty size, SHA-256 validity, digest match, and UTC observation time. Retained file manifest coverage now verifies that every promotion-required handoff item has a unique verified retained file. File verification reporting now exposes missing, empty, invalid digest, digest mismatch, non-UTC observation, duplicate path, and incomplete handoff blockers. Retention ledger modeling now binds verified files to reviewer identity, immutable retention, UTC retention windows, and minimum duration checks. Integrity sealing now computes and validates a deterministic aggregate SHA-256 digest over the ledger. Publication attachment planning now covers sealed ledger entries, validates attachment digests, includes the commercial readiness report, and blocks trace-bearing attachments without redaction approval. Verified promotion gating now requires ready attachments, ready integrity seal, ready retention ledger, verified file report, commercial readiness report presence, and explicit approval before evidence can move into release publication decisions. Command planning now orders observation, digest computation, comparison, report, ledger, seal, attachment, and promotion-gate work for workflow materialization. Status reporting and final validation remain in progress.
 
 ## Recommended First Deliverable
 

src/Sigtran.NET.Tests/Program.cs

@@ -303,6 +303,7 @@
 Run("SIGTRAN commercial evidence integrity seal verifies ledger digest", SigtranCommercialEvidenceIntegritySealVerifiesLedgerDigest);
 Run("SIGTRAN commercial evidence publication attachments protect trace artifacts", SigtranCommercialEvidencePublicationAttachmentsProtectTraceArtifacts);
 Run("SIGTRAN commercial evidence verified promotion gate requires approval", SigtranCommercialEvidenceVerifiedPromotionGateRequiresApproval);
+Run("SIGTRAN commercial evidence file verification command plan orders execution", SigtranCommercialEvidenceFileVerificationCommandPlanOrdersExecution);
 Run("SIGTRAN status capabilities use domain documentation labels", SigtranStatusCapabilitiesUseDomainDocumentationLabels);
 Run("Native SCTP platform probe reports socket creation capability", NativeSctpPlatformProbeReportsSocketCreationCapability);
 Run("Native SCTP socket factory creates or reports unsupported platform", NativeSctpSocketFactoryCreatesOrReportsUnsupportedPlatform);
@@ -5124,6 +5125,24 @@ static void SigtranCommercialEvidenceVerifiedPromotionGateRequiresApproval()
     Assert(blocked.Blockers.Contains("commercial-evidence-approval-missing"), "promotion gate should expose approval blocker");
 }
 
+static void SigtranCommercialEvidenceFileVerificationCommandPlanOrdersExecution()
+{
+    SigtranCommercialEvidenceFileVerificationCommandPlan plan = CreateDefaultCommercialEvidenceFileVerificationCommandPlan();
+
+    Assert(plan.IsReady, plan.Describe());
+    AssertEqual(Enum.GetValues<SigtranCommercialEvidenceFileVerificationCommandKind>().Length, plan.Commands.Count, "file verification command count");
+    Assert(plan.UsesDeterministicOrder, "file verification commands should use deterministic order");
+    Assert(plan.CoversRequiredCommandKinds, "file verification commands should cover every required command kind");
+    Assert(plan.ProducesRequiredArtifacts, "file verification commands should produce required artifacts");
+    Assert(plan.ApprovalReservedForPromotionGate, "file verification commands should reserve approval for promotion gate");
+    Assert(plan.Commands[^1].RequiresApproval, "last file verification command should require approval");
+}
+
+static SigtranCommercialEvidenceFileVerificationCommandPlan CreateDefaultCommercialEvidenceFileVerificationCommandPlan()
+{
+    return SigtranCommercialEvidenceFileVerificationCommands.CreateDefault("artifacts/commercial-evidence");
+}
+
 static SigtranCommercialEvidenceVerifiedPromotionGateResult CreateDefaultCommercialEvidenceVerifiedPromotionGate(SigtranCommercialEvidencePublicationAttachmentManifest? attachmentManifest = null)
 {
     return SigtranCommercialEvidenceVerifiedPromotionGates.Evaluate(