Skip to content

Δ9 — Inspector poll + completion for remote runs (reuse the poll backstop) #33

Description

@jack-champagne

C1. Repoint the existing inspector poll backstop (RunsRootWatcher POLL_MS) at a remote run — via the Δ4 poll endpoint or a local-mirror sync of the S3 run-dir — and handle the Δ5 completion ping. No new inspector paradigm (it's already a poll architecture).

Acceptance (TDD): a state-machine test (à la watcher_statemachine.test.ts) drives a remote run through warming → poll-delivered frames → completion against a faked poll endpoint, asserting the same inspector calls as a local run.

Depends on Δ4, Δ5.

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 (Δ9) · phased plan §5a (plan-20260603-124231-amicode-phased-build) · aws-infra/INFRASTRUCTURE.mdThe 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:webviewenhancementNew feature or requesttrack:cloudTrack C — company compute / cloud solve-service

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions