workflow-fix: post codex verdict from file, no body paging
Highlight text on any card (body, plan, or an event) to anchor a comment, or leave a whole-task comment here. Mention @claude to summon a reply.
No comments yet.
Overview / Motivation
Auto-filed by the /daily 2026-07-11 parked-candidate routing pass (Step C) from a workflow-fix candidate parked on task #1252 (emitting agent: methodology critic, plan review round 1; parked under the recursion guard).
Goal
On trigger-dense review rounds the orchestrator posts the Codex twin's verdict from its output FILE without paging the findings-bearing body into context — grep the verdict line only; post-marker --file needs no full read.
Workflow gap
- Bug observed: orchestrator pages the Codex twin's findings-bearing output body into context on trigger-dense rounds just to post the verdict marker.
- Why it is a workflow gap:
.claude/skills/issue/SKILL.md§ Codex dispatch / verdict-posting guidance is silent on file-only verdict posting for trigger-dense rounds; the #1252 discipline-4 fix covered the SUBAGENT return-text contract but not the ORCHESTRATOR-side posting path. - Confidence (emitter): low
- verified-at-filing:
grep -c "grep the verdict line only" .claude/skills/issue/SKILL.md→ 0 hits (2026-07-12) — the guidance is absent from the skill;.claude/rules/trigger-dense-review.mddiscipline 4 (shipped by #1252, commit 5529832f54) governs reviewer return text, not the orchestrator's post-marker read.
Proposed change (candidate diff sketch — refine in planning)
(none — synthesized from prose follow-up) Add to SKILL.md's Codex dispatch / verdict-posting guidance: on trigger-dense rounds, extract the verdict via grep -m1 '^\*\*Verdict:' <output-file> (or the twin's verdict-line convention) and post the marker with post-marker --file <output-file> — never Read the findings-bearing body into orchestrator context.
Scope / surfaces
- Primary target:
.claude/skills/issue/SKILL.md - Grep the workflow surface for the pattern before editing (
grep -rln 'verdict' .claude/rules/trigger-dense-review.md .claude/skills/issue/SKILL.md) and keep the new orchestrator-side rule consistent with discipline 4 in.claude/rules/trigger-dense-review.md.
Constraints / invariants
- Workflow-surface only — never experiment code,
configs/, ortasks/. scripts/workflow_lint.py --check-askspasses; ruff on touched files passes; ifworkflow.yamlorCLAUDE.mdchange, they stay consistent with the rule file.- This session runs under
EPM_WORKFLOW_FIX_SESSION=1and carries aworkflow_fix_target:Provenance line — it MUST NOT auto-route any of its own subagents' workflow-fix candidates (recursion guard).
Provenance
- workflow_fix_target: .claude/skills/issue/SKILL.md
- fingerprint: 6801241b3143
Origin (parked prose candidate on #1252, 2026-07-11T16:10:40Z): "source: prose-followup (methodology critic, plan review round 1). target_file: .claude/skills/issue/SKILL.md (§ Codex dispatch / verdict-posting guidance). proposed_change: on trigger-dense rounds the orchestrator posts the Codex twin's verdict from its output FILE without paging the findings-bearing body into context — grep the verdict line only; post-marker --file needs no full read. confidence: low."