Preserve cancellation in aggregate smoke tests
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Consolidated audit catalog
|
||||
|
||||
Status: **27 distinct open findings: five P2 and 22 P3**, consolidated from 30
|
||||
Status: **26 distinct open findings: four P2 and 22 P3**, consolidated from 30
|
||||
numbered entries in seven audit documents. Reviewed audit state:
|
||||
`db732e3a1de55c844f77870e1c6db683c2685d5d`.
|
||||
|
||||
@@ -9,7 +9,7 @@ decisions. The linked original entries retain code locations, evidence,
|
||||
contract analysis, and detailed
|
||||
remediation options. Consolidation alone does not resolve a finding or select a
|
||||
proposed contract change. Explicit decisions recorded below supersede the
|
||||
original entries' alternatives; all findings remain open until remediated.
|
||||
original entries' alternatives; findings remain open until remediated.
|
||||
Original priorities are retained. Within those priorities, incorrect outcomes
|
||||
and request isolation lead; blocked validation,
|
||||
resource retention, and consumer contracts precede scaling and maintainability
|
||||
@@ -19,7 +19,7 @@ The [remediation analysis](remediation-analysis.md) records the completed design
|
||||
review and its rationale. All choices identified for discussion have been
|
||||
resolved; no further product or architectural decision is required before
|
||||
implementation planning. Accepted conclusions are recorded in this catalog;
|
||||
all 27 findings still require remediation and validation.
|
||||
the remaining findings still require remediation and validation.
|
||||
|
||||
Three pairs describe the same underlying issue: correctness C2/concurrency N2,
|
||||
correctness C4/concurrency N3, and complexity M6/responsibility R1. Other
|
||||
@@ -38,6 +38,12 @@ these boundaries.
|
||||
|
||||
## F01 — P2: Aggregate smoke testing can stop on cancellation and return success
|
||||
|
||||
**Complete.** The later cancellation checkpoint retains a cause when work is
|
||||
omitted, without duplicating a cause already recorded. Focused aggregate and
|
||||
cancellation tests pass in the aligned workspace; the new progress-delivery
|
||||
regression failed against the original behavior for both successful and failed
|
||||
provider calls, and also covers cancellation after the last completed check.
|
||||
|
||||
In ckprompt's `runSmokeAggregate`, cancellation triggered during progress
|
||||
delivery can stop the remaining smoke kinds without entering the operation
|
||||
cause. A partial aggregate can consequently return status 0; cancellation can
|
||||
|
||||
Reference in New Issue
Block a user