{
 "date":"2026-10-28",
 "requirement":"补齐订单模型 P2 请求取消、provider 与提交故障；验证事务回滚和资源释放；七语言示例、数据库验证、文档和回执同步；保留历史证据和待发布标记；仅使用本地证据。",
 "model":{"revision":"1.2.0","mode":"reuse exact stock-model bytes and source-bound local zero-error evaluation, 14 generated targets and 49 Assist scopes per language","freshEvaluation":false,"freshGeneration":false,"onlineModelTransmission":false,"manualGeneratedSourceChanges":false,"generatedSourceApiDiscovery":false},
 "result":{"cells":"7/7","sqlite":"7/7","independentNativeRuns":77,"runsPerRuntime":11,"databaseCheckpointsPerRuntime":45,"databaseCheckpoints":315,"lockProbesPerRuntime":21,"lockProbes":147,"controlledReaderProcesses":21},
 "cases":["One pre-admission native cancellation with no provider SELECT/DML after the request begins.","One successful transaction control, followed by same-provider idempotent replay.","Three independent cancellations after actual tenant, Order and inventory UPDATEs and before receipt INSERT.","Three independent provider statement failures from a test-only receipt INSERT trigger, after earlier business updates.","Three independent real COMMIT failures while another process holds a SQLite SHARED reader lock in DELETE journal mode, after all business writes and receipt INSERT."],
 "cancellation":{"java":"Native request-thread interruption converted to CancellationException; interrupted status cleared only after transaction cleanup before recovery.","typescript":"Native AbortController/AbortSignal at an awaited transport checkpoint.","python":"Actual asyncio child-task cancellation; CancelledError propagates through graph rollback and the child task is awaited.","rust":"Tokio select drops the in-progress request future; SQLite transaction guard Drop rolls back and releases its connection lease.","go":"Native context.WithCancel for the transaction; context.Canceled returns through graph rollback.","dotnet":"CancellationTokenSource cancels an awaited transport checkpoint; OperationCanceledException is preserved through provider cleanup.","swift":"A child Task receives native cancellation at an awaited mutation checkpoint, then throws CancellationError; parent awaits its completion before recovery."},
 "resourceEvidence":["The parent observes the native PID and an atomically published in-transaction ready file. It reads every domain row while the transaction remains open and requires an independent BEGIN IMMEDIATE probe to report SQLITE_BUSY.","After the failure returns but before the native process exits or recovery begins, a read-only oracle requires the exact original rows, versions, timestamps and receipt absence. The parent releases its controlled reader and requires another independent BEGIN IMMEDIATE to succeed.","The original native process then uses the same provider and retained UserContext state to freshly reload and commit the same request once. The success control replays the existing receipt. Native pointer/resource-reference comparisons are retained; Swift retains its value-type UserContext and the same actor executor.","Only test setup installs/removes the trigger, changes journal mode or probes write-lock admission; it never changes domain data. The oracle uses SQLite mode=ro.","Application-owned async tasks are awaited or dropped before publishing failure/recovery. No unmeasured pool-size, goroutine count or physical-connection closure claim is made."],
 "publishedFailure":{"runtime":"java","version":"1.555-RELEASE","evidence":"discovery/java-published-failure/manifest.json","observed":"A COMMIT SQLException bypasses the RuntimeException/Error-only rollback catch. Restoring auto-commit then fails under the reader lock. The independent oracle stays locked and the same pool incorrectly replays a dirty receipt after forced test teardown. After process shutdown an independent snapshot has no receipts. This proves leaked transaction/pool state; it does not prove a durable erroneous commit."},
 "runtimeRepair":{"repository":"teaql-java","file":"teaql-provider-jdbc/src/main/java/io/teaql/provider/jdbc/JdbcSqlExecutor.java","change":"Catch SQLException from COMMIT alongside business/cancellation failures. Attempt rollback and retain cleanup failures as suppressed exceptions. Always remove transaction ThreadLocal. Do not restore auto-commit on an operation-owned connection that is immediately closed: the transition can implicitly commit unresolved writes.","regressions":"3/3: real SQLite commit BUSY with lock release and retry; COMMIT plus rollback failure retains original cause and never enables auto-commit; cancellation plus rollback failure retains cancellation identity.","packaging":"Compile the single JDBC runtime source and its compiler-generated nested classes against retained published artifacts with javac --release 17. Overlay those runtime classes into a separately fingerprinted workspace JAR and an isolated APFS-cloned Maven repository; generated POMs remain unchanged. Verify every patched class hash in the actual executable JAR. Cached JUnit/Hamcrest and SQLite artifacts are used offline.","qualification":"Java lifecycle WORKSPACE PASS — RELEASE PENDING; no runtime publication or deployment claimed."},
 "otherCleanupDetails":"Python closes its transaction connection when COMMIT fails, so a secondary rollback attempt can report that the connection is already closed. Go can report that a failed-commit transaction is already finished during rollback. Both retain the original failure and must still pass the independent lock-release, unchanged-storage and same-provider recovery checks.",
 "qualifications":{"newLifecycleWorkspacePendingRelease":["java","rust","typescript","python","go","dotnet"],"lifecyclePublishedRuntime":["swift"],"historicalJava":"School, original Order, isolation and stock retain their narrower published Java passes.","otherHistoricalMarkers":"All five existing workspace runtime markers and generator-deployment qualifications remain unchanged."},
 "preserved":"School 238/238, original Order 56/56, P1 77/77, P1 complete 91/91, pages 105/105, insights 119/119, isolation 7/7 and stock 7/7, with all bound inputs unchanged.",
 "limits":["Cooperative native cancellation at a controlled awaited checkpoint; not arbitrary in-flight SQL interruption or HTTP/client-disconnect wiring.","SQLite rollback-journal COMMIT BUSY is the verified commit fault. It does not certify WAL-specific, distributed, network, power-loss or ambiguous post-commit outcomes.","Three bounded repetitions per fault mode. Sustained stress, cancellation during an active cursor and other database providers need separate evidence.","No external audit/event delivery or memory/connection-pool leak instrumentation is certified. Observed resources are transaction locks, same-provider reuse and application task lifetime.","The retained stock fixture remains single-SKU and uses a tenant version gate. Identity allocation counters may consume IDs after rollback and are outside domain snapshots."],
 "mechanicalReview":"Exact generation/model reuse, source hashes, runtime resolution, native SQL and error classes, independently held reader locks, full SQLite snapshots, writer probes, same-provider recovery and immutable historical receipt-chain checks.",
 "humanReviewFocus":"Production request cancellation wiring, chosen timeout budgets, database journal policy, transaction admission and external event-delivery semantics.",
 "telemetry":{"tokenUsage":"not reported","estimatedContextAvoided":"not measured","queryPolicyExecutionCount":"not reported","writePolicyExecutionCount":"not reported"},
 "nextUse":"npm run evidence:order:faults -- --check"
}
