build-and-reportlisted

# Build and Report Post-implementation close for a forge run. Merges work-unit worktrees (if any), bumps the version per the consuming project's convention, runs the project's build, and emits the final report. Stack-agnostic: concrete commands live in the consuming project's own CLAUDE.md. This skill handles two paths: - **Parallel-implementation path** — `/forge:dispatch-implementation` ran; one or more work-unit worktrees need merging into the active branch before build. - **In-session path** — the orchestrator implemented the plan directly in the main session; no worktrees to merge. Skip merge, go straight to version bump + build. ## Required Inputs - The approved master plan in conversation context (the report references its steps + risks). - One of: - All implementer reports from the most recent `/forge:dispatch-implementation` run (parallel path), OR - The orchestrator's in-session edit summary (in-session path). - The consuming project's CLAUDE.md, which provides stack-specific build commands and the version-bump rule. (Note: this is the user's project CLAUDE.md, NOT the forge plugin's own files.) ## Procedure ### 1. Aggregate implementation status **Parallel path:** for each implementer report: - Confirm "done-when criterion: yes" (not "no" / "partial-because"). Any "no" or "partial" is a blocker — surface to the user before proceeding. - Confirm the Blockers section is empty. If a hard blocker exists, route to the user; do NOT silently proceed to merge.