#27: port shell surfaces to xtask (ten interfaces)

[acoliver]

Current disposition, October 3, 2026

READY within the original ten-interface/F1 scope at f52234b7. Original full review and single findings-only follow-up resolved construction/standalone cancellation ownership. Final MSRV/stable/full/all16 release phases/extracted/native-read acceptance and candidate-identical-tree CI8pass completed. Historical strict deadline and SUN_LEN failures remain failed; delegated deadline control left2 empty dirs, so universal forced-KILL cleanup is not claimed. Terminal record: readiness-xtask.md/json.

No merge has been performed. Head/base changes require affected source and check reconciliation. Evidence under branch-2/evalwork/results/pr-remediation-20261002/.

Preserved earlier delivery description

The description below is retained as a time-specific record. Any pending/completed wording there is superseded by the current disposition above, without changing failed-command evidence.

Current-main remediation

Head a096e32eb0dc6d0c9a51e0b386fc64b0383aaa01 preserves original #302 ancestry, integrates main fc872110 plus exact shared #308 ec56694c/unique #194 fixtures, fixes the stable function-item cast normally, retains current provenance enforcement and adds the exact missing-models-lockfile witness. Ten-interface scope is retained; no scanner suppression, workflow/assertion weakening or compatibility reader was added.

Root/xtask fmt, MSRV/stable denied-warning clippy, xtask70+2, quality/compat/provenance and interface/publication/cancellation/deadline-cleanup fixtures passed. Original default-concurrency full MSRV test still reproduced tests/turn_deadline.rs:264 at1.145851333s. Phase diagnostics separately measured expensive synchronous failure persistence and approximately250ms bounded runtime teardown; a focused pass is not claimed as a repair or proof of historical cause. Native acceptance continuation uses bounded test concurrency with unchanged assertions and retains every failed attempt.

Final aggregate archive/extracted acceptance, native release/authenticated smoke and independent original ten-interface review are still active or incomplete. #321 tracks the separately observed empty-PID source-bundle fixture failure on another candidate. The original HTTP503 worker interruption and all source/gate attempts remain preserved.

Evidence: branch-2/evalwork/results/pr-remediation-20261002/{xtask302-prepared.json,xtask302-evidence}. Independent native review has its own immutable candidate/target. Published by nonforced SSH fast-forward for fresh exact-head Linux/macOS CI; keep draft, not merge-ready. No merge authorized or performed.

[acoliver]

Exact-head CI37062472422 on a096e32 completed8pass/0fail/0pending/1tag-only skip, including Linux/macOS MSRV/stable and release/source acceptance. Independent full ten-interface review nevertheless returned REQUEST CHANGES: release construction blocks in delegated helpers after SIGTERM, and standalone verification can exit leaving its helper/private directories behind. Its publisher delegated-deadline control passed, so this is scoped to the uncovered construction/standalone ownership boundaries.

Native Sol is repairing original F1 in a NEW isolated candidate with unchanged compiled adversary witnesses. Original published source and gate attempts remain untouched; the single findings-only follow-up and new exact-head CI will follow. Review’s own extracted run also retained a long-Darwin-temp socket failure; the passing CI does not erase that failure. Keep draft/not merge-ready; no merge or gate weakening.

[acoliver]

Native F1 cancellation fix is now published by nonforced fast-forward a096e32→f52234b713ef1e66baa71f66ac7b2a253aa8d62c; original source/refs/assertions remain. This owns release-layer helper scopes through cancellation, bounded reaping and private cleanup, including standalone verify, reusing existing reserved process-scope identity instead of a new runtime policy. Owning captured-pipe and SIGTERM construction/standalone witnesses, MSRV/stable fmt/clippy and owning ordinary gates passed.

The original independent review REQUEST CHANGES is still the admission record until its single findings-only follow-up completes. That follow-up has launched against an immutable exactf522 copy and original valid probes. Final aggregate/archive/extracted/native acceptance is also running. Fresh exact-head CI is requested; old a096 CI and earlier package acceptance do not certify f522.

Keep draft/not merge-ready. No merge, force-push, workflow/limit weakening, recycled/unowned PID signal or unrelated runtime redesign. Evidence: branch-2/evalwork/results/pr-remediation-20261002/fix-xtask-findings-ready.json.

[acoliver]

READY for a merge decision at exact f52234b7, replacing earlier a096 incomplete acceptance. Single original-F1 follow-up resolved construction/standalone SIGTERM child ownership/private cleanup with4 actual independent cases, all10 interfaces preserved,74xtask tests and6complete semantic fixture suites. Final native acceptance passed1066root+74xtask per MSRV/stable, all16 aggregate release phases, genuine extracted offline/package/direct-vendor gates and final authenticated read. Fresh exact-headCI37076879009 passed8checks,0fail/0pending,1tag-onlyskip; generated checkout53fe92f9 has candidate-identicaltree85f2e589.

Historical <1s teardown failures and SUN_LEN-extracted failure remain failed/root cause unresolved. Original bug-asserting cancel-build harness remains1, with separate positive cleanup proofs. Delegated deadline control passed bounded-timeout/dead-helper/no-publication but left2empty private dirs; failed empty-inventory assertion retained, no universal KILL/destructor cleanup claim. Supplemental archive-deletion timeout, cached-audit/bsdtar/live-operator limitations remain qualified.

Complete source/receipt/hashes reconciliation: branch-2/evalwork/results/pr-remediation-20261002/publication/readiness-xtask.{md,json}. No additional review cycle, weakened assertion or merge.