Δ10 — Estimator integration (v0 = tshirt_sizing) + per-solve routing UX

[jack-champagne]

C1. Wire aws-infra/examples/tshirt_sizing.py's logic (A-v1) at SolveSpec-assembly time → an offload suggestion (vs local RAM) + the cloud sizeClass; per-solve explicit routing (executor: remote / 'run on company compute'), agent-may-suggest, user-confirms. No auto-routing (D7 dropped the classifier). The real solver×integrator estimator is deferred (C2, calibrated from Δ7 records).

Acceptance (TDD): given a SolveSpec, the estimator returns a sizeClass matching tshirt_sizing.py on the same {N, levels, num_qudits}; an estimate over the local-RAM threshold surfaces the offload suggestion; nothing auto-routes.

⛔ Gate: blocked by the wk-3 freeze — run-dir contract + SchemaPackage v0 (amicode #15 + the #28–31 stack). RemoteExecutor/the S3 layout is the run-dir contract, so do not start until that lands.

📄 Refs: Spec armonissima/specs/spec-20260628-amicode-cloud-solve-service.md (Δ10) · phased plan §5a (plan-20260603-124231-amicode-phased-build) · aws-infra/INFRASTRUCTURE.md → The Analysis Pipeline (reuse step_function/ec2_launch_template/dynamodb/runner_image).

Evolve, not build — a working v0 (the aws-infra Analysis Pipeline) already does size→S/M/L EC2→julia→S3→email→terminate. Validate on staging (mirrors prod), then two-step promote.

[jack-champagne]

Re-scoped: the routing-UX slice moved to #63 (→ @kateebonner). This issue is now the estimator only — port tshirt_sizing (A-v1) at SolveSpec-assembly → sizeClass + the offload-suggestion signal. Plumbing; @Rchari1. The estimate feeds Kate's routing UI (#63); Freeze-1 S12 keeps it upstream of the executor.

[jack-champagne]

Unassigned for now — Jack + Raghav will pick this up as integration-testing work (client-side cloud plumbing).

[kateebonner]

Picking this up (was listed under @Rchari1 — reassigning to me per the 7/18 handoff).

Status notes:

• The ⛔ gate is cleared: the wk-3 freeze landed (run-dir contract + SchemaPackage v0 via 0.1a — Establish the shared SchemaPackage as the single source of truth for all five config/artifact schemas #15 + the 0.1a — @amicode/schema: single source of truth for the five config/artifact schemas (closes #15-core) #28–31 stack), and Δ8/Δ9 (RemoteExecutor + inspector coverage) merged on 7/19 — the S3 layout this was gated on is real now.
• Plan stays as written: v0 = port the t-shirt-sizing logic to SolveSpec-assembly time → sizeClass + offload suggestion; per-solve explicit, no auto-routing; the calibrated solver×integrator estimator stays deferred (C2).
• New context: the Connections panel (design-of-record: Connections panel — credentialed backends (Company Compute + Pasqal Cloud) in the app UI #159, ADRs in docs: Connections design-of-record — glossary + ADRs 0001/0002 #158) is what makes executor: remote reachable for users — the estimator's suggestion surfaces in Δ10-UX — per-solve routing UX (local vs company-compute) #63's confirm UX on top of it.