implement, tdd, feasibility (through approval into implement), triage (each route), remediate and pr-review were rewritten from Go into YAML over the general step types and have only been compiled and validated, never run. Done when each has completed one real task on a test repository, and the stored workflow-definitions resource has been restored to the shipped set (stored copies still name the deleted . types).
Acceptance criteria
Each named shipped workflow completes a real test-repository run, and a canvas-created workflow can be saved and run.
Notes
Sandbox runs (private samcharles93/archie-sandbox): triage completed; tdd opened sandbox PR #4; implement parked on the DeepSeek forced tool_choice bug; feasibility handed off to implement (waiting approval); remediate and pr-review pending; canvas-built workflow pending.
Also: build one new workflow only on the canvas, save it, and run it.
2026-10-24: on samcharles93/archie-sandbox, triage, tdd (PR #4), implement (PR #5) and pr-review (review on PR #4, task 16) completed. Remaining: feasibility awaiting operator approval of its implement hand-off; remediate needs a review event on archie's PR (webhook or binding for the sandbox), not a work request; canvas-built workflow.
2026-10-27: A-D not run. Dashboard API on the local instance rejects every credential available to the agent (accounts mode: needs a signed-in user session or personal API token; no archie CLI exists). Need a personal token (POST /api/tokens) exported for the run, then A-D can proceed.
Imported from beads archie-core-v6zm · GitHub #1281 · type task · priority P1 · created 2026-10-04
implement, tdd, feasibility (through approval into implement), triage (each route), remediate and pr-review were rewritten from Go into YAML over the general step types and have only been compiled and validated, never run. Done when each has completed one real task on a test repository, and the stored workflow-definitions resource has been restored to the shipped set (stored copies still name the deleted <workflow>.<stage> types).
### Acceptance criteria
Each named shipped workflow completes a real test-repository run, and a canvas-created workflow can be saved and run.
### Notes
Sandbox runs (private samcharles93/archie-sandbox): triage completed; tdd opened sandbox PR #4; implement parked on the DeepSeek forced tool_choice bug; feasibility handed off to implement (waiting approval); remediate and pr-review pending; canvas-built workflow pending.
Also: build one new workflow only on the canvas, save it, and run it.
2026-10-24: on samcharles93/archie-sandbox, triage, tdd (PR #4), implement (PR #5) and pr-review (review on PR #4, task 16) completed. Remaining: feasibility awaiting operator approval of its implement hand-off; remediate needs a review event on archie's PR (webhook or binding for the sandbox), not a work request; canvas-built workflow.
2026-10-27: A-D not run. Dashboard API on the local instance rejects every credential available to the agent (accounts mode: needs a signed-in user session or personal API token; no archie CLI exists). Need a personal token (POST /api/tokens) exported for the run, then A-D can proceed.
---
_Imported from beads `archie-core-v6zm` · GitHub #1281 · type task · priority P1 · created 2026-10-04_
Stored workflow definitions: cf1be167 repairs a stored collection that no longer validates at State Store startup, entry by entry. An invalid shipped entry is restored from the build, an invalid custom entry is removed and logged (its earlier revision stays in the resource history), valid entries are kept.
Canvas-built workflow: ef84e18f makes a new canvas workflow save the seeded agent identity (it parked with 'declares no identity to run as' before). Built, published and ran one from the canvas on the local e2e stack; it completed.
feasibility through approval into implement, and remediate: not run. The local e2e stack has no forge token for the sandbox (connection 'default' reads ARCHIE_GITHUB_TOKEN) and no usable model provider (aliases point at openai/gpt-5.4 with no openai provider). remediate also needs a webhook secret or an event binding for the sandbox repo. These remain, together with the v1.61.0 linked hand-off run.
Progress on the remaining items:
- Stored workflow definitions: cf1be167 repairs a stored collection that no longer validates at State Store startup, entry by entry. An invalid shipped entry is restored from the build, an invalid custom entry is removed and logged (its earlier revision stays in the resource history), valid entries are kept.
- Canvas-built workflow: ef84e18f makes a new canvas workflow save the seeded agent identity (it parked with 'declares no identity to run as' before). Built, published and ran one from the canvas on the local e2e stack; it completed.
- feasibility through approval into implement, and remediate: not run. The local e2e stack has no forge token for the sandbox (connection 'default' reads ARCHIE_GITHUB_TOKEN) and no usable model provider (aliases point at openai/gpt-5.4 with no openai provider). remediate also needs a webhook secret or an event binding for the sandbox repo. These remain, together with the v1.61.0 linked hand-off run.
Triaged: no code change is needed for this. No code change. #1622 is an operational verification checklist for the YAML rewrite, not a defect report: "done" means six shipped workflows each completed one real run on a test repository, plus a canvas-built workflow saved and run.
What is already in the tree against the issue's own criteria:
All six shipped definitions are in internal/domain/workflow/shipped/ and use only the general step types (agent.run, repo.*, gate.repository, review.*, forge.*, workflow.*). No <workflow>.<stage> type remains in the shipped set.
The stale stored copies the issue complains about are repaired by shipped code, not pending work. RepairDefinitionCollection (internal/domain/workflow/definition.go:391) replaces an invalid shipped entry with this build's copy and keeps valid custom ones; replacement/storedValueIsReplaced (internal/infrastructure/controlplanestore/registry.go:186-215) triggers it when a stored value no longer validates, and ImportConfig runs it for the default org and every org holding a workflow-definitions resource (registry.go:95-125). CHANGELOG 1.61.1 states this behaviour explicitly.
The canvas item is a capability, not a gap: WorkflowCanvas.vue, WorkflowEditor.vue, RunWorkflowButton.vue and the workflow-* e2e checks exist, and 1.61.1 already fixed the one blocker a canvas-created workflow hit ("now saves the agent it runs as, so it runs instead of parking with 'declares no identity to run as'").
So what is left is running things, and it is blocked on operator-side inputs, not on repository code:
Dashboard API access: in accounts mode the shared dashboard token is deliberately not a person (docs/security/authorization.md); the documented route is a session or a personal API token via POST /api/tokens. That is why "rejects every credential available to the agent" is expected, with a known remedy, not a bug.
feasibility is parked on an operator approving its implement hand-off; remediate needs a real review event on the sandbox (webhook or binding), which is configuration on the instance, not code.
The remaining real runs (remediate, pr-review already done per the 2026-10-24 note, canvas-built workflow) need a forge and model, which the e2e harness in e2e/ cannot supply (it is dashboard-only and, per its README, "run by hand or by an agent, never by task check or CI").
Because there is no observable wrong behaviour to reproduce and no unsettled design to write, none of implement/tdd/feasibility applies. Recommended close-out: obtain a personal API token, approve the feasibility hand-off, bind a review event on the sandbox, then record the run evidence on the issue and close it as verification complete.
Triaged: no code change is needed for this. No code change. #1622 is an operational verification checklist for the YAML rewrite, not a defect report: "done" means six shipped workflows each completed one real run on a test repository, plus a canvas-built workflow saved and run.
What is already in the tree against the issue's own criteria:
- All six shipped definitions are in `internal/domain/workflow/shipped/` and use only the general step types (`agent.run`, `repo.*`, `gate.repository`, `review.*`, `forge.*`, `workflow.*`). No `<workflow>.<stage>` type remains in the shipped set.
- The stale stored copies the issue complains about are repaired by shipped code, not pending work. `RepairDefinitionCollection` (internal/domain/workflow/definition.go:391) replaces an invalid shipped entry with this build's copy and keeps valid custom ones; `replacement`/`storedValueIsReplaced` (internal/infrastructure/controlplanestore/registry.go:186-215) triggers it when a stored value no longer validates, and `ImportConfig` runs it for the default org and every org holding a `workflow-definitions` resource (registry.go:95-125). CHANGELOG 1.61.1 states this behaviour explicitly.
- The canvas item is a capability, not a gap: `WorkflowCanvas.vue`, `WorkflowEditor.vue`, `RunWorkflowButton.vue` and the `workflow-*` e2e checks exist, and 1.61.1 already fixed the one blocker a canvas-created workflow hit ("now saves the agent it runs as, so it runs instead of parking with 'declares no identity to run as'").
So what is left is running things, and it is blocked on operator-side inputs, not on repository code:
- Dashboard API access: in accounts mode the shared dashboard token is deliberately not a person (docs/security/authorization.md); the documented route is a session or a personal API token via `POST /api/tokens`. That is why "rejects every credential available to the agent" is expected, with a known remedy, not a bug.
- feasibility is parked on an operator approving its implement hand-off; remediate needs a real review event on the sandbox (webhook or binding), which is configuration on the instance, not code.
- The remaining real runs (remediate, pr-review already done per the 2026-10-24 note, canvas-built workflow) need a forge and model, which the e2e harness in `e2e/` cannot supply (it is dashboard-only and, per its README, "run by hand or by an agent, never by `task check` or CI").
Because there is no observable wrong behaviour to reproduce and no unsettled design to write, none of implement/tdd/feasibility applies. Recommended close-out: obtain a personal API token, approve the feasibility hand-off, bind a review event on the sandbox, then record the run evidence on the issue and close it as verification complete.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
implement, tdd, feasibility (through approval into implement), triage (each route), remediate and pr-review were rewritten from Go into YAML over the general step types and have only been compiled and validated, never run. Done when each has completed one real task on a test repository, and the stored workflow-definitions resource has been restored to the shipped set (stored copies still name the deleted . types).
Acceptance criteria
Each named shipped workflow completes a real test-repository run, and a canvas-created workflow can be saved and run.
Notes
Sandbox runs (private samcharles93/archie-sandbox): triage completed; tdd opened sandbox PR #4; implement parked on the DeepSeek forced tool_choice bug; feasibility handed off to implement (waiting approval); remediate and pr-review pending; canvas-built workflow pending.
Also: build one new workflow only on the canvas, save it, and run it.
2026-10-24: on samcharles93/archie-sandbox, triage, tdd (PR #4), implement (PR #5) and pr-review (review on PR #4, task 16) completed. Remaining: feasibility awaiting operator approval of its implement hand-off; remediate needs a review event on archie's PR (webhook or binding for the sandbox), not a work request; canvas-built workflow.
2026-10-27: A-D not run. Dashboard API on the local instance rejects every credential available to the agent (accounts mode: needs a signed-in user session or personal API token; no archie CLI exists). Need a personal token (POST /api/tokens) exported for the run, then A-D can proceed.
Imported from beads
archie-core-v6zm· GitHub #1281 · type task · priority P1 · created 2026-10-04Progress on the remaining items:
cf1be167repairs a stored collection that no longer validates at State Store startup, entry by entry. An invalid shipped entry is restored from the build, an invalid custom entry is removed and logged (its earlier revision stays in the resource history), valid entries are kept.ef84e18fmakes a new canvas workflow save the seeded agent identity (it parked with 'declares no identity to run as' before). Built, published and ran one from the canvas on the local e2e stack; it completed.Triaged: no code change is needed for this. No code change. #1622 is an operational verification checklist for the YAML rewrite, not a defect report: "done" means six shipped workflows each completed one real run on a test repository, plus a canvas-built workflow saved and run.
What is already in the tree against the issue's own criteria:
internal/domain/workflow/shipped/and use only the general step types (agent.run,repo.*,gate.repository,review.*,forge.*,workflow.*). No<workflow>.<stage>type remains in the shipped set.RepairDefinitionCollection(internal/domain/workflow/definition.go:391) replaces an invalid shipped entry with this build's copy and keeps valid custom ones;replacement/storedValueIsReplaced(internal/infrastructure/controlplanestore/registry.go:186-215) triggers it when a stored value no longer validates, andImportConfigruns it for the default org and every org holding aworkflow-definitionsresource (registry.go:95-125). CHANGELOG 1.61.1 states this behaviour explicitly.WorkflowCanvas.vue,WorkflowEditor.vue,RunWorkflowButton.vueand theworkflow-*e2e checks exist, and 1.61.1 already fixed the one blocker a canvas-created workflow hit ("now saves the agent it runs as, so it runs instead of parking with 'declares no identity to run as'").So what is left is running things, and it is blocked on operator-side inputs, not on repository code:
POST /api/tokens. That is why "rejects every credential available to the agent" is expected, with a known remedy, not a bug.e2e/cannot supply (it is dashboard-only and, per its README, "run by hand or by an agent, never bytask checkor CI").Because there is no observable wrong behaviour to reproduce and no unsettled design to write, none of implement/tdd/feasibility applies. Recommended close-out: obtain a personal API token, approve the feasibility hand-off, bind a review event on the sandbox, then record the run evidence on the issue and close it as verification complete.