Show publication and synchronization as independent task and agent milestones
I maintainer di solito rispondono entro 1 giorno
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Current evidence and impact
AgentResultLine.jsx shows a verified publication immediately but always says synchronization is not yet verified. Task detail/status views have no independent synchronization projection. A failed continuation must not make the publication disappear.
Chosen implementation
Consume the durable continuation and independently verified obligation states from the other children of #13760. Project pending/running/blocked/verified synchronization in task and agent detail/status, retaining the original publication timestamp and link. Use existing tasks:changed and agent:updated/socket events; add missing change events at their source, never periodic API polling. Keep execution status separate from both milestones, including completed historical records loaded by id.
Acceptance criteria
- Rendered interaction tests show publication unchanged while synchronization moves through pending, running, blocked and independently verified.
- Task details/status and agent cards reflect the same durable identity and exact sync PR/head where appropriate.
- Changes arrive reactively through existing event contracts without reload/polling.
- Terminal prose and task execution success do not synthesize verified synchronization.
- Parent and continuation views remain usable after completed history leaves the working set.
Areas: agent/task projections, server/lib/agentOutcome.js with client parity if changed, client/src/components/cos/AgentResultLine.jsx, tabs/TaskItem.jsx and relevant socket consumers.
Dispatch: model:medium for routine multi-view projection over established service contracts; effort:medium for event and historical-state parity. hardwareRequirements: [].
Part of #13760.
On delivery, check this child in #13760. If this was the last open child, summarize the delivered children and close #13760.
Blocked by #13772
- Lingua principale
- JavaScript
- Stelle
- 38
- Fork
- 32
- Merge medio
- 46m
- PR unite (30g)
- 993
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Issue simili
-
step.duration reflects only the last retry attempt (HelperStep.run() overwrites startTime)Forse già presa @mirao l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
codeceptjs/CodeceptJS#5774 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
Status: Unconfirmed
Difficoltà 1/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
AllTheMods/ATM10-Aeronautics#151 ·
I maintainer di solito rispondono entro 4 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
feimacode/open-design-agent-kit#66 ·
I maintainer di solito rispondono entro 1 giorno