C3R v0.1.0 integration candidate: reconciled host readiness and developer API

[wilkont]

Integration candidate — not release approval

Reconciles the five PR #6 production commits individually: their final source tree is identical to reviewed local 45f2a86. Deliberately joins ancestry while preserving reviewed readiness changes; no existing branch is force-updated. This is the replacement integration candidate for PR #6, not authorization to merge it or deploy production.

Implemented

• Hash-only scoped API keys, tenant/project identity, revocation/expiry and operator-local key CLI.
• Request IDs, canonical developer errors, per-project/key limits and bounded route admission.
• Real Responses SSE with cancellation before backend headers and during idle generation; verification before generation; no private reasoning fields.
• Metadata-only usage with unknown GPU allocation/cost explicitly null, not invented billing.
• Official unmodified Python 3.24.0 and JavaScript 7.27.0 SDK HTTP acceptance; developer documentation and CPU-only exact-source qualification configuration.
• /v1/c3r/execute remains disabled; recommendation/inference only.

Verification

171 local tests pass with both SDKs enabled; selected strict Pyright and Ruff checks pass. Independent Standards and Spec code review findings resolved. Local fixture inference is protocol evidence, not GPU qualification.

Deployment reality

System One: self-hosted CLM + Qwen3-8B. System Two: self-hosted DeepSeek V4.1 Flash. Existing 8×H100; no OpenRouter/hosted inference or additional GPU infrastructure in this deployment plan. MC-1 excluded.

Public traffic remains off. NFSD/VSOCK enforcement, security queues, 18/18 host preflight, managed TLS, deployed key-store controls, live infrastructure CVoC/exact metering, cold starts/load/SLO/drills/canary, final Cloud Build/image scans and independent release approvals remain pending. No production tag, trained-weight/calibration claim or Hugging Face promotion.

[wilkont]

Qualification is still pending. This PR remains draft and is not approved for merge, public deployment, or a production release. Detailed reviewer evidence remains in the approved access-controlled channel. No production-readiness claim is being made.