[anycodes]

The exported Node schema still reserves e2b although the authoritative Python registry permits it as an installable catalog id. Remove that stale reservation, preserving the other ids and all 23 configuration keys. Both READMEs now describe usable source-checkout/local-dependency installation because an actual anonymous public npm metadata request returned HTTP 404.

Fixes #1. Fixes #2. Authoritative Python/server revision: Alibaba-Agent-Sandbox/python-sdk@145341d.

Changes:

• Correct one JSON reservation and add a regression through the built public export; no provider/cloud implementation or package publication.
• Update both README languages, changelog and repository-owned engineering records.
• Introduce the repository's first PR CI workflow (there were no existing workflows): Node 20/22, fixed Python 3.12.15 and server SHA, lockfile install, complete Python-vs-Node JSON comparison, typecheck and the existing real local server-loop tests.

Validation:

• Built unchanged schema plus new public-export regression: 1 FAIL, true !== false; fixed full suite 9 PASS / 0 SKIP.
• Full current JSON structure equals the actual pinned Python config_keys.py --json export, including all 23 keys and metadata.
• npm ci, typecheck, and direct real local agent loop: PASS. Health/command/file round trip and SIGTERM/reaping succeed with the matching Python server; no cloud credentials.
• npm pack and fresh consumers installed from both local checkout and tarball: PASS. Both import the public package and verify reservations, env name and ServerClient export. The npm 12 pack JSON shape initially required a verification-harness correction; no product failure was hidden.
• Workflow YAML, record links, scoped diff and configured-secret scan: PASS. Original untracked contributor-workflow proposals are untouched.

Exact head e1144aa: newly introduced Node.js 20 and 22 CI both PASS. Root independently reviewed all 9 scoped files and additionally ran typecheck, all 9 tests and the direct real local loop successfully; no blocking findings. No existing CI pass is invented and no publishing workflow, release or cloud behavior is added.

Records: .agents/notes/proposed/process/2026-10-18-config-provider-reservations.md and .agents/evidence/verify/2026-10-18-config-provider-reservations.md.