[CompleteDotTech]

Split keyless hosted Linux GNU tests, musl tests and GNU release builds into four fresh package shards per workload. A shared manifest checks original-versus-expanded root labels; consumers verify source/run/artifact identity and recompute disjoint package assignments. Original exclusions, flags and required aggregate gates remain. Historical output weights are estimates, not proof of physical headroom.

This qualification aggregate retains the existing Windows cache policy, supported provider/sample constructor and accepted SDK LF fixes. It includes fixes for strict Clippy, policy fixtures, Opus header staging, copied-package helper controls and mapped rollout groups. A required Linux host companion runs the original ownership assertions; the ordinary suite remains sandboxed and its optional precondition return cannot qualify ownership coverage alone.

The latest diagnostic changes add a fixed first PowerShell entry marker and bounded retained-capture metadata while preserving the original10-second timeout and same failure. Failure-only managed-proxy diagnostics report bounded path/interpreter facts; unavailable observations remain unknown. Original HTTP200, proxy capture and direct-egress denial assertions remain. Neither diagnostic establishes the underlying cause or implements a production permission change.

The aggregate retains Fence first in audit mode while updating its finalized pin to v0.12.5, correct the policy inventory for the two package jobs, add bounded sanitized PowerShell fixture stages without changing its10-second timeout/assertions, and transfer the existing #62 explicit V8 tar.gz type fix without changing version/URL/checksum/patches. PowerShell stages are diagnostic only; their failing Linux phase remains unknown.

Refs #18, #41, #50, #54, #62, #67, #71, #81. Prior work: this updates existing PR83. PR78 owns the earlier cache policy, PR92 the constructor/sample repair, PR84 the helper controls, PR48 Wine work, and PR73/#62 the existing archive-type fix. Fresh bounded repository/CompleteDotTech searches for ownership timeout and managed-proxy diagnostics returned no matches; original ownership and donor commits are preserved.

Frozen headd7bddc80065a74e4636aa30930250e08d4fa2477, tree8cada6a9e4989688a480cea72a75afdc1db4d65c. Review base17975a80a8c224989b10e6df5d9bdcb34f2cfadd stays fixed. Proposed normal local merge against accepted08185f4bf3990ee3068f84ddbecb6f5070cdff8e has that same tree. Source is signed and clean; no accepted local merge is claimed.

Validation:

• Exactd7: all237 Windows Python policy tests passed, zero skips,58.728s. Only two test files differ from ce3; their blobs exactly match independently reviewed donors, and all9808 other entries are unchanged. Affected Linux/proxy runtime remains unrun.
• Prior exactce3: all235 Windows Python policy tests passed, zero skips,54.615s. Applicable source formatter/static checks passed. Independent source PRELIM reviews found zero actionable findings; FINAL streak0.
• Exactce3 local WSL qualification: the full ordinary rollout suite passed162/0/0 under linux-sandbox, while its required uncached host companion passed1/0/0 under local execution with the exercised chown/worker/materialization marker. The ordinary optional group case honestly reported not_exercised; the strict companion supplied the actual positive coverage. All162 own-name results, BEP strategy/cache records, artifact/source custody and cleanup were independently read back by ROOT.
• Exactce3 local WSL missing-helper case passed1/0/0 uncached under linux-sandbox, with raw/BEP/source/cleanup readback. This qualifies that copied-package control only, not the separate proxy case or full sandbox suite. These WSL results are not fresh-VM qualification.
• Prior328 hosted manifest artifact: verified digest and exact synthetic tree,1430 test/1279 release labels with original-expansion equality and disjoint185/171 package assignments, including the strict rollout companion. These are unconfigured query results, not configured closure or suite/headroom proof.
• Prior9d2 hosted Fence/blob-policy job122963841966 passed on synthetic a8599ab/tree8fd0c2e, with healthy Fence evidence. The same run's GNU shard4 again timed out in the first PowerShell ownership fixture; other jobs remained active at this publication. The later ce3 blocking run40733707423 has one observed GNU shard1 PowerShell10-second timeout with no parsed stages; remaining jobs were queued/running at the latest readback. Empty retained markers do not prove startup cause. Exactd7 hosted CI is pending publication.
• Donoraf4324e passed five focused tests and official20-target argument-comment/Clippy gates with recorded cache-supported results. These are donor results; the corresponding source blobs are retained.
• Local9d2 rollout built successfully, but the listing harness supplied incorrect argument separators and observed zero cases/162 filtered. The guard rejected it; zero rollout coverage is credited. Corrected current-source preparation requires fresh review and actual names/results.
• Private registry/Opus archive copying passed full hash audit. Subsequent E4 source materialization stopped before Opus on missing private V8 input. The distinct ce3 declared266-input repair passed full hash audit; current-source materialization remains pending; this is not an observed patch, compilation or install result.

Remaining: exact-current full configured closure/runtime integration, full hosted CI and capacity, affected Linux PowerShell diagnosis, Wine timeout, managed-proxy re-exec ENOENT, fresh VM/installed/live-provider acceptance, and three consecutive fresh independent FINAL reviews after the last relevant change. Current fresh disposable VM qualification is not run; shared-host/static evidence is not maintainer-ready VM confirmation.

Keep draft and unmerged; issues stay open. Publication updates only the owned feature branch. No GitHub merge or remote base/default/integration update is authorized or requested.

[CompleteDotTech]

Prior work: repository issue and CompleteDotTech PR searches for ownership fixture diagnostics found no competing record; this continues #18 / PR83.

The PR head remains d7bddc80065a74e4636aa30930250e08d4fa2477. A separately published diagnostic branch, diagnostic/67-linux-ownership-fixture, pins 352d401a65994a49eeddab58634704105eccc7c3 and isolates a manual Linux module run from normal CI cancellation. Its source and caller-error fixes passed independent PRELIM reviews; local Windows policy tests passed 256/256. Three FINAL clean reviews and acceptance remain pending.

The focused Linux run failed its existing 10-second fixture cutoff: 44 tests ran, with one timeout. The first literal marker arrived at 10,376 ms; the collector returned at 16,257 ms. The child later exited zero and owned cleanup completed, but that late result remains failed qualification. This establishes a pre-marker delay, not its underlying cause. Raw logs remain private; no timeout, assertion or provider gate has been waived.

This is GitHub-hosted Linux evidence, not a separately provisioned test-VM result; fresh VM validation is UNRUN. Normal D7 CI continued separately. No GitHub merge, accepted local merge, remote base update, installed-fork or live-provider acceptance is claimed.

[CompleteDotTech]

Prior work: this continues the existing #67 / PR83 ownership-fixture investigation and the earlier diagnostic comment; repository searches found no competing publication. PR83 remains at d7bddc80065a74e4636aa30930250e08d4fa2477.

The separately published diagnostic/67-ownership-full-module branch pins signed commit f0376bcf04f54f7b33da4a0b3486901f027d8325, tree 99816b9b73d4a926c9505948767c5428fb7977b1. Its new manual route runs the unchanged full ownership module once, with the original ten-second fixture limit and no PowerShell warmup or retry. Source review found no actionable issue; this is preliminary review, not final acceptance.

The once-only full-module run failed: 44 total, 41 passed, one timeout error and two existing platform skips. Parent-observed entry arrived at 8,249 ms; collector-call at 11,666 ms, after the qualification cutoff; collector-return at 12,830 ms. The child was live at the cutoff, later exited zero, and owned cleanup completed without a retained lease. The timeout remains failed qualification. Raw log SHA256: 404a5033dd13a3375e5468668ca7c699ab2b6cf26c7730248ec5079e0969acd7; raw contents remain private.

Earlier minimal/full single-case controls passed on f6e55fb64649cd3b4ab07eff07e146016bc9a625. They do not qualify this full module or establish a matched-host cause. The failure is observed before collector entry; runtime initialization, script loading and scheduling remain unresolved possibilities. No timeout or assertion has been weakened.

This is GitHub-hosted Linux evidence; separately provisioned fresh test-VM verification remains UNRUN. No full-matrix, Windows-runtime, installed-fork or live-provider acceptance is claimed. No GitHub merge, accepted local merge or remote base update occurred.