Skip to content

test(m0): execute SDK capability probes and generate observed compatibility report - #72

Draft
afflom wants to merge 8 commits into
m0/offline-sdk-validationfrom
m0/sdk-capability-probes
Draft

afflom wants to merge 8 commits into
m0/offline-sdk-validationfrom
m0/sdk-capability-probes

Conversation

@afflom

@afflom afflom commented Oct 10, 2026 •

Copy link
Copy Markdown
Member

Closes #5 only when all remaining acceptance below is satisfied. This draft is not mergeable as a completed M0 implementation.

LexLean-authored probes execute through the digest-locked SDK and generate a source-bound compatibility report separating language, exporter, runtime and physical feasibility. Each primitive has independent export roots and request-dependent checks; no compression-specific compiler/runtime fallback is supplied. The mandatory sdk-capabilities prerequisite keeps full just vv failing when required functionality is unsupported.

This is stacked on #71 and includes its artifact-parent confinement correction. Pre-merge review also found that a successful app.verify command could be reported as runtime support after receipt validation failed. The corrected report returns evidence_missing, rejects empty capability inventories and duplicate observation IDs, and retains the SDK failure. Both new regressions failed against the earlier implementation. All 41 local Node tests now pass without skips: 24 capability/reporting tests and 17 offline-boundary tests. The documented red/green results are in probes/capabilities/README.md and the offline evidence document.

Current head: 87b9d70b6f4b56abcf81b26a5d9c3d887d818e42.

The earlier observed probe run was independently checked during this review: all 266 retained project/artifact/command-output hashes matched. It established these actual blockers in the unchanged SDK:

Requirement Observed missing capability
Byte buffers Generated Rust compilation fails PP4102 on borrowed-byte append.
Checked U64, indexed immutable bytes and Scan Export fails PP5004 on specialized runtime calls.
Persistent U64-addressed store Installed LexLean rejects language 1.2 during initialization.
Oracle invocation PP5301 at oracle construction: immutable offline cache lacks tokio.
Arbitrary binary transport and generated CLI/filesystem adapters TextApplication is insufficient; a qualified BinaryProgram SDK binding is required.

All five core modules kernel-verified in that run; this does not establish successful export/runtime support. Physical large-input feasibility remains unmeasured.

Remaining issue #5 acceptance:

  1. Complete selected-LexLean reconciliation through PrismPM #184 and the generic binary capability prerequisite PrismPM #186, including their actual dependency import and generated artifact closure.
  2. Pass complete upstream acceptance, reproducibility, security and native-platform inventory gates, then publish the qualified immutable multi-platform SDK. The current BinaryProgram runner-local qualification is not a published whole-SDK closure.
  3. Render the SDK/template/standards/devcontainer/workflow bindings through the supported process, bind and execute all required probes, and rerun all compression checks on both platforms.

No locks, required gates or branch protections have been weakened. Keep this PR and M0 open until those requirements pass. Independently supported M1 claim-disposition and ULEB128 work is authored in #74 and #75 following the explicit request to proceed with supported tooling; those PRs remain unmerged under the milestone merge prerequisite.

The additional local full-gate run passed model/source/Rust/formal/reproducibility stages and reached the runtime probes. It was stopped after the complete hosted results established the blocker on both architectures; no local full-pass claim is made.

@afflom
afflom changed the base branch from main to m0/offline-sdk-validation October 10, 2026 04:40
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.

Execute latest-main SDK reconciliation, bootstrap freeze, and capability report

1 participant