waiting_human names who, not what: the operator cannot tell what is being asked. Rename the status to waiting_approval and carry what the approval is for as its kind (plan from human.approve, review gate findings, handoff, etc.), so every surface (task page, list, chat, notifications) shows the kind and the thing to approve. review_gate already carries one such kind; fold it in. Done when no waiting_human remains in state store, contracts, UI or workflow docs, existing rows are migrated, and each approval kind renders what it asks for.
Close reason
Status renamed to waiting_approval everywhere with a data migration; tasks carry approval kind (plan or review) shown beside the status; plan approvals render the plan with Approve/Reject on the task page
Imported from beads archie-core-t1uf5 · GitHub #1830 · type task · priority P1 · created 2026-10-24 · closed 2026-10-24
waiting_human names who, not what: the operator cannot tell what is being asked. Rename the status to waiting_approval and carry what the approval is for as its kind (plan from human.approve, review gate findings, handoff, etc.), so every surface (task page, list, chat, notifications) shows the kind and the thing to approve. review_gate already carries one such kind; fold it in. Done when no waiting_human remains in state store, contracts, UI or workflow docs, existing rows are migrated, and each approval kind renders what it asks for.
### Close reason
Status renamed to waiting_approval everywhere with a data migration; tasks carry approval kind (plan or review) shown beside the status; plan approvals render the plan with Approve/Reject on the task page
---
_Imported from beads `archie-core-t1uf5` · GitHub #1830 · type task · priority P1 · created 2026-10-24 · closed 2026-10-24_
sam
added the hightask labels 2026-10-27 13:40:58 +00:00
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.
waiting_human names who, not what: the operator cannot tell what is being asked. Rename the status to waiting_approval and carry what the approval is for as its kind (plan from human.approve, review gate findings, handoff, etc.), so every surface (task page, list, chat, notifications) shows the kind and the thing to approve. review_gate already carries one such kind; fold it in. Done when no waiting_human remains in state store, contracts, UI or workflow docs, existing rows are migrated, and each approval kind renders what it asks for.
Close reason
Status renamed to waiting_approval everywhere with a data migration; tasks carry approval kind (plan or review) shown beside the status; plan approvals render the plan with Approve/Reject on the task page
Imported from beads
archie-core-t1uf5· GitHub #1830 · type task · priority P1 · created 2026-10-24 · closed 2026-10-24