Skip to content

Prepare 1.8 bounded store workflows and Transform selection - #74

Draft
ThorFuchs wants to merge 7 commits into
mainfrom
codex/1.8-selection-main-qa
Draft

ThorFuchs wants to merge 7 commits into
mainfrom
codex/1.8-selection-main-qa

Conversation

@ThorFuchs

@ThorFuchs ThorFuchs commented Oct 29, 2026 •

Copy link
Copy Markdown
Owner

The 1.8 candidate adds ordered Inspection batches/read-only store workflows plus exact Transform source definitions, compile reports and finite indexed selection. Selection uses owner-bound positions, EOF-only completion, cumulative budgets and terminal lease accounting through the existing compiler/VM. Thirteen public products and empty root dependencies remain.

The candidate preserves PR #73's release-metadata observation, dynamic documentation labels, artifact packaging and main-only Pages guard. The four documentation-tooling paths still match main 3f73fa9; native workflow scheduling changes deliberately below. Product source, manifest, Swift tests, fixtures, resource policies and CLI identity are unchanged from the selection checkpoint dfa0f96. PR #71 and sibling work remain intact.

At 48dca4d, macOS and both Linux normal/safety lanes, DocC and Git-free archive reproduction passed. The Native and x86 normal jobs nevertheless hit their existing 60-minute job limits in appended composition steps: Native retained a completed nine-command composition receipt; x86 completed only five of nine commands. The cancelled checks remain cancelled; no blind rerun or timeout increase is used.

Successor c9a5a4c schedules the unchanged composition lane separately on macOS and both Linux architectures. Existing Native / ... and Linux / ... names become final gates over each complete execution matrix; only success passes, including after failure/cancellation/skip. Pages waits for these gates. Existing commands, pins, execution timeouts, fixtures and branch protection settings stay unchanged. Three regression cases cover wiring, fail-closed gate behavior and policy preservation; the exact harness cardinality increases from 32 to 35.

Qualification at c9a5a4c / synthetic ca7c8c2 (identical tree 2501403): all eleven execution jobs and all eight final product contexts passed in Native run 40936575244 and Linux run 40936575256. Normal Debug/Release roots: macOS 1,042 functions/390 parameter invocations; each Linux architecture 1,026/390. All three full nine-command composition lanes, ASan/TSan/strict-memory/lifetime, 49 caps, pinned independent suites, public consumers, 13 DocC catalogs/1,690 declarations and Git-free native/Linux reproduction passed. Fresh API graphs have no additions/removals/fragment changes versus 48dca4d. The actual PR site artifact's 5,525 members match its manifest and label source 1.8.0-dev/stable 1.7.0; Pages publication is correctly skipped.

The installed pinned Swift6.4/WASI lane also passed all 82 commands: 938 root functions/353 parameter invocations per configuration, Node/WasmKit public/cap scopes, independent suites, strict-memory and ABI. Optional host timing was explicitly omitted through the existing lane option. Two copied public-only consumers outside Git additionally passed 16 build/binpath/runtime commands across Debug/Release and Node/WasmKit (six definition witnesses and ten selection witnesses per run). These are path-dependent consumer checks, not version-tag resolution or new Swift Testing function counts.

Local prechecks, all 35 harness cases, all 22 documentation-site cases and YAML structure passed. Earlier timeout/storage/SDK-observer failures remain historical. Final-source Apple SDK/runtime refresh, source-specific performance/allocation decisions and versioned RC coherence still remain; this is not release readiness.

Keep historical 1.8 loaded-host regressions, unmeasured allocations and held final-source platform/performance gates explicit. No 1.7 waiver is inherited. No ready conversion, merge, tag or publication is requested.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant