Stabilize diagnostic export and preserve authorized policy continuity

This commit is contained in:
Karl committed 2026-10-14 01:18:23 +02:00
1 parent 0a5df7398e
commit 09bf616d98
18 files changed
+364 -57

No files matched your search

+14 -5
View File
@@ -84,6 +84,15 @@ that the whole application is clean, fully optimized or independently audited.
## Latest reproducible checks
The latest final-source Windows acceptance supersedes the historical failed
runs below:784 tests, lint, packaged-artifact verification, actual clipboard,
upload, process restart, local Gemma and audited Window/Worker transport tests
pass. All native browser lifetimes have zero export failures. Bounded exporter
FIFO, an SDK completion barrier, single-flight flush, verified policy continuity,
collector admission and idempotent private ACL startup are implemented.
See [current evidence and limits](diagnostics-backpressure.md). The separate
WebRTC engine crash remains reproducible in the official44.7.1 candidate too.
A subsequent full run after the Established-alarm regression added a test
passed 764 of765 and exposed a real gateway cancellation race: the policy
monitor aborted the provider but discarded its fixed409 error, producing500.
@@ -127,8 +136,8 @@ concurrency failure. A bounded export queue, single-flight flush and collector
commit-latency measurements are the next narrowly scoped diagnostics work;
mandatory inspection and audit durability must remain intact.
- Full source suite: 771 tests passed with `--test-concurrency=2`, no failures
or skips; see `artifacts/transport-owner-final-failure-ledger-suite.log`. An earlier
- Full source suite: 784 tests passed with `--test-concurrency=2`, no failures
or skips; see `artifacts/diagnostics-continuity-final-suite.log`. An earlier
higher-concurrency run failed one evidence-key ACL check; its cause remains
unconfirmed and its log is retained. All 18 evidence tests passed separately.
No ACL protection or timeout was weakened. `npm run lint` passed with zero
@@ -143,9 +152,9 @@ mandatory inspection and audit durability must remain intact.
literal and semantic payloads. Restart reused the protected device profile.
These are separate from packaged-artifact acceptance. The final literal and
actual-restart fixtures pass17+5 checks with zero lifetime exports failed.
The latest semantic receiver/model checks pass, but diagnostics acceptance
fails on three measured2s timeouts and one concurrency rejection. These are
retained as real failures, not cancelled exports or successful delivery.
The latest semantic receiver/model and diagnostics checks pass with zero
lifetime failures. Earlier three measured2s timeouts and one concurrency
rejection remain retained as real failures, with no retrospective cause claim.
- The protected local OpenTelemetry receiver reported zero rejected writes.
Trace `33b46998b44c3179cccd2826d5790c00` correlates browser.request,
browser.inspect.local, inspector.inspect, semantic load/inference and durable