You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(unic-archon-dlc): /qa reports failed resolved writes only on the console #664
After a merge lands, merge in apps/claude-code/unic-archon-dlc/.archon/workflows/unic-dlc-qa.yaml writes the resolved role on every item the pull request links. When some of those writes fail, the run still ends completed, which #652 accepts. But the failed item ids reach only the console line merge: QA for "<slug>" complete …. They are not in merge's structured output and not in any file under <artifacts_dir>/<slug>/.
In AFK nobody reads that line, and uat-prep already notes that console output dies with the worktree. So an item whose resolved write failed stays at ready-for-agent, and a later AFK loop can pick it up again.
Found by review round 1 of PR #663, outside that ticket's scope.
Acceptance criteria
merge reports, as structured output, the ids of the linked items whose resolved write failed, and reports none when every write succeeded.
The same list is written to a file under <artifacts_dir>/<slug>/ that outlives the worktree.
docs/boxes/unic-dlc-qa.md says where an operator finds the list after an AFK run.
A run where every write succeeded behaves as it does today.
Reproduced by reading unic-dlc-qa.yaml at 5506f2ae on PR #663, not by a run. merge's output_format carries merged and reason only, and step 3 names the failed items in the closing console line alone. #652 ruled that a merge that landed ends completed even when some resolved writes failed, so this keeps that outcome and only makes the failure findable.
Blocked by #652, which adds the structured output this builds on. Left at needs-triage for the maintainer.
Closed as superseded by #678's resolution, approved by the maintainer on 2026-10-30: run 4 is dropped and unic-archon-dlc is frozen. Reason for this ticket: it carries one linked line to #687: a failed write recorded nowhere a later run reads.
Activity
orioltf commentedon Oct 27, 2026
Reproduced by reading
unic-dlc-qa.yamlat5506f2aeon PR #663, not by a run.merge'soutput_formatcarriesmergedandreasononly, and step 3 names the failed items in the closing console line alone. #652 ruled that a merge that landed ends completed even when someresolvedwrites failed, so this keeps that outcome and only makes the failure findable.Blocked by #652, which adds the structured output this builds on. Left at
needs-triagefor the maintainer./qaends green on paths where nothing merged #652orioltf commentedon Oct 30, 2026
Closed as superseded by #678's resolution, approved by the maintainer on 2026-10-30: run 4 is dropped and
unic-archon-dlcis frozen. Reason for this ticket: it carries one linked line to #687: a failed write recorded nowhere a later run reads.—
unic-sdlc-orchestrator-9