Skip to content

fix(admission): qualify the actual execution environment before scheduling work #241

Open

Description

@ebarti

Implementation progress — 27 October 2026

Implementation candidate; acceptance not yet qualified. #263 prepares and verifies the actual execution environment and carries candidate-bound readiness receipts.

The original mandatory gate and current integrated environment still require qualification. Durable installation completion remains tracked in #237; resource admission/descendant closure in #242 and final unpaid-repair reservation/GO accounting in #243 are separate unfinished contracts.

The referenced candidates are open and unmerged in stack #253. This progress map is non-closing; issue acceptance remains authoritative. Historical text below calling #238 open is superseded: #238 merged as c43cf0b.

Problem and evidence

Healthy API/Temporal processes and free role slots did not establish delivery readiness. The incident encountered stale repository/base/scope registration, unavailable offline dependency artifacts, missing browser binaries in isolated homes and Temporal-backed tests without their required server/CLI binding.

A small controlled test passed with the correct environment while the original broad gate still lacked valid completion evidence. Environment diagnosis must not be presented as product acceptance or used to waive the real gate.

Required behavior

  • Before dispatching a batch, validate current repository/base and issue-scoped plan, paths, commands, endpoint and capabilities against the original authorization.
  • Prepare and probe the actual isolated role/check environment: locked dependency graph, cache/network policy, tool executables, browser binaries, writable artifact locations and required local service/backend bindings.
  • Check installed runtime/persistence durability using the shared installation contract.
  • Record candidate/config/toolchain-bound readiness evidence and reuse it only while those inputs remain valid. Detect changed inputs before launch.
  • Distinguish deterministic configuration refusal from retriable preparation failure; report the owning component and smallest permitted remediation.
  • Avoid starting expensive model roles or every item in a batch when a shared prerequisite is known to fail. No automatic scope expansion, weakened gates or silent network-policy changes.

Acceptance

Use real owned preparation and execution paths with empty/offline caches, incomplete browser homes, missing/mismatched Temporal test binaries, stale base/scope registration and later corrected configuration. Verify a failed readiness check launches no product role and consumes no product repair cycle.

After remediation, run the original mandatory gate in the same prepared environment and retain its real result and artifacts. Selected smoke success alone cannot satisfy that gate.

Existing implementation to reuse

PR #238 is open at bfc918a545ce820f47c814e99a6fe5e92b1c3fc1, matching the inspected installed runtime. Reuse its native dependency and environment custody. This issue qualifies the complete actual execution environment before dispatch, including shared batch prerequisites.

Dependencies

Blocked by:

These are required contracts for this issue's acceptance. Related work without a blocking relationship can proceed in parallel.

Blocks:

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions