Doc Run Manual Screenshots

When a manual chapter is content-complete (per doc-add-entity-chapter) but still carries [SCREENSHOT NEEDED] placeholders that need turning into real, correctly-cropped images before the chapter is ready for human review.

Run How do I capture screenshots for a manual chapter? end to end:

1. Its Prerequisites section — build if needed, then ready the environment (fresh database, Acme Corporation provisioned by you, not the user), then confirm the chapter itself already builds. Non-negotiable, in order — never capture against a build or database that predates the entity's current state.
2. Its capture/wire-in sections — a test_scenario with one step per placeholder, run through the QA Validation Runner, each capture cropped and named per convention, wired into the chapter, both the PDF and the Qt-embedded help rebuilt, then handed off for human review — this skill's job ends at a chapter with real images in place, not at marking the task DONE.

Leave Clients in = Scenario Info= genuinely empty* for a single-client scenario (the common case) — any non-empty value there, even a placeholder like "single client", makes the Runner load zero steps, silently.

• How do I capture screenshots for a manual chapter?
• How do I ready up an environment?
• How do I document an entity? — the recipe this one follows on from.

• Archetype: doc_test_scenario.org.mustache — the test_scenario doc shape.
• QA Validation Runner: in-app test tracking for the multi-worktree fleet — the panel this skill drives.
• Devops Run Client — --open-scenario mechanics.
• code-run-feature-test — sibling skill sharing the same environment-readying recipe, applied to feature verification instead of screenshot capture.