Skip to content

docs(dag): avoid hardcoded acceptance worker-type whitelists #499

Description

@LeXwDeX

This was generated by AI during triage.

Why

The v1.0.37-dev.3 acceptance used a hardcoded nine-agent checklist that omitted build, even though workflow blocks compile coding and prototype to build and the runtime can resolve it. At that release, the model-facing WorkflowTool catalog also filtered primary agents, so build and plan were absent from the list available to the acceptance worker.

Audit correction

The original issue incorrectly called {explore, build, plan, general} the runtime-compat catalog. runtime-compat.json records the compatible runtime repository and commit; it is not a worker-type catalog. Environment validation derives valid worker types from the live agent catalog.

The underlying model-facing catalog defect was fixed by #507 / PR #509 after v1.0.37-dev.3:

  • packages/opencode/src/tool/registry.ts now includes native primary agents for WorkflowTool, exposing build and plan while preserving TaskTool behavior.
  • packages/opencode/src/dag/environment-catalogs.ts derives validation worker types from agents.list().
  • packages/opencode/src/dag/blocks.ts still intentionally maps coding/prototype to build.

The flagged checklist lived in ignored .opencode/workflow-drafts/, so there is no tracked acceptance asset left to repair in this repository.

Resolution

Closed as already implemented by #507. Future acceptance workflows must use the WorkflowTool/environment catalog and normal workflow validation rather than inventing a closed worker-type whitelist.

Evidence

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions