Skip to content

Extend 1.1 acceptance and fix failed Base64 retention accounting - #14

Closed
ThorFuchs wants to merge 3 commits into
docs/1.1-release-readinessfrom
codex/1.1-qa-and-conformance
Closed

ThorFuchs wants to merge 3 commits into
docs/1.1-release-readinessfrom
codex/1.1-qa-and-conformance

Conversation

@ThorFuchs

@ThorFuchs ThorFuchs commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner

Caught malformed Base64 previously left freed scratch charged to the native decoder's logical-retention ledger, so ordinary caller recovery could cause a later false quota refusal. Restore only that failed decoder reservation; keep successful ownership, consumed work and terminal operational errors intact.

Add 19 meaningful acceptance/conformance functions across JSON, Schema, Patch and streaming: seeded exact native/foreign payload round trips, range oracles, canonical padding, real index boundaries, cumulative budgets, source diagnostics, shared immutable inputs and accepted sink prefixes. Extend the public mobile consumer and add an exact-cardinality supplemental QA lane. Correct the API lookup description and distinguish historical and candidate streaming measurements.

Validation on Swift 6.4 / Xcode 27.2 / macOS 27:

  • Full native debug/release and ASAN: 175 functions, all prior 173 parameterized invocations; TSAN five sharing cases and strict memory safety pass.
  • All 49 cap probes and pinned independent corpora retain exact discoveries, evaluated outcomes and policy exclusions. Rooted public consumer retains 20 cases.
  • Reviewed final boundary cases pass debug/release/ASAN; all 48 earlier Swift test files are byte-identical. Both mobile SDKs, both simulator families and physical iPhone public/disk checks pass.
  • Final DocC: four catalogues, 582 documented public symbols, 10 executed README examples and static site checks.
  • Three matched release Base64 benchmark pairs cross no new 10% timing trigger. Existing +15.76% candidate stream disposition is retained.

Source bindings distinguish the full tested core from test/documentation successors. Physical iPad remains a release blocker. This PR is draft; no protected-stack merge, tag or 1.1 publication is performed.

Integration status (2026-10-12): this reviewed component is included in the full candidate merged into main through #16, commit e9c6693. All protected integration Native checks passed in run 38268997289. Main's tree exactly matches frozen candidate 65d86ed. This component PR is closed as integrated; its original description, head branch and qualification history are retained. Tagging and release publication remain separate.

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