Skip to content

Merge pull request #44 from commandlayer/codex/implement-builtin-firs…#45

Open
GsCommand wants to merge 15 commits intocodex/implement-builtin-first-schema-warmupfrom
main
Open

Merge pull request #44 from commandlayer/codex/implement-builtin-firs…#45
GsCommand wants to merge 15 commits intocodex/implement-builtin-first-schema-warmupfrom
main

Conversation

@GsCommand
Copy link
Contributor

…t-schema-warmup

[runtime] prefer builtin schemas during validator warmup

…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
@railway-app railway-app bot temporarily deployed to CommandLayer Runtime / production March 20, 2026 23:08 Inactive
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
@railway-app railway-app bot temporarily deployed to CommandLayer Runtime / production March 21, 2026 15:10 Inactive
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
@railway-app railway-app bot temporarily deployed to CommandLayer Runtime / production March 21, 2026 18:03 Inactive
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
@railway-app railway-app bot temporarily deployed to CommandLayer Runtime / production March 21, 2026 18:29 Inactive
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
@railway-app railway-app bot temporarily deployed to CommandLayer Runtime / production March 21, 2026 18:51 Inactive
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
@railway-app railway-app bot temporarily deployed to CommandLayer Runtime / production March 22, 2026 03:36 Inactive
@railway-app railway-app bot temporarily deployed to CommandLayer Runtime / production March 22, 2026 05:39 Inactive
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.
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