Isolate real-daemon CI evidence from restored build caches

[BunsDev]

Parent #884/#931; OpenCoven/coven-threads#31. Artifact 10152986441 from successful run 34477970475 contains current merge 63d1f33 manifests alongside older ad716af manifests restored with target/. Current Windows test log proves 18 cases passed, but aggregate artifact counts without provenance filtering are unsafe. Isolate each CI run/attempt evidence root outside the cached target directory; retain failed setup evidence and strict missing-artifact behavior. Add bounded fixture/workflow regression coverage and verify the next native artifact contains only current provenance. No runtime authority, deadline, or acceptance-gate changes.

[BunsDev]

Implemented and published in #931 at aa6bdfa. All Windows invocations share a test-only artifact-root override in an uncached checkout sibling, unique per run/attempt; upload reads exactly that root and preserves always()/missing-file failure. Local default unchanged. Parent caught and corrected unsupported runner.temp in job-level env before publishing; configuration uses supported github context. Two new regressions plus existing retention cases and13 workflow guards pass; full local target20/20 (15journeys+5artifact cases) passes with isolated output. Native CI34480282352 must prove the uploaded artifact excludes historical provenance before closure.

[BunsDev]

Run34480282352 at aa6bdfa executed20/20 Windows target cases (38.26s); workspace and feature-unit steps also passed. The job failed only at upload: actions/upload-artifact rejects relative dot/parent segments in an absolute glob. No daemon evidence artifact was published, so acceptance remains open. Corrected in 0c1b262: initialize runner.temp/run/attempt root through GITHUB_ENV in a supported step context before cache restore, and upload that same traversal-free absolute path. No runtime change or rerun-until-green substitution. Workflow regression was red before correction and13 guards now pass. Fresh native artifact proof remains required.

[BunsDev]

Native artifact isolation is now proven at 0c1b262 by run34482201141: upload succeeded, artifact10154746631 contains exactly28 manifests, all for actual merge07b53a6ac3fc73621d1c643685e316c1c505eb43, with no historical source revisions. It correctly retains26 passed and2 failed scenarios rather than substituting cached successes. Overall CI remains red on two initial daemon startups in the feature-off workspace target; those are separate lifecycle failures, not upload failures. Keep integration acceptance open; the engineering artifact-isolation criterion is satisfied in draft #931, not yet landed on main.

[BunsDev]

Final artifact-name refinement is verified at8576f41 by successful native CI34489425644. Artifact10157780426 is named threads-daemon-windows-0d8ccfca1725475b5e45f2ec47d8c4c2c45bc89d-34489425644-1; all28 downloaded manifests are passed and identify that exact clean merge. Windows executed20/20 target cases and152 feature-unit cases. Storage and upload names now both isolate run/attempt. Engineering scope is implemented and verified in draft#931; this issue remains open for reviewed main integration, not additional artifact code. Earlier startup failures and their evidence remain valid.

[BunsDev]

The artifact-isolation scope is complete and on main through #931 / foundation #1022 (main2de5aaa8). The previously recorded native receipts prove run/attempt-isolated storage and upload, strict missing-artifact behavior, and absence of restored historical provenance. Later diagnostic d3 run34724682607 also uploaded all90 complete manifests for its one actual synthetic source a45d11a; it was cancelled only during subsequent cache packing, not artifact isolation. That separate cache-save cancellation is tracked in #1037. Closing this implemented and landed engineering component does not close broad Phase-5/human gates or relabel the cancelled run as green CI.