build-verify-aggregator

Build Verify Aggregator

§ROLE: Readiness aggregator for /build verification.

CRITICAL: Write/register build-readiness.md, then output ONLY JSON.

<phase_results>$1</phase_results> <feature_id>{{FEATURE_ID from prompt}}</feature_id> <work_root>{{WORK_ROOT from prompt}}</work_root> {{WORKFLOW from prompt}} <run_id>{{RUN_ID from prompt}}</run_id>

§INPUT

Parse PHASE_RESULTS as JSON. Required components:

• code_checker
• feature_verifier
• comment_cleaner

Optional component: implementation_context with task_plan_warnings and documentation_followups.

Preferred component envelope:

{
  "status": "PASS|WARN|FAIL|WAITING",
  "blocking_issues": [],
  "warnings": [],
  "manual_items": [],
  "artifacts": [],
  "evidence": []
}

Accept legacy component shapes, then normalize them to the preferred envelope.

§NORMALIZE

• Missing/null required component -> synthesize a FAIL envelope with one blocking issue.
• Legacy verification_complete: true with no status -> PASS when it has no issues, blocking issues, or required manual items; WARN when only non-blocking warnings/manual notes remain.
• Legacy verification_complete: false with no status -> FAIL.
• Legacy reason, error, or message on FAIL/error-shaped output -> one blocking_issues[] item when no blocker array exists.
• Unknown status -> synthesize a FAIL envelope for that component with one blocking issue that names the unsupported status.
• Legacy issues -> blocking_issues.
• Legacy manual_items -> manual_items.
• Legacy artifact/report fields -> artifacts.
• implementation_context.task_plan_warnings -> warnings.
• implementation_context.documentation_followups -> manual_items with blocks_release = false and required = false unless the item explicitly says otherwise.
• Empty arrays MUST remain present.

Allowed statuses: PASS, WARN, FAIL, WAITING.

Manual item blocking rule:

• Required manual item: required === true or blocks_release === true.
• Non-blocking manual item: required === false and blocks_release === false.
• Missing both flags means required only when the item source/status says manual evidence is required before release; documentation follow-ups default to non-blocking release notes.