Δ8 — RemoteExecutor backend wiring (submit→poll→RunHandle, keyed on run-dir contract)

[jack-champagne]

C1. Implement the RemoteExecutor (today a NotImplemented stub) against Δ2/Δ4: submit(script, lab) → RunHandle{runId, events, finished, abort}, keyed on the run-dir contract, events sourced from the poll endpoint. Zero changes to the local path.

Acceptance (TDD): a LocalExecutor run and a RemoteExecutor run over the same script emit identical inspector/catalog event sequences (the S7/S11 snapshot test); the S12 executor-branch grep stays clean (no executor-type branches in RunsManager/Inspector/Catalog).

Depends on Δ2, Δ4.

⛔ 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 (Δ8) · 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]

Executor contract ratified (Track C spec Locked decisions; Phase-1 counterpart is #56). Build the RemoteExecutor to RunHandle{runId, events, finished, abort} with:

• frames best-effort — S7/S11 = identical terminal-on-resolution + best-effort stream (poll lossy vs fs.watch), not literal frame equality
• abort() = request — run alive until FINISHED/liveness-terminal; no post-abort assumptions
• terminal via poll + liveness — Δ4 status must carry a liveness signal so a box that dies without FINISHED resolves to an inferred terminal, not an infinite poll
• S12 — no executor-type branches downstream

#56 builds the Scheduler to the same seam, so this issue is only the remote half.

[jack-champagne]

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