finalize-promoted-knowledgelisted

# Finalize Promoted Knowledge Flip reviewed drafts to approved. This is the step that turns a filed proposal into product truth — for a pure knowledge update with no design work attached, this step (not a design document) is what closes the request. ## Dispatch One synchronous `Agent`-tool call, `subagent_type: solution-architect`, with `business-analyst` and `documentation-steward` named in the prompt as supporting lenses. ## Required inputs - The promoted requirement register in draft status. - The resolved Solution-Architect open questions from clarify-requirements. ## Required outputs (all mandatory) - Each promoted document's lifecycle status flipped from draft (`Requirements`) to `Approved`. - Requirement-register rows marked finalized. - The target's status record set to pass or pass_with_risks, with blocking questions confirmed empty. - The destination folder's README index confirmed current for every finalized document. ## Rules — draft-state discipline (closing half) - Nothing flips to `Approved` while any Solution-Architect question is unresolved — zero open questions is the precondition, not a preference. - Do not skip the status flip because the design work itself feels done; a draft-status document left behind after the run moves on is an unfinished job. ## Result Report each required output produced (with its location), the result (pass / pass_with_risks / blocked / failure), and blocking questions as an explicit list (empty list stated explicitly).