feat(workflow): registered steps covering the deleted .archie gate behaviour #1196
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#1196
Reference in new issue
Block a user
internal/domain/workflow/steps.go:215 and :227 now hard-error on legacy .archie/stages/*.go
and .archie/gate.go, telling the operator to migrate the behaviour to a registered YAML
workflow step.
docs/prds/runtime-control-plane.md ("Workflows") requires that the useful behaviour be
available as normal workflow steps first. BuiltinStepRegistry() only exposes the six shipped
workflows own stages, so there is nothing to migrate repository-specific gate logic to.
Scope: identify what the removed hooks actually did, and land the equivalent as registered
step types. Depends on plugin-supplied step types if the answer is that repositories supply
their own.
Notes
Closed 2026-09-21 under maintainer decision (B): the .archie/gate.go equivalent landed as gate.diff-rules (plus a follow-up making it fail closed on an empty diff), merged to main. The .archie/stages/*.go equivalent is carved out to the command.run decision bead because it changes the trust tier. steps.go:215's repo-stages error message was deliberately left untouched rather than made true with a command step.
Imported from beads
archie-core-8szi· GitHub #974 · type feature · priority P2 · created 2026-09-20Closed: goes against the product plan in epic #1977. Core gains no more built-in repository steps; forge and repository actions come from connectors (#1979, #1657).