final-integration-checklisted

# Final integration check ## Purpose Audit the assembled article as one reader package and prepare portable Markdown and metadata, or an exact CMS draft payload when that is the requested destination. Confirm that text, media, captions, metadata, and publication boundary preserve the chief-editor meaning lock. This is an integration check, not another open-ended editing pass. ## Responsibility `final-integration-check`: - compares final reader Markdown with the chief-editor lock; - verifies real integrated assets against the media manifest; - aligns claims across text, image, caption, and `alt`; - checks markers, links, privacy, accessibility, and mobile behavior; - validates trust surface and the proposed CMS payload; - returns a `ready` integration handoff and minimal reader-surface package for `cold-reader-review`, or a precise owner and blocker. It does not change the reader promise, argument, section order, or claim without cause; create a missing visual; substitute illustration for proof; read or mutate CMS; create a draft; change a Suggested Topic; or publish. ## Inputs and priority Use: 1. `ready` chief-editor decision log and `lockedMeaning`; 2. locked reader Markdown and snapshot; 3. Article Brief and claim permissions; 4. `visual-storytelling` handoff with annotated draft, media manifest, production status, and deferred visuals; 5. real local assets or verifiable URLs; 6. captions, `alt`, source-of-truth, and privacy decisions; 7. author and publisher met