Skip to content

Prepare 1.9 bounded store workflows and Transform selection - #74

Merged
ThorFuchs merged 10 commits into
mainfrom
codex/1.8-selection-main-qa
Nov 10, 2026
Merged

ThorFuchs merged 10 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.

Merge main at 1.8.0 (66718f1, located root-array streaming) into the
bounded store workflows and Transform selection candidate. The candidate
now targets 1.9.0, matching the roadmap. Resolve the source-line header,
CHANGELOG (Unreleased 1.9.0-dev above the published 1.8.0 and 1.7.1
entries), CLI version 1.9.0-dev with its assertion, and the regenerated
CLI source identity. Retitle the current-authority, API, contributing,
release-line and README banners from 1.8.0-dev to 1.9.0-dev. Historical
1.8-named records keep their file names. Candidate APIs, algorithms,
tests and fixtures are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ThorFuchs ThorFuchs changed the title Prepare 1.8 bounded store workflows and Transform selection Prepare 1.9 bounded store workflows and Transform selection Nov 9, 2026
@ThorFuchs

Copy link
Copy Markdown
Owner Author

Retargeted to 1.9.0 (maintainer decision, 2026-11-09). 1.8.0 was published from 66718f1 as located root-array streaming (#78/#79), and the roadmap now places bounded structural workflows in 1.9.0.

Merge commit 1c0988d brings main at 1.8.0 into this branch. History is kept and no commits were rewritten. Only bookkeeping conflicted: AGENTS source-line header, CHANGELOG (Unreleased — 1.9.0-dev above the published 1.8.0/1.7.1 entries), CLI version 1.9.0-dev with its assertion, and the regenerated CLI identity. The README, Documentation/README, API.md, CONTRIBUTING and ReleaseLines banners now say 1.9.0-dev and published 1.8.0. Historical 1.8-named files keep their names. Candidate APIs, algorithms, tests and fixtures are unchanged.

Locally after the merge: swift build --build-tests passed, all 35 qualification-harness cases passed, and public_check reported no errors. The new CI run on this head is the authoritative check. This stays a draft. Making the store API public still needs separate maintainer admission (AGENTS.md currently says the store is package-only).

Merge main at 5362626 (#81 composition per-document input and charged
completion, #82 README for 1.8.0). Combine the Unreleased 1.9.0-dev
CHANGELOG entries, set JSONIntegrationTests to 45 (43 here plus #81's two
owned proofs) in the native, portable and WASI inventories and the
harness assertion, and regenerate the CLI source identity.

This candidate builds JSONIntegrationTests with -strict-memory-safety
-warnings-as-errors. Mark #81's test-only withUnsafeCurrentTask
cancellation hook with unsafe, using the same justification as the
existing composition contract test. Behavior is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ThorFuchs

Copy link
Copy Markdown
Owner Author

Reconciled with main at 5362626 (#81 composition accounting, #82 README) in merge commit f788cd2. No history was rewritten, and the PR is mergeable again.

  • CHANGELOG: both Unreleased — 1.9.0-dev entries are combined.
  • Test inventory: JSONIntegrationTests is 45 (43 here plus Account composition input per document and charge completion (1.9.0-dev) #81's two owned proofs) in the native, portable and WASI lists and the harness assertion. The CLI source identity is regenerated.
  • One semantic conflict, fixed: this candidate builds JSONIntegrationTests with -strict-memory-safety -warnings-as-errors (Scripts/ci.py workflow-strict step). Account composition input per document and charge completion (1.9.0-dev) #81's new CompositionOwnedProofTests used withUnsafeCurrentTask without the unsafe marker, which failed that build locally with two errors. It is now marked with the same justification comment as the existing composition contract test. Behavior is unchanged.

Local checks: the strict JSONIntegrationTests build passed, swift test passed for JSONIntegrationTests (45) and JSONCLITests (88), all 35 harness cases passed, and public_check reported no errors. The fresh CI run on f788cd2 is the authoritative check. This stays a draft; making the store API public still needs maintainer admission.

The maintainer approved the read-only configured store/follow surface as
public API on 2026-11-10, superseding the package-only store policy on
main. Record that in AGENTS.md (now the 1.9 candidate), the roadmap's
1.9.0 row (the store is no longer "if separately admitted"; admission does
not waive the release gates), the read-only store decision in the
qualification record and the bounded-workflows contract. This admits the
API shape only; merge and release remain separate decisions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ThorFuchs

Copy link
Copy Markdown
Owner Author

Maintainer decision (2026-11-10): the read-only configured store/follow API is admitted as public API, overriding the package-only store rule in AGENTS.md on main.

Recorded in deb82a4, documentation only:

  • AGENTS.md: now describes the 1.9 candidate and the admission, with merge and release still separate decisions.
  • ReleaseRoadmap.md: the 1.9.0 row now lists the store as admitted; admission does not waive the gates.
  • Qualification/Release1.8.md: an admission note under Read-only store decision.
  • BoundedWorkflows1.8.md: an admission line and the 1.9.0 target.

The remaining items the PR description lists still stand: final-source Apple SDK/runtime refresh, performance and allocation decisions, and release-candidate coherence.

@ThorFuchs
ThorFuchs marked this pull request as ready for review November 9, 2026 23:44
@ThorFuchs
ThorFuchs merged commit d02b75b into main Nov 10, 2026
20 checks passed
@ThorFuchs
ThorFuchs deleted the codex/1.8-selection-main-qa branch November 10, 2026 00:37
@ThorFuchs
ThorFuchs restored the codex/1.8-selection-main-qa branch November 10, 2026 00:38
@ThorFuchs
ThorFuchs deleted the codex/1.8-selection-main-qa branch November 10, 2026 00:46
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