Add commercial evidence filesystem command materialization status

Author: ammarheidari

README.md

@@ -75,7 +75,7 @@ The first production milestone is M3UA over a transport abstraction. SCCP, TCAP,
 | 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 foundation-complete: retained file evidence item verification, retained file manifest coverage, file verification blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, verified promotion gating, command planning, status reporting, final validation, and documentation alignment 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, workflow-ready verification command order, and readiness status separation; real retained file evidence remains required before commercial publication |
-| Commercial evidence filesystem execution | Phase 40 in progress: filesystem observation, manifest execution, verification report execution, artifact writing, ledger execution, seal execution, publication attachment execution, and promotion execution are available, reading retained files from disk, computing real SHA-256 digests, reporting file existence and size, supporting retained-path-to-local-path overrides, building retained file manifests from real observations, exposing blocker-aware retained file reports from filesystem evidence, writing retained Markdown/TSV verification artifacts, creating retention ledgers from filesystem-backed reports, sealing those ledgers with deterministic aggregate SHA-256 digests, creating release dossier attachments with redaction approval gates, and evaluating reviewer-approved promotion gates; command materialization, status reporting, and final validation remain |
+| Commercial evidence filesystem execution | Phase 40 in progress: filesystem observation, manifest execution, verification report execution, artifact writing, ledger execution, seal execution, publication attachment execution, promotion execution, command materialization, and interim status reporting are available, reading retained files from disk, computing real SHA-256 digests, reporting file existence and size, supporting retained-path-to-local-path overrides, building retained file manifests from real observations, exposing blocker-aware retained file reports from filesystem evidence, writing retained Markdown/TSV verification artifacts, creating retention ledgers from filesystem-backed reports, sealing those ledgers with deterministic aggregate SHA-256 digests, creating release dossier attachments with redaction approval gates, evaluating reviewer-approved promotion gates, and writing ordered execution scripts; final validation remains |
 
 ## Requirements
 

docs/PHASE40_COMMERCIAL_EVIDENCE_FILESYSTEM_EXECUTION.md

@@ -97,6 +97,18 @@ This unit connects sealed filesystem evidence to release dossier attachment plan
 
 This unit makes the filesystem-backed evidence path promotion-aware while preserving the existing commercial approval gate.
 
+## Unit 9 - Command Materialization And Interim Status
+
+`SigtranCommercialEvidenceFileSystemCommandMaterializer` writes a retained shell script from the commercial evidence file verification command plan:
+
+- Preserves deterministic command order.
+- Writes the script to a retained filesystem path.
+- Includes the configured artifact root.
+- Includes every command from the command plan.
+- Keeps the promotion gate command visible as the explicit approval step.
+
+`SigtranCommercialEvidenceFileSystemExecutionStatus` reports the first nine completed filesystem execution capabilities and keeps `status-final-validation-pending` as a blocker until the final unit completes.
+
 ## Validation
 
 Each unit in this phase is validated with:

docs/PHASE40_SUMMARY.md

@@ -12,7 +12,9 @@ Phase 40 prepares the SDK to run commercial evidence file verification against r
 - Integrity seal execution that signs the filesystem-backed ledger with a deterministic aggregate SHA-256 seal.
 - Publication attachment execution that creates release dossier attachments from the filesystem-backed seal and requires redaction approval for trace-bearing artifacts.
 - Promotion gate execution that evaluates filesystem-backed attachments with reviewer identity, UTC evaluation time, and explicit approval blockers.
+- Command materialization that writes the ordered commercial evidence file verification plan to a retained shell script.
+- Interim status reporting for nine completed filesystem execution units, with final validation still pending.
 
 ## Readiness Position
 
-The phase is in progress. Filesystem observation, manifest execution, report execution, artifact writing, ledger execution, seal execution, publication attachment execution, and promotion execution are available. Command materialization, status reporting, and final validation remain.
+The phase is in progress. Filesystem observation, manifest execution, report execution, artifact writing, ledger execution, seal execution, publication attachment execution, promotion execution, command materialization, and interim status reporting are available. Final validation remains.

docs/PHASE_INDEX.md

@@ -44,7 +44,7 @@ This index is the complete phase map for Sigtran.NET. It links each phase to the
 | 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) | Foundation complete; real retained file evidence required |
-| 40 | Commercial evidence filesystem execution | [Phase 40 Commercial Evidence Filesystem Execution](PHASE40_COMMERCIAL_EVIDENCE_FILESYSTEM_EXECUTION.md), [Phase 40 Summary](PHASE40_SUMMARY.md) | In progress; filesystem promotion execution complete |
+| 40 | Commercial evidence filesystem execution | [Phase 40 Commercial Evidence Filesystem Execution](PHASE40_COMMERCIAL_EVIDENCE_FILESYSTEM_EXECUTION.md), [Phase 40 Summary](PHASE40_SUMMARY.md) | In progress; command materialization and interim status complete |
 
 ## Current Commercial Gate
 

docs/SDK_ROADMAP.md

@@ -355,7 +355,7 @@ Status: Phase 39 is foundation-complete. Retained file evidence item verificatio
 - Build verification manifests, reports, retained artifacts, ledger, seal, attachments, promotion gate, and command materialization from observed files.
 - Keep filesystem execution separate from commercial publication: helpers can verify real files, but publication remains blocked until retained evidence comes from an approved commercial run.
 
-Status: Phase 40 is in progress. Filesystem observation now reads retained files from disk, computes real SHA-256 digests, records file existence and size, and maps observations into the retained file verification model. Filesystem manifest execution now observes every promotion handoff item, supports retained-path-to-local-path overrides, and builds retained file manifests from real observations. Filesystem verification report execution now evaluates those manifests and exposes retained file blockers from real files. Verification artifact writing now retains a Markdown report and tab-separated observation manifest on disk. Retention ledger execution now creates ledger entries from filesystem-backed verification reports and written artifacts. Integrity seal execution now seals filesystem-backed ledgers with deterministic aggregate SHA-256 digests. Publication attachment execution now creates release dossier attachments from the filesystem-backed seal and requires approved redaction state for trace-bearing artifacts. Promotion execution now evaluates filesystem-backed attachments through reviewer approval, UTC evaluation, and explicit blockers. Command materialization, status reporting, and final validation remain in progress.
+Status: Phase 40 is in progress. Filesystem observation now reads retained files from disk, computes real SHA-256 digests, records file existence and size, and maps observations into the retained file verification model. Filesystem manifest execution now observes every promotion handoff item, supports retained-path-to-local-path overrides, and builds retained file manifests from real observations. Filesystem verification report execution now evaluates those manifests and exposes retained file blockers from real files. Verification artifact writing now retains a Markdown report and tab-separated observation manifest on disk. Retention ledger execution now creates ledger entries from filesystem-backed verification reports and written artifacts. Integrity seal execution now seals filesystem-backed ledgers with deterministic aggregate SHA-256 digests. Publication attachment execution now creates release dossier attachments from the filesystem-backed seal and requires approved redaction state for trace-bearing artifacts. Promotion execution now evaluates filesystem-backed attachments through reviewer approval, UTC evaluation, and explicit blockers. Command materialization now writes the ordered execution plan to a retained shell script. Interim status reporting now tracks nine completed capabilities and keeps final validation pending. Final validation remains in progress.
 
 ## Recommended First Deliverable
 

src/Sigtran.NET.Tests/Program.cs

@@ -313,6 +313,8 @@
 Run("SIGTRAN commercial evidence filesystem integrity seal matches ledger", SigtranCommercialEvidenceFileSystemIntegritySealMatchesLedger);
 Run("SIGTRAN commercial evidence filesystem publication attachments protect trace evidence", SigtranCommercialEvidenceFileSystemPublicationAttachmentsProtectTraceEvidence);
 Run("SIGTRAN commercial evidence filesystem promotion gate requires approval", SigtranCommercialEvidenceFileSystemPromotionGateRequiresApproval);
+Run("SIGTRAN commercial evidence filesystem command materializer writes execution script", SigtranCommercialEvidenceFileSystemCommandMaterializerWritesExecutionScript);
+Run("SIGTRAN commercial evidence filesystem execution status summarizes pending final validation", SigtranCommercialEvidenceFileSystemExecutionStatusSummarizesPendingFinalValidation);
 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);
@@ -5416,6 +5418,51 @@ static void SigtranCommercialEvidenceFileSystemPromotionGateRequiresApproval()
     }
 }
 
+static void SigtranCommercialEvidenceFileSystemCommandMaterializerWritesExecutionScript()
+{
+    string tempRoot = Path.Combine(Path.GetTempPath(), "sigtran-commercial-evidence-" + Guid.NewGuid().ToString("N"));
+    Directory.CreateDirectory(tempRoot);
+
+    try
+    {
+        SigtranCommercialEvidenceFileVerificationCommandPlan plan = SigtranCommercialEvidenceFileVerificationCommands.CreateDefault(
+            Path.Combine(tempRoot, "artifacts"));
+        string scriptPath = Path.Combine(tempRoot, "scripts", "commercial-evidence.sh");
+
+        SigtranCommercialEvidenceFileSystemCommandMaterialization materialization = SigtranCommercialEvidenceFileSystemCommandMaterializer.WriteScript(
+            plan,
+            scriptPath,
+            DateTimeOffset.UtcNow);
+
+        Assert(materialization.IsReady, materialization.Describe());
+        Assert(materialization.ScriptExists, "materialized command script should exist");
+        Assert(materialization.ScriptSizeBytes > 0, "materialized command script should be non-empty");
+        Assert(materialization.IncludesArtifactRoot, "materialized command script should include artifact root");
+        Assert(materialization.IncludesAllCommands, "materialized command script should include all commands");
+        Assert(materialization.IncludesPromotionGate, "materialized command script should include promotion gate");
+    }
+    finally
+    {
+        DeleteTempEvidenceRoot(tempRoot);
+    }
+}
+
+static void SigtranCommercialEvidenceFileSystemExecutionStatusSummarizesPendingFinalValidation()
+{
+    IReadOnlyList<string> capabilities = SigtranCommercialEvidenceFileSystemExecutionStatus.GetCompletedCapabilities();
+    IReadOnlyList<string> blockers = SigtranCommercialEvidenceFileSystemExecutionStatus.GetDefaultBlockers();
+
+    AssertEqual(9, SigtranCommercialEvidenceFileSystemExecutionStatus.CompletedUnitCount, "filesystem execution completed unit count");
+    AssertEqual(9, capabilities.Count, "filesystem execution capability count");
+    Assert(capabilities.Contains("command-materialization"), "filesystem execution status should include command materialization");
+    Assert(!capabilities.Contains("documentation"), "filesystem execution status should keep documentation pending before final validation");
+    Assert(SigtranCommercialEvidenceFileSystemExecutionStatus.ExecutionFoundationReady, SigtranCommercialEvidenceFileSystemExecutionStatus.Describe());
+    Assert(!SigtranCommercialEvidenceFileSystemExecutionStatus.RealApprovedCommercialRunReady, SigtranCommercialEvidenceFileSystemExecutionStatus.Describe());
+    Assert(!SigtranCommercialEvidenceFileSystemExecutionStatus.CommercialPublicationReady, SigtranCommercialEvidenceFileSystemExecutionStatus.Describe());
+    Assert(blockers.Contains("real-approved-commercial-run-required"), "filesystem execution status should require a real approved run");
+    Assert(blockers.Contains("status-final-validation-pending"), "filesystem execution status should keep final validation pending");
+}
+
 static SigtranCommercialEvidenceFileSystemPublicationAttachmentExecution CreateReadyCommercialEvidenceFileSystemPublicationAttachmentExecution(string tempRoot)
 {
     return SigtranCommercialEvidenceFileSystemPublicationAttachments.Create(