Triaged: no code change is needed for this. This is an epic used as an index, not a change request. The body states where the gaps came from (an adversarial review of chat, channels, curators, memory, skills, tools and Kits) and then lists only what is "Already tracked": archie-core-c3zh, h3s0, trnd.2/.3, d0jp, 7ftt, 1ng1, sod1, egkf.12, x0wk, fkpe, 1j6w, ykrp, b6ks, 22ed, pgsb, ho86, plus the image-capability and agent2agent epics. No gap is described in the issue itself, so there is no requirement, no acceptance criterion and nothing for a workflow to build from this text — the substantive plans live in the cited issues, each with its own scope.
The tree has also moved a month past the epic's 2026-10-05 creation (release 1.61.2, 2026-11-07) and already covers much of the named ground: the harness setup terminal is shipped (ui/src/harness/SetupTerminal.vue) against the Approved docs/prds/external-agent-harness.md, personas are gone (CHANGELOG.md "Personas are gone"), curators are live code with definitions, activity and a runtime (internal/domain/curator), and messaging has a full domain (internal/domain/messaging). What I could not verify is the beads state of the 16 cited issues — that lives outside this repository, so I am not claiming they are closed, only that this issue adds no work of its own to them.
Recommended disposition: close this epic as a duplicate index of the cited issues, or keep it open purely as a tracker and route work through the children. If the operator believes the review found gaps that were never filed, that is a new, specific issue listing those gaps; it is not a code change this issue can be routed as today.
Triaged: no code change is needed for this. This is an epic used as an index, not a change request. The body states where the gaps came from (an adversarial review of chat, channels, curators, memory, skills, tools and Kits) and then lists only what is "Already tracked": archie-core-c3zh, h3s0, trnd.2/.3, d0jp, 7ftt, 1ng1, sod1, egkf.12, x0wk, fkpe, 1j6w, ykrp, b6ks, 22ed, pgsb, ho86, plus the image-capability and agent2agent epics. No gap is described in the issue itself, so there is no requirement, no acceptance criterion and nothing for a workflow to build from this text — the substantive plans live in the cited issues, each with its own scope.
The tree has also moved a month past the epic's 2026-10-05 creation (release 1.61.2, 2026-11-07) and already covers much of the named ground: the harness setup terminal is shipped (ui/src/harness/SetupTerminal.vue) against the Approved docs/prds/external-agent-harness.md, personas are gone (CHANGELOG.md "Personas are gone"), curators are live code with definitions, activity and a runtime (internal/domain/curator), and messaging has a full domain (internal/domain/messaging). What I could not verify is the beads state of the 16 cited issues — that lives outside this repository, so I am not claiming they are closed, only that this issue adds no work of its own to them.
Recommended disposition: close this epic as a duplicate index of the cited issues, or keep it open purely as a tracker and route work through the children. If the operator believes the review found gaps that were never filed, that is a new, specific issue listing those gaps; it is not a code change this issue can be routed as today.
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.
Gaps from the adversarial review of chat, channels, curators, memory, skills, tools and Kits. Already tracked: archie-core-c3zh and archie-core-h3s0 (harness setup terminal), archie-core-trnd.2/.3 and archie-core-d0jp (curators), archie-core-7ftt (remove personas), archie-core-1ng1 (messaging dependency gate), archie-core-sod1 (dangerous-command authority), archie-core-egkf.12 (central-tools MCP gateway), archie-core-x0wk (agent profiles editor), archie-core-fkpe (tool-settings new fields), archie-core-1j6w (messaging health registry), archie-core-ykrp and archie-core-b6ks (non-web sessions), archie-core-22ed and archie-core-pgsb (session summary curator), archie-core-ho86 (Telegram /approve), the image capability epic, the agent2agent epic.
Imported from beads
archie-core-mqti· GitHub #1259 · type epic · priority P1 · created 2026-10-05Triaged: no code change is needed for this. This is an epic used as an index, not a change request. The body states where the gaps came from (an adversarial review of chat, channels, curators, memory, skills, tools and Kits) and then lists only what is "Already tracked": archie-core-c3zh, h3s0, trnd.2/.3, d0jp, 7ftt, 1ng1, sod1, egkf.12, x0wk, fkpe, 1j6w, ykrp, b6ks, 22ed, pgsb, ho86, plus the image-capability and agent2agent epics. No gap is described in the issue itself, so there is no requirement, no acceptance criterion and nothing for a workflow to build from this text — the substantive plans live in the cited issues, each with its own scope.
The tree has also moved a month past the epic's 2026-10-05 creation (release 1.61.2, 2026-11-07) and already covers much of the named ground: the harness setup terminal is shipped (ui/src/harness/SetupTerminal.vue) against the Approved docs/prds/external-agent-harness.md, personas are gone (CHANGELOG.md "Personas are gone"), curators are live code with definitions, activity and a runtime (internal/domain/curator), and messaging has a full domain (internal/domain/messaging). What I could not verify is the beads state of the 16 cited issues — that lives outside this repository, so I am not claiming they are closed, only that this issue adds no work of its own to them.
Recommended disposition: close this epic as a duplicate index of the cited issues, or keep it open purely as a tracker and route work through the children. If the operator believes the review found gaps that were never filed, that is a new, specific issue listing those gaps; it is not a code change this issue can be routed as today.