Skip to main content
Version: 0.1.0-alpha.4 (alpha)

Resource recovery qualification, 20 September 2026

Four bounded standalone profiles passed on source d70d4e724728fc833ca4f29bfaf100e12b35cd44 after the blob staging reclamation fix in PR #453. Every requested dormant population was admitted; sampled processes, threads and listeners plateaued, active ownership returned, and each node shut down cleanly and was reaped. These observations are from the shared Docker Desktop host, not a dedicated performance machine.

ProfileSamplesResult
Provider smoke23All seven checks passed
Provider campaign72All seven checks passed
Actual Angular web smoke48All seven checks passed
Actual Angular web campaign59All seven checks passed

Provider smoke completed all eight HTTP and eight blob churn arrivals successfully. The campaign retained 96 arrivals per provider: 56 successful blob operations and 43 successful HTTP operations. The remaining 40 blob and 53 HTTP arrivals were failed or unfinished outcomes, not throughput. No closed provider diagnostic codes were observed. Final post-churn provider recovery succeeded.

The provider matrix attempt 08 has status failed because its later web setup used an incorrect compiler path. Its two completed provider profiles remain individually passed. A new web-only matrix attempt 09 used the actual compiler and passed both web profiles. The original failed matrix is retained alongside the successful observations; no result was rewritten.

The raw receipts, their build identities and both matrix outcomes are linked below. JSON bytes are unchanged and each has a SHA-256 sidecar. Runtime binaries were built from the recorded source; later source-capture tooling and this documentation commit are not relabelled as measured runtime revisions.

Scope at this checkpoint​

At this checkpoint, standalone secret/event/child-call campaigns, OCI token/resolver/redirect pool accounting, multiple resource ceilings and shared-storage deduplication measurements were still outstanding. Later measurements and the closure decision are recorded in resource qualification #239; they do not change the four observations retained here. JavaScript allocator heap bytes were not exported; unknown values remain unknown. Actual browser qualification belongs to #236, and cold/warm conclusions remain scoped to the recorded host and profiles. The four passing profiles do not certify the full Phase 3 gate.