Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-capabilitiesprerequisite keeps fulljust vvfailing 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.verifycommand could be reported as runtime support after receipt validation failed. The corrected report returnsevidence_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 inprobes/capabilities/README.mdand the offline evidence document.Current head:
87b9d70b6f4b56abcf81b26a5d9c3d887d818e42.sdk-capabilities; completed job logs confirm the owning recipe.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:
tokio.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:
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.