Repository navigation
Carry execution and recovery requirements from SDL into plans #1361
Description
Activity
🛠️ Picked up by /implement - driver codex, branch
1361-execution-recovery-requirements, 2026-10-04T03:59:51.981Z.gc workflow phase recorded:
plan(issue #1361). Posted by the MCP server to enforce ordering between workflow steps (issue #794 MVP-2). Do not edit or delete — used by downstream tools to gate phase prerequisites.Implement #1361 against ADR-113 and the issue preflight, preserving the existing workflow, participant, trial and backend-operation owners.
- AC1 (Path A): introduce a closed versioned execution-policy scope table with complete policies, canonical namespace/JSON-pointer scopes and explicit policy identity. Reuse the existing lexical specificity and composition pointer helpers. Carry authored defaults and imported definition-site scope through every SDL phase; resolve effective policies once in compilation and retain them through native plans, public projection, HTTP reconstruction and inspection.
- AC2 (Path A): represent never-repeat, bounded operation retry, verified continuation, termination and separately requested fresh trial. Reuse ExecutionRetryPolicyModel's max_attempts/after_effect_policy semantics rather than making another retry vocabulary. Preserve existing explicit workflow and participant choices; reject incompatible independently selected policies rather than multiply or clamp retry bounds. Missing effect-repeat permission remains conservative. Bind required evidence, failure classes, budgets, exhaustion and validity choices explicitly without inferring them from application labels.
- AC3 (Path A): preserve operation/invocation/attempt versus trial/run/episode identity. Add no participant or experiment requirement for ordinary execution. Represent fresh-trial authority as an exact reference to the existing experiment/trial owner, and reject admission without that authority; it never allocates a trial. Reject continuation without a compatible published capability rather than equating it with durability.
- AC4 (Path A): add focused tests covering alternatives/defaults, nested and sibling scope resolution, imported lexical binding, invalid combinations, workflow retry conflicts, plan serialization/reconstruction/digests and backend incapability/refusal. Bind effective requirements to Publish backend operation and supervision contracts #1360 native plan references and exact contextual willingness, using existing canonical digests, admission validators and safe diagnostics.
- Publication/documentation (Path D alongside executable tests): publish the affected SDL/plan/manifest schemas with matching schema_bundle output and per-contract v2 publication ledger hashes; update canonical SDL and backend author migration guidance. Release Please retains version and changelog ownership.
Security: reuse safe SDL ingress, closed strict bounded models, canonical references, protected-value handling, native plan authorization and result/disclosure gates. Policy references grant no authority and carry no secrets. Maintainability: reuse scope, compilation, projection and #1360 admission helpers. Extensibility: versioned complete policy and capability contracts permit future supported continuation without backend/application branches. Whole-repo boundaries include parser catalogs, phase models, composition, compiler/planner, manifest conversion, public DTO reconstruction, schema publication, policy tooling and CI.
Run targeted changed-file repository policy before/after work, explicit relevant pytest modules/cases, schema parity/publication checks and targeted lint locally. Set RAES_REQUIREMENT_UID=SEM-203 for relevant local governance checks on this issue branch; the issue itself has no attached requirement and adds no new policy/workflow enforcement gate. Full test/integration/fuzz/completion suites remain CI/CD only. Preserve pre-publish hooks, pre-push review, hosted CI/Sonar and readiness gates.
gc_codex_review — sanitized deferred publication for issue #1361, cycle 1 of 1
Reviewed revision:26f2f816b601a871fba857651a8d99d2478114eedc41a803b019dcf5a6deb2beArchitectural read
The typed policy and native-plan/admission seams fit the existing architecture. Required repairs concern preparation conversion and composed declaration identity. The security review found no concrete exploitable regression across the seven reviewed slices.
Verdict:
ship-with-fixesFindings
core-F1 — Preserve execution policies through preparation conversion
- Classification:
one-off - Decision:
fix - Location:
BackendPreparationResponseModel.to_runtime - Rationale: Forward both native policy fields during preparation reconstruction and verify executable preparation admission with a policy-bearing operation.
core-F2 — Rewrite binding identities inside imported policy scopes
- Classification:
one-off - Decision:
fix - Location:
raes/composition/_execution_policy.py:22 - Rationale: Rewrite nested feature, condition and inject binding tokens through their owning symbol maps; add import regressions covering canonical pointer identity.
core-F3 — Preserve nested policy namespaces across private import renaming
- Classification:
one-off - Decision:
fix - Location:
raes/composition/_execution_policy.py:21 - Rationale: Bind policy namespaces to actual exported/private declaration renames and verify nested imports with mixed visibility.
- Classification:
3 remaining items
Pre-PR base synchronization
- Source:
refs/remotes/origin/devat41c3f469ef21e0c570d8321c47de446b06e6b324 - Outcome:
already_current - Published feature head:
af78001f9bb02137c9d8ad8ad3761a37f44be3aa - Synchronized tree:
51820351a6202bcbd0e525b74491c86649d61cff
- Source:
Pre-PR base synchronization
- Source:
refs/remotes/origin/devat41c3f469ef21e0c570d8321c47de446b06e6b324 - Outcome:
already_current - Published feature head:
3cc94506adbed89a5361850fed01cb5bc1b07bcb - Synchronized tree:
ca6f927c0c3671f18d5cb19d5cf68137532a6ed0
- Source:
Pre-PR base synchronization
- Source:
refs/remotes/origin/devat41c3f469ef21e0c570d8321c47de446b06e6b324 - Outcome:
already_current - Published feature head:
8fe40ed8a21747f724a33b6058c74d04b4a89323 - Synchronized tree:
bc5d9d601832187cd495511c1f763388f72f5606
- Source:
Pre-PR base synchronization
- Source:
refs/remotes/origin/devat41c3f469ef21e0c570d8321c47de446b06e6b324 - Outcome:
already_current - Published feature head:
5bcaabfce648fd3cdee48f291ea7c56d99d0093e - Synchronized tree:
84448447587b9030f371f11c1df283f912277349
- Source:
Execution obligation 1361-SONAR-WATCHER-ISSUE-FETCH — Opened
Category: workflow
Observed state: Ground Control Sonar watcher read quality_gate ERROR but failed issue search page 1 with HTTP 400.
Impact: Required canonical Sonar findings and hotspot verification is incomplete.
Current obligation: Repair the active Ground Control Sonar watcher organization scope and verify the current PR head through the canonical monitor.Evidence
- gc_codex_job job-muuqvant-m: sonar_watch_issues_fetch_failed, HTTP 400
- https://sonarcloud.io/dashboard?id=Brad-Edwards_aces&pullRequest=1413
- Public issue API returned 44 open findings; local Ground Control sonar-api.js and organization-scope regression explain organization-scoped-token searches.
Pre-PR base synchronization
- Source:
refs/remotes/origin/devat41c3f469ef21e0c570d8321c47de446b06e6b324 - Outcome:
already_current - Published feature head:
78fcc6cf0f86a7e1b471065214f5b21bbd25cfb2 - Synchronized tree:
a221773623cffcbb3f76969825d3e87c5e3b12d8
- Source:
Pre-PR base synchronization
- Source:
refs/remotes/origin/devat41c3f469ef21e0c570d8321c47de446b06e6b324 - Outcome:
already_current - Published feature head:
9e1d6f83b2bb52bd96d72ff9404d23e12a8d58ae - Synchronized tree:
9fb97d951d013beabfd055c24a93b043eb6090ee
- Source:
Execution obligation 1361-SONAR-WATCHER-ISSUE-FETCH — Resolved
Category: workflow
Observed state: The canonical current-head Sonar watcher successfully fetched issues and hotspots without HTTP 400.
Impact: The required Sonar verification is evaluable; three real type-hint findings remain under active repair.
Current obligation: Repair the active Ground Control Sonar watcher organization scope and verify the current PR head through the canonical monitor.Evidence
- gc_codex_job job-muus73b0-7 returned ok=true, quality_gate=ERROR, open_count=3, hotspots open_count=0.
- Current monitored head: 9e1d6f8
Disposition: fix
Corrective action: Resumed verification with the active Ground Control server and successfully re-ran the canonical monitor against the published PR revision.Verification
- Canonical issue and hotspot fetch completed for PR feat: carry authored execution and recovery requirements #1413; the three reported findings match the current analysis.
Pre-PR base synchronization
- Source:
refs/remotes/origin/devat41c3f469ef21e0c570d8321c47de446b06e6b324 - Outcome:
already_current - Published feature head:
e87b08a344642b7005baca31387a2d819a88328a - Synchronized tree:
01937adac228568fdc286ebc8225b753fc5d2c89
- Source:
Pre-PR base synchronization
- Source:
refs/remotes/origin/devat546d0642bbab1a4460d702d7332aab56603fe0b3 - Outcome:
merged_conflicts_resolved - Published feature head:
6062d6b50abe01e9b24d3a3ab598a08840d8b2c3 - Synchronized tree:
5fa669d428e1981972fb1cd7384243e155ef7019
- Source:
Ready for review — issue #1361
PR: #1413
Plan: #1361 (comment)Outcome
Authored execution and recovery requirements now reach compiled plans, inspection and backend admission with their defaults and scope preserved. Unsupported or refused choices are rejected explicitly, and operation retries remain distinct from creating a fresh trial.
Files changed
Added:
docs/decisions/issue-1361-execution-recovery-requirements-preflight.mddocs/explain/reference/execution-recovery-migration.mddocs/research/execution-recovery-pre-sync-evidence/README.mddocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/analysis-v68.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/analysis-v69.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/analysis-v70.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/bundles/retest-v68.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/bundles/retest-v69.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/bundles/retest-v70.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/execution-snapshot-v68.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/execution-snapshot-v69.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/execution-snapshot-v70.jsondocs/research/execution-recovery-pre-sync-evidence/records.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/analysis-v67.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/analysis-v68.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/analysis-v69.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/bundles/raes-standardized-specification-coverage-issue-1361-v67.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/bundles/raes-standardized-specification-coverage-issue-1361-v68.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/bundles/raes-standardized-specification-coverage-issue-1361-v69.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/execution-snapshot-v67.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/execution-snapshot-v68.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/execution-snapshot-v69.jsondocs/research/formal-semantic-validation/analysis-v69.jsondocs/research/formal-semantic-validation/bundles/retest-v69.jsondocs/research/formal-semantic-validation/execution-snapshot-v69.jsondocs/research/specification-coverage/analysis-v68.jsondocs/research/specification-coverage/bundles/raes-standardized-specification-coverage-issue-1361-v68.jsondocs/research/specification-coverage/execution-snapshot-v68.jsonimplementations/python/packages/raes/composition/_execution_policy.pyimplementations/python/packages/raes/execution_policy_scope.pyimplementations/python/packages/raes/validator/_execution_policy.pyimplementations/python/packages/raes_contracts/contracts/_execution_policy_exports.pyimplementations/python/packages/raes_contracts/contracts/plan_operation.pyimplementations/python/packages/raes_contracts/execution_policy.pyimplementations/python/packages/raes_contracts/execution_policy_schema.pyimplementations/python/packages/raes_contracts/execution_retry.pyimplementations/python/packages/raes_processor/compiler/execution_policy.pyimplementations/python/packages/raes_processor/planner/execution_policy.pyimplementations/python/tests/test_issue_1361_execution_policy.pyimplementations/python/tests/test_issue_1361_policy_admission.pyimplementations/python/tests/test_issue_1361_policy_composition.pyspecs/sdl/execution-recovery.md
Modified:
contracts/README.mdcontracts/provenance/sdl-lineage-ledger-v2.jsoncontracts/schema-publication/entries/backend-manifest-v2.jsoncontracts/schema-publication/entries/backend-operation-capabilities-v1.jsoncontracts/schema-publication/entries/backend-realization-preparation-v1.jsoncontracts/schema-publication/entries/evaluation-plan-v1.jsoncontracts/schema-publication/entries/instantiated-scenario-snapshot-v1.jsoncontracts/schema-publication/entries/instantiated-scenario-v1.jsoncontracts/schema-publication/entries/materialized-scenario-v1.jsoncontracts/schema-publication/entries/orchestration-plan-v1.jsoncontracts/schema-publication/entries/provisioning-plan-v1.jsoncontracts/schema-publication/entries/scenario-satisfiability-evidence-v1.jsoncontracts/schema-publication/entries/sdl-authoring-input-v1.jsoncontracts/schemas/backend-manifest/backend-manifest-v2.jsoncontracts/schemas/control-plane/backend-operation-capabilities-v1.jsoncontracts/schemas/plans/backend-realization-preparation-v1.jsoncontracts/schemas/plans/evaluation-plan-v1.jsoncontracts/schemas/plans/orchestration-plan-v1.jsoncontracts/schemas/plans/provisioning-plan-v1.jsoncontracts/schemas/satisfiability/scenario-satisfiability-evidence-v1.jsoncontracts/schemas/sdl/instantiated-scenario-snapshot-v1.jsoncontracts/schemas/sdl/instantiated-scenario-v1.jsoncontracts/schemas/sdl/materialized-scenario-v1.jsoncontracts/schemas/sdl/sdl-authoring-input-v1.jsondocs/explain/reference/backend-operation-supervision.mddocs/research/formal-semantic-validation/index.mddocs/research/specification-coverage/index.mdimplementations/python/packages/raes/composition/_expand.pyimplementations/python/packages/raes/scenario.pyimplementations/python/packages/raes/validator/__init__.pyimplementations/python/packages/raes/validator/_core.pyimplementations/python/packages/raes_backend_protocols/backend_manifest.pyimplementations/python/packages/raes_backend_protocols/manifest.pyimplementations/python/packages/raes_contracts/_planning_validation.pyimplementations/python/packages/raes_contracts/contracts/__init__.pyimplementations/python/packages/raes_contracts/contracts/_backend_operation_exports.pyimplementations/python/packages/raes_contracts/contracts/_exports.pyimplementations/python/packages/raes_contracts/contracts/backend_operation.pyimplementations/python/packages/raes_contracts/contracts/backend_operation_validation.pyimplementations/python/packages/raes_contracts/contracts/backend_preparation.pyimplementations/python/packages/raes_contracts/contracts/participant_manifests.pyimplementations/python/packages/raes_contracts/contracts/realization_plans.pyimplementations/python/packages/raes_contracts/contracts/trial_cleanup.pyimplementations/python/packages/raes_contracts/plan_projection.pyimplementations/python/packages/raes_contracts/planning.pyimplementations/python/packages/raes_processor/compiler/pipeline.pyimplementations/python/packages/raes_processor/models/runtime_model.pyimplementations/python/packages/raes_processor/planner/core.pyimplementations/python/packages/raes_runtime/control_plane_api_models.pyimplementations/python/tests/test_formal_semantic_validation.pyimplementations/python/tests/test_issue_989_versioned_evidence.pyimplementations/python/tests/test_sdl_catalog_parity.pyimplementations/python/tests/test_sdl_lineage.pyimplementations/python/tests/test_specification_coverage.pyspecs/sdl/README.mdspecs/sdl/references.mdspecs/sdl/sections.mdtools/check_specification_coverage.pytools/formal_semantic_validation/_loading.pytools/formal_semantic_validation/_release_revisions.pytools/formal_semantic_validation/_releases.pytools/formal_semantic_validation/_retest.pytools/sdl_catalog_parity/_expectations_3.py
Reviews
- codex: One review cycle at the configured cap; all three findings fixed with regression tests. User authorized publication. Current-head CI passes; Sonar has zero open issues or hotspots after two repair cycles.
Traceability reconciliation
Proposed in this PR — verified against the merged tree in Phase E.
- IMPLEMENTS / TESTS / DOCUMENTS added: 0
- Links updated: 0
- Stale links removed: 0
Status
- CI: ✅ green
- SonarCloud: ✅ passed
- PR ready for user review and merge. Phase E validates the merged requirement state, posts the final report, and closes the issue automatically once this PR merges.
Final report — issue #1361 complete
PR: #1413
Plan: #1361 (comment)Outcome
Authored execution and recovery requirements now reach compiled plans, inspection and backend admission with their defaults and scope preserved. Unsupported or refused choices are rejected explicitly, and operation retries remain distinct from creating a fresh trial.
Files changed
Added:
docs/decisions/issue-1361-execution-recovery-requirements-preflight.mddocs/explain/reference/execution-recovery-migration.mddocs/research/execution-recovery-pre-sync-evidence/README.mddocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/analysis-v68.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/analysis-v69.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/analysis-v70.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/bundles/retest-v68.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/bundles/retest-v69.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/bundles/retest-v70.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/execution-snapshot-v68.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/execution-snapshot-v69.jsondocs/research/execution-recovery-pre-sync-evidence/formal-semantic-validation/execution-snapshot-v70.jsondocs/research/execution-recovery-pre-sync-evidence/records.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/analysis-v67.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/analysis-v68.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/analysis-v69.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/bundles/raes-standardized-specification-coverage-issue-1361-v67.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/bundles/raes-standardized-specification-coverage-issue-1361-v68.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/bundles/raes-standardized-specification-coverage-issue-1361-v69.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/execution-snapshot-v67.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/execution-snapshot-v68.jsondocs/research/execution-recovery-pre-sync-evidence/specification-coverage/execution-snapshot-v69.jsondocs/research/formal-semantic-validation/analysis-v69.jsondocs/research/formal-semantic-validation/bundles/retest-v69.jsondocs/research/formal-semantic-validation/execution-snapshot-v69.jsondocs/research/specification-coverage/analysis-v68.jsondocs/research/specification-coverage/bundles/raes-standardized-specification-coverage-issue-1361-v68.jsondocs/research/specification-coverage/execution-snapshot-v68.jsonimplementations/python/packages/raes/composition/_execution_policy.pyimplementations/python/packages/raes/execution_policy_scope.pyimplementations/python/packages/raes/validator/_execution_policy.pyimplementations/python/packages/raes_contracts/contracts/_execution_policy_exports.pyimplementations/python/packages/raes_contracts/contracts/plan_operation.pyimplementations/python/packages/raes_contracts/execution_policy.pyimplementations/python/packages/raes_contracts/execution_policy_schema.pyimplementations/python/packages/raes_contracts/execution_retry.pyimplementations/python/packages/raes_processor/compiler/execution_policy.pyimplementations/python/packages/raes_processor/planner/execution_policy.pyimplementations/python/tests/test_issue_1361_execution_policy.pyimplementations/python/tests/test_issue_1361_policy_admission.pyimplementations/python/tests/test_issue_1361_policy_composition.pyspecs/sdl/execution-recovery.md
Modified:
contracts/README.mdcontracts/provenance/sdl-lineage-ledger-v2.jsoncontracts/schema-publication/entries/backend-manifest-v2.jsoncontracts/schema-publication/entries/backend-operation-capabilities-v1.jsoncontracts/schema-publication/entries/backend-realization-preparation-v1.jsoncontracts/schema-publication/entries/evaluation-plan-v1.jsoncontracts/schema-publication/entries/instantiated-scenario-snapshot-v1.jsoncontracts/schema-publication/entries/instantiated-scenario-v1.jsoncontracts/schema-publication/entries/materialized-scenario-v1.jsoncontracts/schema-publication/entries/orchestration-plan-v1.jsoncontracts/schema-publication/entries/provisioning-plan-v1.jsoncontracts/schema-publication/entries/scenario-satisfiability-evidence-v1.jsoncontracts/schema-publication/entries/sdl-authoring-input-v1.jsoncontracts/schemas/backend-manifest/backend-manifest-v2.jsoncontracts/schemas/control-plane/backend-operation-capabilities-v1.jsoncontracts/schemas/plans/backend-realization-preparation-v1.jsoncontracts/schemas/plans/evaluation-plan-v1.jsoncontracts/schemas/plans/orchestration-plan-v1.jsoncontracts/schemas/plans/provisioning-plan-v1.jsoncontracts/schemas/satisfiability/scenario-satisfiability-evidence-v1.jsoncontracts/schemas/sdl/instantiated-scenario-snapshot-v1.jsoncontracts/schemas/sdl/instantiated-scenario-v1.jsoncontracts/schemas/sdl/materialized-scenario-v1.jsoncontracts/schemas/sdl/sdl-authoring-input-v1.jsondocs/explain/reference/backend-operation-supervision.mddocs/research/formal-semantic-validation/index.mddocs/research/specification-coverage/index.mdimplementations/python/packages/raes/composition/_expand.pyimplementations/python/packages/raes/scenario.pyimplementations/python/packages/raes/validator/__init__.pyimplementations/python/packages/raes/validator/_core.pyimplementations/python/packages/raes_backend_protocols/backend_manifest.pyimplementations/python/packages/raes_backend_protocols/manifest.pyimplementations/python/packages/raes_contracts/_planning_validation.pyimplementations/python/packages/raes_contracts/contracts/__init__.pyimplementations/python/packages/raes_contracts/contracts/_backend_operation_exports.pyimplementations/python/packages/raes_contracts/contracts/_exports.pyimplementations/python/packages/raes_contracts/contracts/backend_operation.pyimplementations/python/packages/raes_contracts/contracts/backend_operation_validation.pyimplementations/python/packages/raes_contracts/contracts/backend_preparation.pyimplementations/python/packages/raes_contracts/contracts/participant_manifests.pyimplementations/python/packages/raes_contracts/contracts/realization_plans.pyimplementations/python/packages/raes_contracts/contracts/trial_cleanup.pyimplementations/python/packages/raes_contracts/plan_projection.pyimplementations/python/packages/raes_contracts/planning.pyimplementations/python/packages/raes_processor/compiler/pipeline.pyimplementations/python/packages/raes_processor/models/runtime_model.pyimplementations/python/packages/raes_processor/planner/core.pyimplementations/python/packages/raes_runtime/control_plane_api_models.pyimplementations/python/tests/test_formal_semantic_validation.pyimplementations/python/tests/test_issue_989_versioned_evidence.pyimplementations/python/tests/test_sdl_catalog_parity.pyimplementations/python/tests/test_sdl_lineage.pyimplementations/python/tests/test_specification_coverage.pyspecs/sdl/README.mdspecs/sdl/references.mdspecs/sdl/sections.mdtools/check_specification_coverage.pytools/formal_semantic_validation/_loading.pytools/formal_semantic_validation/_release_revisions.pytools/formal_semantic_validation/_releases.pytools/formal_semantic_validation/_retest.pytools/sdl_catalog_parity/_expectations_3.py
Reviews
- codex: One review cycle at the configured cap; all three findings fixed with regression tests. User authorized publication. Current-head CI passes; Sonar has zero open issues or hotspots after two repair cycles.
Traceability reconciliation
- IMPLEMENTS / TESTS / DOCUMENTS added: 0
- Links updated: 0
- Stale links removed: 0
Issue #1361 has no attached requirement UIDs. SDL lineage, schema publication ledgers, migration guidance and source-bound evidence releases are updated in the delivery PR. The delivery merges dev at 546d064. Colliding feature capture revisions are archived byte-for-byte with exact digest and source-revision records; incoming published releases are preserved and combined-source captures are current.
Status
- CI: ✅ green
- SonarCloud: ✅ passed
- PR ready for user review and merge.
The accepted failure and recovery choices must reach backend admission as authored requirements, rather than being inferred from durability or application type.
Acceptance criteria
Prerequisites: #1360.
References: Agreed failure and author-choice boundaries.