Open
Conversation
Why: schema validation tests and custom schema hosts should work without the verifier rewriting non-CommandLayer URLs to HTTPS. Contract impact: none
…essing-chain [runtime] preserve schema-verifiable chained receipts
…lidation-failure [runtime] preserve custom schema hosts in verifier schema checks and add deterministic schema regression test
…g test fail fast with explicit per-step errors instead of hanging on opaque fetch failures.\nContract impact: none
…-in-runtime-signing.test.mjs [runtime] Harden chain test diagnostics
Why: expose the exact stalled network step in CI before the full-chain signing test hits its suite timeout. Contract impact: none
…mprove-logging-and-timeout-handling [runtime] improve chain test failure diagnostics
…uiltins Why: The chain verify test set VERIFY_SCHEMA_CACHED_ONLY=0, causing /verify to call getValidatorForVerb() synchronously. The schema network fetch (default 15s timeout) outlasted the test client's 5s abort timeout, producing an AbortError before the builtin fallback was ever reached. Setting SCHEMA_FETCH_TIMEOUT_MS=50 in the test makes the network attempt fail fast so the server falls back to builtin schemas immediately, well within the client timeout. Contract impact: none https://claude.ai/code/session_01WNKXjEEi48x86HETyYPhBr
…-h3GcK Add schema fetch timeout configuration to signing test
Why: ensure the end-to-end signing chain test follows cached-only validator warmup behavior in CI instead of hanging on cold schema startup. Contract impact: none
…-for-schema-verification [runtime] Make schema chain test deterministic
Why: cached-only /verify warmup should avoid CI flakiness from remote schema fetches when builtin schemas already exist. Contract impact: none
…t-schema-warmup [runtime] prefer builtin schemas during validator warmup
…n schema verification test resilient to cached-only validator warmup while routing verify warmup through the shared helper.\nContract impact: none
…y-and-improve-warmup-handling [runtime] tighten verify warmup polling and centralize cached-only warmup
Why: multi-step runtime flows need a stable trace id and unique per-step receipt ids without breaking signing or verification. Contract impact: additive receipt/response fields only; existing signing and verify behavior preserved
…del-to-runtime [runtime] add flow trace ids to signed receipts
Why: commons receipts must reflect the real runtime execution surface instead of payment-gated x402 semantics. Contract impact: commons receipt fields now use entry/verb/version/class and remove nested x402 blocks; commercial x402 semantics remain out of scope for this repo.
…-runtime-entry runtime: emit commons receipts with canonical execute entry
Why: preserve existing runtime receipt/signing behavior while exposing a single POST /execute entrypoint. Contract impact: none
…ute-route Add unified POST /execute route that dispatches to existing verb handlers
Why: /execute was forwarding nested execution envelopes to handlers that expect the legacy flat request shape. Contract impact: none
…ormalization Normalize /execute request bodies before verb dispatch
Why: bring the runtime layer back into sync with the current CommandLayer Commons v1.1.0 contract and remove stale commons/payment drift. Contract impact: commons receipts, docs, fixtures, and package metadata now consistently present the v1.1.0 current-line shape; no new protocol behavior introduced.
…commandlayer-v1.1.0 Align runtime to CommandLayer Commons v1.1.0 and remove Commons x402 drift
Added a JSON configuration file for CommandLayer with details on version, description, identity, runtime, supported verbs, schemas, SDKs, tech stack, compute constraints, task categories, and repositories.
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
2 participants
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.
No description provided.