Repository navigation
[pre-1.0] Freeze the Python API and qualify the declared support matrix #119
Description
Purpose
Freeze the supported Python public API and packaging boundary, then qualify an immutable stability candidate. The coordinated stable target remains withheld until the cross-component gates pass.
Acceptance criteria
- Review exported APIs, errors, defaults, configuration precedence and compatibility guarantees.
- Validate CPython 3.11–3.14 on Linux x86-64/arm64, macOS arm64 and Windows x86-64.
- Pass public, restricted and local-only modes against isolated PHP and Rust Directory lanes.
- Pass the applicable risk catalog, online locked install and offline exact install.
- Meet the representative first-request budget with no manual secret transfer.
- Narrow package metadata to the proven range only after the matrix passes.
- Bind evidence to one immutable
stability-candidate; do not publish or tag 1.0 from this issue alone.
Intel macOS is outside the coordinated pre-1.0 boundary; future native Intel evidence is tracked in RobLe3/iicp.network#1253. Historical evidence remains preserved.
Activity
RobLe3 commentedon Aug 26, 2026
Source-bound API review recorded by root PR RobLe3/iicp.network#1114 at commit
3ad681bf1a8af2d4edcc9cbc54e0823631baedeb:PASS_WITH_QUALIFICATION_BLOCKERS. The documented package exports, CLI, configuration precedence, error boundary, and CPython 3.11–3.14 candidate policy are internally coherent; no release-blocking source defect was found. Keep this issue open for the 268-cell matrix subset, applicable edge cases, representative first-request evidence, package-metadata reconciliation, and immutable candidate.RobLe3 commentedon Aug 27, 2026
Qualification harness progress: PR #120 is merged at
7e581d00f3bd237ce97cc1c3d7741307ad101bcb. It adds the reviewed, content-free component case driver and exact scenario map used by the root executor registry. The driver unit tests and component-focused validation passed; the root registry now validates all six driver descriptions. This does not complete any runtime/target cell, edge execution, representative workflow or immutable artifact gate. This issue remains open for its actual qualification evidence, and no release, deployment or stable-version authority follows.RobLe3 commentedon Aug 28, 2026
Exact source-level qualification binding is merged by PR #121 at
77be8276b2a61500f0268582a7d8fbc42c945826.The support case plus all 25 applicable risk scenarios now bind distinct exact pytest nodes and consume every cell dimension plus immutable candidate/artifact/runtime/offline-environment digests. All 26 nodes passed individually; the full suite passed 1,222 tests with 2 skips and 9 passing subtests; Ruff, the existing mypy no-regression baseline, lock validation and CI passed.
This is source-level readiness only. It completes no runtime/OS/architecture/Directory/mode cell, package/offline gate, representative workflow, release, deployment, or 1.0/stability claim. #119 remains open for candidate-bound native executions.
RobLe3 commentedon Aug 28, 2026
PR #122 is merged at
319147d8e24901735eba4d0ae54c42d4be2cb22f. Source0.7.110now declares CPython 3.11–3.14 exactly and includes a clean-source wheel/sdist builder that proves locked build, exact online install, locked offline install and CLI self-report. The local macOS arm64 rehearsal passed, but no artifact was retained or frozen. This issue remains open for all-target package smoke, qualification environments and complete candidate-bound evidence; nothing was published or deployed.RobLe3 commentedon Aug 28, 2026
Root source-closure update: RobLe3/iicp.network#1186 now binds the Python assertions for eight required-stable client contracts into one three-SDK semantic crosswalk and verifies shared fixture digests where applicable. This is source evidence only; this issue remains open for exact packaged-artifact and declared-target qualification.
RobLe3 commentedon Aug 29, 2026
Python PR #129 is merged at
ac3a8bfd706e5fd04caa15a29856ef1df58010cc. It corrected the public client's local-only discovery filter so explicitIICP_PROXY_ALLOW_LOOPBACK_NODES=1behaves consistently with the pinned transport.Validation passed on CPython 3.11, 3.12 and 3.13; the clean-source package builder also passed on CPython 3.14.7. The new non-authorizing macOS arm64 fragment digest is
sha256:54aa75572cc0e8aafbe9030ff6cf78f9c57e2efe549ed6ae5e4cb793557473d0.That exact package then passed 10/10 direct and 10/10 routed 4 KiB loopback requests in the cross-client smoke retained by root PR RobLe3/iicp.network#1192. This does not close the issue: API freeze and declared target-lane qualification remain open.
RobLe3 commentedon Aug 29, 2026
Source boundary advanced through PR #130 to
dc800166bb8ed962df4945215b7438ad4b3b39cf. The supported HTTP task path now enforces the shared 1 MiB encoded request/response boundary, identity-only encoding, early and incremental rejection, bounded structured failures, and no success/receipt accounting for undeliverable output. The complete component quality gate and hosted check passed. A fresh macOS arm64 fragment validates atsha256:6b6637ea367b08bb996fc82545e28b564cfd0e57c5a722ff8ed14d1a47dc1960.This issue remains open: one local fragment is not the five-target support matrix, immutable six-component candidate, or representative qualification.
RobLe3 commentedon Sep 6, 2026
Python PR #133 is merged at 8cfa0cf. It corrects Windows HTTP-only/native-peeking separation, accept-loop shutdown, non-destructive process liveness and platform fixtures without new public exports or wire semantics. Recorded local quality: 1,256 passing tests on each CPython 3.11–3.14, locked package/install checks, lint, audit and coverage; affected tests also passed repeated runs. This is source evidence, not a clean Windows artifact pass. Root #1118 is rebinding the draft and invalidating only Python in the three retained local artifact sets. Qualification criteria remain open.
RobLe3 commentedon Sep 13, 2026
AWS Linux Directory v18 supplied the missing content-free boundary evidence for the Python 0.7.110 compatibility path. Against the Rust Directory, direct discovery returned HTTP 200 with exactly 3 nodes, 3 string node IDs, 3 endpoints, and 3 usable loopback route shapes. The Python adapter, with explicit local-only loopback and plaintext compatibility opt-ins, nevertheless returned
IICP-E006on the first permitted case and made no accepted matrix row.This narrows the next work under this issue: reproduce the external-Directory response in a deterministic local fixture and identify why
IicpClient.discover_async()yields no candidates despite the valid route projection. Do not weaken SSRF or confidentiality defaults; any fix needs a negative regression proving loopback remains refused without the explicit test/private-deployment opt-in.The AWS observation is diagnostic and non-authorizing; no release claim follows from it.
RobLe3 commentedon Sep 13, 2026
v18 IICP-E006 disposition: this was not the explicit loopback-admission bug. Python 0.7.110 admitted the loopback routes, but its normal
TaskRequestdefault projectedqos=interactive; the Rust Directory’s documented historical-evidence rule then excluded the freshly registered zero-history synthetic providers. The root compatibility adapter now suppliesTaskConstraints(qos=None)only for this basic Directory/SDK matrix. Public Python defaults and policy-before-ranking semantics are unchanged. The permitted case passed locally against the isolated PHP operator after this fixture correction; clean AWS evidence remains pending.RobLe3 commentedon Sep 16, 2026
Qualification harness fix committed locally on codex/pre1-harness-v3-binding: validate prepared v3 environment provenance and bind test-tooling identity separately from unchanged frozen product source. Exact tooling pins, clean-checkout checks and a four-file test-only allowlist refuse product/pin substitution. Component fixture tests pass; real Linux arm64 metadata compatibility passes across all six components. This is zero-credit compatibility evidence, NOT executor READY or final qualification. Root #1143 carries coordinated receipt invalidation and remaining packaged-assertion/runner blockers. No publication, deployment or AWS allocation performed; review/push pending final local preflight.
RobLe3 commentedon Sep 16, 2026
Integration update: the component v3-environment/separate-tooling-pin patch has passed required checks and merged to main. The coordinated registry now binds exact merged tooling commits and unchanged frozen product sources. Six-component metadata compatibility and all 74 local contract commands pass; no final executor was promoted and no qualification credit is claimed. This issue stays open for packaged semantic assertion proof and final candidate-bound execution. No package publication, deployment or AWS allocation occurred.
RobLe3 commentedon Sep 16, 2026
Installed-package adapter implementation is backed up on codex/pre1-packaged-sdk-execution (f27c198). The driver requires iicp.pre1-package-execution.v1, exact frozen wheel bytes, isolated staged assertions, digest-bound test dependencies and checked SDK import origins. The four credential/signature assertions now call the existing runtime verifier in staged fixtures; original vector IDs and expected decisions remain unchanged. All nine targeted installed-wheel checks passed on native macOS arm64 / CPython 3.13, and the 23 driver/adapter contract tests pass. A full local mapping rerun is running. This is project-owned local adapter evidence, not cross-runtime/target qualification or independent adoption. API/package version and frozen product artifacts are unchanged. Root #1143 remains the receipt-integration owner; do not close this issue or promote executor readiness.
RobLe3 commentedon Oct 9, 2026
Native Windows successor sentinel diagnosis found the package-execution helper eagerly evaluating the legacy HOME fallback even when IICP_PRE1_PREPARED_PACKAGE_HOME was explicit. PR #144 contains the smallest tooling-only correction and a no-HOME regression test. The failed AWS run remains diagnostic with zero credit; a clean successor-bound retry is required after merge and harness rebind.