Add commercial evidence execution retry policy

Author: ammarheidari

README.md

@@ -72,7 +72,7 @@ The first production milestone is M3UA over a transport abstraction. SCCP, TCAP,
 | Supply-chain release execution | Phase 34 foundation-complete: final versioned SBOM, trusted timestamped package signing, provenance attestation, public API diff, artifact upload, ordered command-plan, release promotion gate, concrete workflow execution, status reporting, and final validation are available; retained release-run artifacts and commercial evidence are still required |
 | RC publish and commercial gate | Phase 35 complete: dry-run release rehearsal, gated NuGet prerelease publication, retained release notes, retained migration notes, final commercial readiness reporting, RC/stable decisioning, RC publication evidence manifest, release workflow channel wiring, status reporting, and final commercial gate report are available; stable publication remains blocked until commercial evidence is complete |
 | 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 in progress: evidence execution run identity, stage catalog, operator command plan, execution environment contract, artifact collection manifest, digest/redaction verification, and blocker classification are available; retry/resume and status reporting are still being implemented |
+| Commercial evidence execution orchestration | Phase 37 in progress: evidence execution run identity, stage catalog, operator command plan, execution environment contract, artifact collection manifest, digest/redaction verification, blocker classification, and retry/resume policy are available; status reporting is still being implemented |
 
 ## Requirements
 

docs/PHASE37_COMMERCIAL_EVIDENCE_EXECUTION_ORCHESTRATION.md

@@ -92,6 +92,16 @@ This plan keeps evidence review auditable and prevents sensitive telecom traces
 
 Each blocker declares whether it is retryable after correction. Unknown blockers are not retried automatically and require manual triage.
 
+## Unit 8 - Retry And Resume Policy
+
+`SigtranCommercialEvidenceExecutionRetryPolicies` maps blocker kinds to retry decisions:
+
+- Environment, command, external peer, artifact, digest, and redaction blockers can be retried within bounded attempt counts.
+- Native SCTP host blockers, protected approval blockers, unknown blockers, and failed preflight blockers require manual correction.
+- Retry decisions include the stage identifier where execution should resume.
+
+The policy prevents endless retries and keeps host capability, approval, and unknown failures under operator control.
+
 ## Validation
 
 Each unit in this phase is validated with:

docs/PHASE37_SUMMARY.md

@@ -11,7 +11,8 @@ Phase 37 prepares the SDK to execute real commercial evidence runs after readine
 - Artifact collection manifest that maps checklist artifacts to known stage roots and retained output paths.
 - Digest and redaction verification plan for every retained execution artifact.
 - Execution blocker classifier for readiness, environment, command, native SCTP, external peer, artifact, digest, redaction, and approval failures.
+- Retry and resume policy with bounded retries and manual-correction gates for non-retryable failures.
 
 ## Readiness Position
 
-The phase is in progress. Execution orchestration still requires retry/resume policy, status reporting, and final validation.
+The phase is in progress. Execution orchestration still requires status reporting and final validation.

docs/PHASE_INDEX.md

@@ -41,7 +41,7 @@ This index is the complete phase map for Sigtran.NET. It links each phase to the
 | 34 | Supply-chain release execution | [Phase 34 Supply Chain Release Execution](PHASE34_SUPPLY_CHAIN_RELEASE_EXECUTION.md), [Phase 34 Summary](PHASE34_SUMMARY.md) | Foundation complete; retained release run pending |
 | 35 | RC publish and commercial gate | [Phase 35 RC Publish And Commercial Gate](PHASE35_RC_PUBLISH_COMMERCIAL_GATE.md), [Phase 35 Summary](PHASE35_SUMMARY.md), [Phase 35 Commercial Gate Report](PHASE35_COMMERCIAL_GATE_REPORT.md) | RC gate foundation complete; stable publication blocked |
 | 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) | In progress; blocker classifier complete |
+| 37 | Commercial evidence execution orchestration | [Phase 37 Commercial Evidence Execution Orchestration](PHASE37_COMMERCIAL_EVIDENCE_EXECUTION_ORCHESTRATION.md), [Phase 37 Summary](PHASE37_SUMMARY.md) | In progress; retry/resume policy complete |
 
 ## Current Commercial Gate
 

docs/SDK_ROADMAP.md

@@ -331,7 +331,7 @@ Status: Phase 36 is foundation-complete. The release target lock binds an RC ver
 - Define execution stages, operator commands, environment contracts, artifact collection, digest and redaction verification, blocker handling, retry/resume behavior, and execution status.
 - Keep the phase separate from real passing evidence: orchestration can prepare a run, but publication remains blocked until retained artifacts prove execution success.
 
-Status: Phase 37 is in progress. Evidence execution run identity now binds a locked release target to a stable run id, operator identity, UTC start time, and run-scoped artifact root. The stage catalog now covers readiness preflight, native SCTP lab, external peer interoperability, protocol validation, performance benchmark, supply-chain evidence, release workflow dry-run, and dossier assembly with run-scoped artifact roots. The operator command plan now maps every stage to an ordered run-id-aware command and requires protected approval for supply-chain, workflow, and dossier assembly execution. The environment contract now binds run identity, lab inputs, and protected secrets while preventing fixed secret values from being stored. Artifact collection now maps all checklist artifacts to known stage roots and retained output paths. Digest and redaction verification now requires digest coverage for every artifact and redaction review for trace-bearing evidence. Blocker classification now categorizes readiness, environment, command, native SCTP, external peer, artifact, digest, redaction, and approval failures with retryability guidance. Retry/resume, status reporting, and final validation remain in progress.
+Status: Phase 37 is in progress. Evidence execution run identity now binds a locked release target to a stable run id, operator identity, UTC start time, and run-scoped artifact root. The stage catalog now covers readiness preflight, native SCTP lab, external peer interoperability, protocol validation, performance benchmark, supply-chain evidence, release workflow dry-run, and dossier assembly with run-scoped artifact roots. The operator command plan now maps every stage to an ordered run-id-aware command and requires protected approval for supply-chain, workflow, and dossier assembly execution. The environment contract now binds run identity, lab inputs, and protected secrets while preventing fixed secret values from being stored. Artifact collection now maps all checklist artifacts to known stage roots and retained output paths. Digest and redaction verification now requires digest coverage for every artifact and redaction review for trace-bearing evidence. Blocker classification now categorizes readiness, environment, command, native SCTP, external peer, artifact, digest, redaction, and approval failures with retryability guidance. Retry/resume now applies bounded retries and manual-correction gates for non-retryable failures. Status reporting and final validation remain in progress.
 
 ## Recommended First Deliverable
 

src/Sigtran.NET.Tests/Program.cs

@@ -285,6 +285,7 @@
 Run("SIGTRAN commercial evidence execution artifact manifest covers retained outputs", SigtranCommercialEvidenceExecutionArtifactManifestCoversRetainedOutputs);
 Run("SIGTRAN commercial evidence execution verification requires digests and redaction", SigtranCommercialEvidenceExecutionVerificationRequiresDigestsAndRedaction);
 Run("SIGTRAN commercial evidence execution blocker classifier categorizes failures", SigtranCommercialEvidenceExecutionBlockerClassifierCategorizesFailures);
+Run("SIGTRAN commercial evidence execution retry policy gates resume decisions", SigtranCommercialEvidenceExecutionRetryPolicyGatesResumeDecisions);
 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);
@@ -4733,6 +4734,35 @@ static void SigtranCommercialEvidenceExecutionBlockerClassifierCategorizesFailur
     Assert(!unknown.Retryable, "unknown blocker should not be automatically retried");
 }
 
+static void SigtranCommercialEvidenceExecutionRetryPolicyGatesResumeDecisions()
+{
+    SigtranCommercialEvidenceExecutionRun run = SigtranCommercialEvidenceExecutionRuns.CreateReleaseCandidateRun(
+        "1.0.0-rc.1",
+        "abcdef123456",
+        "run-20260622-001",
+        "release-automation",
+        DateTimeOffset.UtcNow);
+    SigtranCommercialEvidenceExecutionStageCatalog catalog = SigtranCommercialEvidenceExecutionStages.CreateDefault(run);
+    SigtranCommercialEvidenceExecutionRetryPolicy policy = SigtranCommercialEvidenceExecutionRetryPolicies.CreateDefault(catalog);
+    SigtranCommercialEvidenceExecutionBlockerClassifier classifier = SigtranCommercialEvidenceExecutionBlockers.CreateDefault();
+    SigtranCommercialEvidenceExecutionRetryDecision peerRetry = policy.Decide(classifier.Classify("external-peer-unavailable"), attemptCount: 1);
+    SigtranCommercialEvidenceExecutionRetryDecision peerExhausted = policy.Decide(classifier.Classify("external-peer-unavailable"), attemptCount: 3);
+    SigtranCommercialEvidenceExecutionRetryDecision nativeSctp = policy.Decide(classifier.Classify("native-sctp-unavailable"), attemptCount: 0);
+    SigtranCommercialEvidenceExecutionRetryDecision unknown = policy.Decide(classifier.Classify("operator-note-required"), attemptCount: 0);
+
+    Assert(policy.IsReady, policy.Describe());
+    Assert(policy.CoversKnownBlockers, "retry policy should cover known blocker kinds");
+    Assert(policy.UsesKnownResumeStages, "retry policy should resume from known stages");
+    Assert(policy.ProtectsNonRetryableFailures, "retry policy should protect non-retryable failures");
+    Assert(peerRetry.CanRetry, "external peer blocker should be retryable before exhaustion");
+    Assert(peerRetry.ResumeStageId == "external-peer-interop", "external peer retry should resume from peer stage");
+    Assert(!peerExhausted.CanRetry, "external peer retry should stop after max attempts");
+    Assert(peerExhausted.RequiresManualCorrection, "exhausted retry should require manual correction");
+    Assert(!nativeSctp.CanRetry, "native SCTP host blocker should not retry automatically");
+    Assert(nativeSctp.RequiresManualCorrection, "native SCTP blocker should require host correction");
+    Assert(!unknown.CanRetry, "unknown blockers should not retry automatically");
+}
+
 static void SigtranStatusCapabilitiesUseDomainDocumentationLabels()
 {
     IReadOnlyList<string>[] statusCapabilities =