Align runtime to CommandLayer Commons v1.1.0 and remove Commons x402 drift

[GsCommand]

Motivation

• Bring the runtime repository into strict alignment with the CommandLayer Commons current-line v1.1.0 contract and remove stale 1.0.0 assumptions.
• Remove accidental Commons dependence on inbound x402 payment metadata so Commons responses remain payment-agnostic.
• Ensure docs, examples, fixtures, package metadata, and tests all present a consistent v1.1.0 picture.

Description

• Stop reading x402 fields for trace/actor state and ensure traces and runtime_metadata are derived only from Commons-native request fields by updating handleVerb logic in server.mjs.
• Bump repository package metadata to 1.1.0 by updating package.json and the root entries in package-lock.json.
• Refresh golden fixture and generator (tests/fixtures/golden.receipt.json, tests/fixtures/make-golden.mjs) to the v1.1.0 wrapped Commons receipt shape and update tests/golden.mjs to validate the wrapper shape instead of asserting cryptographic verification inline.
• Update docs to state commercial/payment-aware behavior is out of scope for this Commons runtime and to consistently reference v1.1.0 schema/paths (README.md, docs/CONFIGURATION.md, docs/OPERATIONS.md, CHANGELOG.md).
• Add a regression test that proves Commons handlers ignore inbound x402 metadata (runtime/tests/runtime-signing.test.mjs) and remove stale smoke env usage of legacy CL_KEY_ID / CL_CANONICAL_ID.

Testing

• Ran npm test (unit tests + smoke); all tests passed (unit tests 26/26, smoke finished successfully).
• Ran the golden example check with node tests/golden.mjs; it passed and verifies the wrapped receipt envelope shape.
• Ran node --check server.mjs for syntax validation; it succeeded.

---

Codex Task