Integrate confirmed report workflow and review inputs (0.9.0)

references/content-handoff.md

@@ -6,6 +6,12 @@ Report structure and production are separate responsibilities. The optional `rep
 
 Accept a readable outline or page plan; no special file schema or compiler integration is required. Reuse stable page IDs and the user's agreed review sequence. For the current page, identify its purpose, what the audience should understand, content, evidence, necessary qualifications, progression within the page, relationship to adjacent pages, and allocation between visible content and speaker notes or appendix. A summary that introduces groups should match the actual groups and their organizing basis.
 
+For the extended structure workflow, receive the current lightweight page-explanation PDF and its editable page source together, along with the confirmed content scope, audience/professional starting point and execution choices. A slide's explanation may span several physical PDF pages; use stable slide IDs rather than assuming PDF page numbers equal slide numbers. Take actual slide text, formulas, required visual descriptions, dependencies and transitions from the editable source. Preserve its separation of screen content, required visuals and speaker/review analysis; analysis does not automatically become slide text. No reverse PDF parsing or installed structure Skill is required. Ordinary user plans remain supported without this specific PDF delivery format.
+
+The source identifies the contribution or judgment supported by the report, section and current page, including whether a portion presents a result or an objective analysis. Make each text/visual group serve those goals. Preserve required visual objects, relationships, directions, labels, data/sources and presentation order; optional decoration or equivalent visual expression follows production authorization. An addition that changes a fact, cause, conclusion strength or necessary premise first returns to the content plan. Do not default to adding limitations or self-undermining endings.
+
+Reuse the [confirmed execution choices](execution-and-review.md): specialist reviews and assignments, review after revision, page/block mode, ImageGen scope/budget and any selected alternatives. Ask once for consequential unresolved production choices, not for choices already supplied. A refusal alone does not identify a replacement Agent or tool.
+
 For reasoning or mathematical derivation, retain the necessary premises, definitions, key steps and conditions that make the next step valid. Show the exact premises again where the audience needs them. A task that explicitly needs only results may omit the derivation; keep the result's meaning, conditions and sources. Identify which evidence supports each conclusion and how the page should make that association visible. These details can live in the existing brief rather than additional required fields. A time constraint concerns the overall report or relevant sections; a time budget for every page is not required.
 
 Select layout and composition from those information relationships under the chosen template. Check the actual page's reading order, information burden and conclusion-to-evidence associations. Keep essential explanations and qualifications in the related main information; small text may retain sources, ranges, references and supplementary definitions. Fix ambiguous or overstrong body text directly, and remove preventive disclaimers that add no useful understanding or action. Preserve facts, numbers, source meaning and content boundaries even when the plan came from another Skill. A supplied plan is input, not proof of truth or authorization to generate all pages.
@@ -18,4 +24,6 @@ When the declared typography, spacing and supported layouts cannot accommodate t
 
 The content owner resolves chapter/order/selection changes. For one Agent handling both responsibilities, revise the content plan first and then produce the affected authorized pages; no extra peer or approval round is required for settled, reversible work. When order or page allocation changes, synchronize stable IDs and their destinations, page numbers, references and speaker notes. Keep necessary premises and key steps connected across a split.
 
+When source content or speaker explanation changes, return the affected IDs and source revision so the content owner can synchronize the current PDF and related analysis. Distinguish the received version from a later draft; an older PDF or approval does not validate changed content. Apply the agreed independent-review assignment to affected production revisions through [review after revision](execution-and-review.md#review-after-revision).
+
 User feedback about report logic goes to the structure Skill's maintained example/rule source when authorized. Feedback about fonts, spacing, layout recipes or template geometry stays with the production/template maintainer. A content-plan review does not establish visual, native-editing or projection acceptance.

references/execution-and-review.md

@@ -0,0 +1,40 @@
+# Execution choices and review
+
+Use the user's confirmed arrangement for the current report. This reference coordinates production with a content workflow; it does not introduce a compiler schema, scheduler or extra approval round. A local revision or single-page task only uses the relevant parts of the existing arrangement.
+
+## Confirm once and reuse
+
+Receive the existing execution table or equivalent readable choices with the content handoff. For a new or substantially restructured report, combine the review scope, assignments, budget and production choices into one request before dependent work. Offer a default arrangement and editable choices together; accepting the listed default once covers subsequent authorized pages, blocks and necessary revisions within that scope. Do not ask again for settled choices.
+
+The arrangement identifies the following as relevant to the task:
+
+| Choice | Record |
+|---|---|
+| Content transitions and page purpose | Main Agent, fresh-context serial reviewer, authorized block-parallel reviewers, or skipped specialist review; scope and budget |
+| Language, terminology and prior knowledge | Assignment, covered content and how results are reported |
+| Mathematics and other professional reasoning | Assignment, audience knowledge, scope and budget |
+| Review after revision | Default independent reviewer who did not edit that portion; any explicit main-Agent self-check or skip choice, and affected scope |
+| Production | Page-by-page or authorized block-parallel work, permitted pages and review granularity |
+| ImageGen layout drafts | Enabled scope/budget, skipped image drafts, or a user-selected main-Agent text composition/template preview alternative |
+
+These are human-readable decisions in existing project notes or the page plan, not mandatory JSON fields or a new file format. A choice can remain pending until first needed. Resolve consequential pending choices together before using the relevant tool or assignment; progress on independent authorized work can continue.
+
+Declining parallel Agents does not authorize serial sub-Agents. Declining all sub-Agents does not select main-Agent work for every step. Declining ImageGen does not decide whether to skip image drafts or use a text composition/template preview. Ask the user to settle the affected steps together, then reuse the answer. Do not silently choose a replacement, claim a different arrangement or remove all checks. Required production fidelity and current-page checks remain distinct from optional specialist reviews.
+
+A user's later change affects the stated scope; revise the same arrangement and apply it to affected work. Reviewing a new page layout is content feedback, not a new request for the same tool permission. A page-by-page choice never grants permission for unreviewed later pages; block production only covers the authorized block.
+
+## Review after revision
+
+By default, the agreed post-revision review uses a fresh-context Agent who did not participate in editing that portion. Reuse the once-confirmed assignment and budget. If the user explicitly selected main-Agent checking or skipped this review, follow and label that choice; do not describe it as independent review.
+
+Provide current deliverable source and preview as relevant, confirmed report/section/page goals, audience knowledge, criteria, original evidence and sufficient prior content to verify dependencies. Include precise premises, symbol meanings, conditions and source locations needed for the current use. Do not make the reviewer assume a preceding block has already explained them. A missing item in the review input is not proof that the whole report lacks it; allow source lookup, and distinguish missing evidence from an input gap.
+
+Before the reviewer forms a judgment, omit author self-assessments, expected pass/fail verdicts, defenses of the edits, leading summaries and earlier approval or resolution conclusions. Keep any old issue list separate. The reviewer first checks the current material and records locations and reasons; only afterwards compare specific old findings when needed. Preserve useful evidence rather than shortening away context to make the packet look neutral.
+
+The reviewer reports the actual version/scope, concrete issues, unresolved evidence and passed checks, with no finding quota or expectation of agreement/disagreement. The author resolves findings against sources. After a substantive further revision, independently recheck the affected portion and dependencies under the same agreed arrangement; old approval does not cover new text. Reuse unaffected valid checks.
+
+## What production checks
+
+Every title, paragraph, formula, label, figure and meaningful decorative group has an expression role serving the page, its section and the report goal. Keep the demonstrated contribution/judgment and supporting evidence. Do not add a limitations list, self-doubt or preventive defense merely because review began. Explain premises and facts that actually change the judgment with the relevant content.
+
+Review current reading order, visible evidence associations, required visual relationships, capacity and template fidelity. Keep content-plan review, image-draft feedback, native structure, actual rendering, editing and projection evidence separate. General review input principles do not require this Skill to repeat the structure Skill's full content analysis.

references/page-collaboration.md

@@ -6,7 +6,9 @@ Use one coordinator and one active writer per page. The coordinator owns narrati
 
 Consume the agreed audience, deck argument, page order and review cadence through [content handoff](content-handoff.md). Define stable IDs and a brief per page: its task, intended understanding, evidence, data/units, necessary premises and key steps, progression, conclusion-to-evidence associations, capacity, transition and content/notes/appendix allocation. Express these in the existing brief as relevant to the task; no new compiler schema or mandatory page-by-page time budget is needed. Report structure may come from the optional `report-structure` Skill or the user's own plan. Assign only pages authorized to proceed. Under `interactive-page`, review gates still apply; parallel workers do not authorize future pages or a batch.
 
-Freeze one template/version/theme, manifest and style input hashes, roster, fonts, glossary, shared data/assets. Use the project tools for the template snapshot and builder. Give each worker the same baseline, a visual reference when available, page brief and write allowlist. Read library examples from the selected template. Route shared changes to the coordinator before implementation.
+Receive the current editable page source and any accompanying explanation PDF, confirmed content scope and [execution choices](execution-and-review.md). Reuse page-by-page or block-parallel selection, review assignments and budget, ImageGen scope/alternative and confirmed layout preferences; confirm only consequential pending choices. Time pressure alone does not authorize parallel work. A refusal of parallel Agents does not choose serial Agents or main-Agent replacement.
+
+Freeze one template/version/theme, content-source revision, manifest and style input hashes, roster, fonts, glossary, shared data/assets. Use the project tools for the template snapshot and builder. Give each worker the same baseline, actual selected-template visual when a layout draft needs it, page brief, scoped confirmed preferences and write allowlist. Read library examples from the selected template. Route shared changes to the coordinator before implementation.
 
 Freeze shared container renderers/recipes, named text roles and supported variants as part of that baseline. Workers instantiate them with content and whole-container bounds; they cannot hand-position child text/icons or create private offsets. Include the [text/container constraints](text-and-containers.md) in page review. Any necessary paragraph fragments retain one logical text source/frame and a documented layout implementation; route shared recipe changes to the coordinator.
 
@@ -32,14 +34,14 @@ Source, content and notes must agree. Update table/chart metadata with data; pre
 ## Integrate and revise
 
 1. Compare template/theme/style baseline and incoming hashes. Reject stale baselines and duplicate writers; preserve the worker version for repair. Never silently accept a different theme.
-2. Check ID/layout, paths, evidence fidelity, notes, preview and object claims. Return precise issues to that page's worker; a coordinator may fix locally after explicitly taking over the page.
+2. Check ID/layout, paths, content revision, evidence fidelity, notes, preview and object claims. Return precise issues to that page's worker; a coordinator may fix locally after explicitly taking over the page. Verify cross-block dependencies and transitions from actual source, rather than assuming an earlier block supplied them.
 3. Integrate accepted source/assets. The coordinator updates `project.json` order/declarations and shared inputs, then runs `ppt_project.py lock`, `check`, and one `build`. A common roster/theme preserves common Master/Layout identities. Do not merge finished PPTX files as source integration.
 4. Review the integrated deck for narrative, terminology, units, title rhythm, density, figure scale, repeated icons and navigation state. Render it: per-page static checks cannot establish visual consistency. Shared-style changes require affected pages to rebase and rerender.
 5. Keep the agreed user acceptance granularity. Record accepted/revision-needed with evidence, then proceed to the next authorized pages. Pack after locks/integration pass. Another device supplies declared dependencies/fonts and runs its own application checks.
 
 Reauthor or repair only affected pages; integrated export still compiles the completed SVG set together. If content allocation or order changes, synchronize stable IDs and destinations, page numbers, references and notes with the plan, including links across split arguments. Reuse unchanged page content and valid prior checks. For shared changes identify affected pages before repeating checks. Author completion, integrated render and user acceptance remain separate states.
 
-Use independent review when it can resolve a meaningful understanding gap; it is not a fixed multi-Agent pipeline. Save new reference implementations only from actual received or produced material, with source, method and the scope of acceptance. Template geometry feedback stays with the template maintainer; report-logic examples and rule learning stay with the structure maintainer.
+Use the confirmed review-after-revision assignment; its default is an independent fresh-context reviewer who did not edit that portion. Supply current source and necessary criteria/evidence without author self-assessment, expected verdicts or leading summaries, and let the reviewer judge before seeing old resolution conclusions. Main-Agent checks or skipped reviews retain their actual labels. See [review inputs and affected scope](execution-and-review.md#review-after-revision). This uses the existing page ownership and handoff rather than a new scheduler or fixed Agent count. Save new reference implementations only from actual received or produced material, with source, method and the scope of acceptance. Template geometry feedback stays with the template maintainer; report-logic examples and rule learning stay with the structure maintainer.
 
 ## Research basis
 

references/production-rules.md

@@ -6,7 +6,7 @@ These rules apply across templates and authoring routes. **Required** rules prot
 
 - **C01 · Recommended:** consume the supplied audience, purpose, material boundary and page content plan, including the intended understanding, necessary premises and progression within the current page. Establish the production route, template and review rhythm from settled choices. If no plan is provided, form only the brief needed for the current authorized work; substantial report planning and example-derived content rules belong to the optional `report-structure` Skill. See [content handoff](content-handoff.md).
 - **C02 · Required:** preserve facts, numbers, conditions, causal relationships and strength of conclusions. Distinguish source statements, inference and added material. Do not invent unknown values. Identify synthetic examples and retain traceable sources for material claims.
-- **C03 · Required meaning and visual correspondence, recommended composition:** preserve the supplied page purpose, intended understanding, evidence and key steps. Make the association between each conclusion and its evidence visible, and check the actual page's progression and necessary context. Choose a suitable composition and reading order for those relationships; concrete layout methods may vary. Do not silently change chapter order or move essential content to notes. Return meaningful omissions, contradictions or capacity conflicts to the content plan; do not create a parallel report-structure rule library. Summarize only within the authorized content scope and without changing meaning; C02 governs required content fidelity.
+- **C03 · Required meaning and visual correspondence, recommended composition:** preserve the supplied page purpose, intended understanding, evidence and key steps. Every text, formula, label, visualization and meaningful decorative group serves the page, section and report goals. Make the association between each conclusion and its evidence visible, and check the actual page's progression and necessary context. Choose a suitable composition and reading order for those relationships; concrete layout methods may vary. Preserve demonstrated contributions and judgments without defaulting to limitations lists or preventive self-doubt. Do not silently change chapter order or move essential content to notes. Return meaningful omissions, contradictions or capacity conflicts to the content plan; do not create a parallel report-structure rule library. Summarize only within the authorized content scope and without changing meaning; C02 governs required content fidelity.
 - **C04 · Recommended:** keep hierarchy, color semantics, terminology, units, legends, strokes, icon grammar and component scale consistent across pages. Use declared template exceptions where needed.
 - **C05 · Recommended:** choose layout and columns from content relationships, then place components. Maintain grouping, alignment, spacing, reading order and moderate density. Add decoration for a purpose. Resolve excess content through the template's rewrite/layout/split policy; keep its declared typography and grid rules.
 - **C06 · Recommended:** inspect suitable components and page-library examples before authoring. Read their rationale and method; adapt, combine or create as needed. Remove example content, update data and metadata, and preserve reference attribution.
@@ -22,7 +22,7 @@ These rules apply across templates and authoring routes. **Required** rules prot
 
 - **C11 · Required:** implement text, shapes, connectors, tables and charts according to the selected route. Do not claim a full-page screenshot is editable completion. Use supported tools and disclose technical limits; do not silently change backend, depend on another installed Skill or introduce an online provider. [Native objects](native-objects.md) describes actual object support.
 - **C12 · Required:** retain source data, page content/code, notes, assets, generation parameters, template version, environment and necessary metadata. When content changes, synchronize chart cache/workbook, SVG fallback and current previews. Use relocatable project paths. A cached export or final PPTX alone is not a rebuildable project. See [project workspace](project-workspace.md).
-- **C13 · Recommended:** complete content, visual and implementation checks at the authorized review granularity. Even an authorized batch needs page checks. Multiple authors share a frozen brief/style; the coordinator checks cross-page progression, terminology and appearance. Revisions preserve premises, key steps, evidence associations and agreed content destinations across source, page and notes. Existing page-by-page authorization remains binding. See [page collaboration](page-collaboration.md).
+- **C13 · Required agreed execution, recommended organization:** follow the once-confirmed review/production/ImageGen choices and selected alternatives; do not silently replace a declined tool or Agent arrangement. Complete content, visual and implementation checks at the authorized granularity. Even an authorized batch needs page checks. Multiple authors share a frozen brief/style/content revision; the coordinator checks cross-page progression, terminology and appearance. Revisions preserve premises, key steps, evidence associations and content destinations across source, page, explanation PDF and notes. Apply the agreed post-revision review, using non-leading inputs and accurately distinguishing independent review from main-Agent self-check or skipped scope. Existing page-by-page authorization remains binding. See [execution and review](execution-and-review.md) and [page collaboration](page-collaboration.md).
 
 ## Verify, revise and deliver
 

references/visual-design.md

@@ -1,12 +1,22 @@
 # Page mockups and visual materials
 
-Reuse the user's settled template, theme, route and page workflow. Receive the current page's title/message, evidence, content groups and notes through [content handoff](content-handoff.md), then define its layout, asset roles and required native objects before generating its mockup. Establish a minimal page brief if none is supplied. Review only consequential decisions that remain open; do not restart settled outline or style choices. A request to review one page does not authorize a full-deck generation run.
+Reuse the user's settled template, theme, route and page workflow. Receive the current page's title/message, evidence, content groups and notes through [content handoff](content-handoff.md), then define its layout, asset roles and required native objects before generating its mockup. Establish a minimal page brief if none is supplied. Follow the confirmed [execution choices](execution-and-review.md), including ImageGen scope/budget and selected alternatives. Review only consequential decisions that remain open; do not restart settled outline, style or tool choices. A request to review one page does not authorize a full-deck generation run.
 
 When extracting style from an existing presentation or PDF, render representative pages and inspect the actual images. XML/object counts alone cannot establish density, hierarchy, ornament or spacing. Keep style references separate from strict source assets. Use existing accepted references; a rejected mockup does not remain a design baseline.
 
+## Rough layouts and confirmed preferences
+
+For page-by-page work with ImageGen enabled, use an actual visual or actual render from the selected template and theme as the reference. Inspect it before generation. Make a rough layout with the main content elements approximately in their intended regions, retaining the fixed page UI as a reference; focus on grouping, hierarchy, reading order and the contribution-to-evidence relationship. Do not spend the layout-draft budget on fine detail or claim pixel correspondence with the final PPT.
+
+Let the user review the current layout at the agreed granularity, incorporate feedback, then implement the authorized page. Later authorized pages reuse the confirmed ImageGen choice and budget; seeing each new layout is page review, not a repeated permission question. If ImageGen is declined or unavailable, use only the user's selected alternative or resolve that pending choice before dependent work. Do not silently switch to another generator, Agent arrangement or text-only plan.
+
+Record confirmed feedback in existing project/page notes or review material: the preference, user confirmation, applicable page/report scope and reference image/source revision. Reuse it within that scope on subsequent authorized pages. A local change does not become a global rule; an ongoing preference needs explicit support. Do not create another preference database or write global memory. Keep rejected drafts distinguishable from accepted references.
+
+The template/shared recipe owns final geometry, typography, fixed spacing and UI. Rough positions in the draft cannot override those contracts. Rebuild the actual page with supported native objects and check its reading order, capacity and visual evidence associations. Draft feedback does not establish final native rendering, editing or projection acceptance. Follow [review after revision](execution-and-review.md#review-after-revision) for the agreed independent check of substantive changes.
+
 ## Page composition and HTML boundary
 
-Choose text, figures, diagrams and their arrangement from the current information relationship. Pure text can serve a short question, quotation or conclusion; a picture or icon needs a useful role. Do not mechanically reuse website hero sections, selling cards or dashboards as report layouts. The page's main meaning must be readable without scrolling, hovering or clicking.
+Every title, text, formula, label, visualization and meaningful decorative group must serve the page task and, through it, the section and report goals. Choose their arrangement from the current information relationship. Pure text can serve a short question, quotation or conclusion; a picture or icon needs a useful role. Do not mechanically reuse website hero sections, selling cards or dashboards as report layouts. The page's main meaning must be readable without scrolling, hovering or clicking.
 
 Make conclusions and their supporting evidence visibly correspond through proximity, a shared heading, matching labels, annotations, highlighting or a necessary connector. Use only connections that express real relationships. Preserve exact premises and key reasoning/derivation steps where the audience needs them; check progression and information burden in the actual composition. Internal item counts, maintenance IDs and authoring decisions stay in process material unless the audience needs them for the report itself.
 
@@ -14,7 +24,7 @@ Do not use HTML/DOM/CSS to lay out report pages, including layouts later capture
 
 ## Mockup prompt inputs
 
-Use the host image-generation tool directly for requested raster page samples. Supply:
+For a requested raster page sample within the confirmed ImageGen scope, use the host image-generation tool directly. Supply:
 
 - The selected canvas/aspect ratio, template palette, typography intent, grid and fixed content regions.
 - The exact current-page text and moderate content density, with a declared hierarchy and clear content division.