Preserve approved mockups with controlled adjustments and recolorable assets (0.9.4)

references/native-authoring.md

@@ -6,13 +6,13 @@ Create or continue the [mandatory buildable Skill project](project-workspace.md)
 
 Start the current page from its selected layout source. Retain inheritance metadata, inherited objects and placeholder indices. Fill the declared placeholder carrier; put independent content objects in the intended slide layer. Do not paint opaque slide-local copies over the master logo or layout watermarks. When a template supplies a custom composition generator, inspect it and use its declared content interface rather than approximating its source geometry.
 
-Use the template's discrete typography, grid, fixed content region and spacing. Resolve overflow by choosing a suitable layout, or by shortening content/dividing the page within the user's authorized content scope. For an approved mockup, preserve its content, graphics and relationship-bearing shapes under [mockup fidelity](visual-design.md#approved-mockup-fidelity); necessary quality repair does not permit silently dropping elements. Do not infer ad hoc font sizes and alignment guides from mockup pixels. Keep text as text, simple panels and connectors as geometry, and exact image exceptions as independent assets. Tables, charts and formulas must retain their required native object type; a collection of lines/text or a formula picture does not automatically qualify.
+Start with the template's typography, grid, fixed content region and spacing. For an approved mockup, use [controlled content-area adjustments](visual-design.md#controlled-adjustments-for-approved-mockups) to font sizes, bounds, spacing and necessary fit/alignment, with declared shared project values in integer/fixed-step units. Preserve fixed UI, locked structures, accepted relative positions, visualization forms, icons and text styling under [mockup fidelity](visual-design.md#approved-mockup-fidelity). Resolve remaining overflow through reflow or an authorized layout/content change; necessary quality repair does not permit silently dropping or redesigning elements. Do not trace raster artifacts or introduce unexplained multi-digit offsets. Keep text as text, simple panels and connectors as geometry, and exact image exceptions as independent assets. For an element that native components/SVG cannot conveniently reproduce faithfully, use [ImageGen](visual-design.md#elements-that-need-imagegen) and disclose its independent picture type. Tables, charts and formulas must retain any explicitly required native object type; a collection of lines/text or a formula picture does not automatically qualify.
 
 Apply [text and container rules](text-and-containers.md) before authoring: prefer one native frame per paragraph, use a unified logical block for any necessary fragments, distinguish text functions by size/weight/color and instantiate repeated containers through a shared renderer. Inspect actual native paragraph structure after export; positional SVG spans can otherwise be split by the compiler.
 
 Before emitting paragraph rows, check punctuation at both line edges and prohibit every singleton row, including one character surrounded by punctuation. Reflow the complete paragraph with measured text widths; keep derived rows inside the same native frame. Repeat the check against actual rendered lines if PowerPoint performs further wrapping.
 
-Keep separate paragraphs separated by the template's fixed paragraph gap, retaining their normal internal line height. Spacing values and applicable relationships belong to the shared recipe; content callers cannot adjust them. Check exact fixed padding/gaps and actual glyph/edge clearance at normal scale. Use [text-block/spacing helpers](text-and-containers.md#spacing-and-paragraph-separation) for supported content. Explicit math markers use the [Office Math wrapper](mathematics.md), not the upstream table/chart marker kinds.
+Keep separate paragraphs separated by the active shared recipe's fixed paragraph gap, retaining their normal internal line height. Use template defaults or the declared project adjustment above. Spacing values and applicable relationships belong to the shared recipe; content callers cannot adjust them. Check exact fixed padding/gaps and actual glyph/edge clearance at normal scale. Use [text-block/spacing helpers](text-and-containers.md#spacing-and-paragraph-separation) for supported content. Explicit math markers use the [Office Math wrapper](mathematics.md), not the upstream table/chart marker kinds.
 
 ## Current-page project build
 
@@ -36,6 +36,8 @@ The exporter embeds images in temporary source copies, preserving canonical sour
 
 Before marking each page complete, perform the [full-page hierarchy check](visual-design.md#full-page-hierarchy-check) on its current render, covering font sizes/families/weights, spacing and visual content groups across the entire page. Compare with any approved sample, repair the source and rebuild/reinspect as needed; a successful compile is not this visual check.
 
+After any approved-mockup typography or geometry adjustment, also check [container and page overflow](visual-design.md#controlled-adjustments-for-approved-mockups): actual text/formula extents and paragraph height must fit their frames/containers, and complete visible groups must fit the usable page/canvas without unintended clipping, occlusion or collisions with fixed UI. Check the actual rebuilt render, repair source and repeat for affected shared instances.
+
 ## Template authors and review prototypes
 
 Keep proposed styles and mockups outside the final template workspace until the user's design review allows formal construction. A proposal manifest cannot be consumed as a released production template. After approval, author the common style, independent themes, roster and native SVG layout definitions together; compare each theme against the same geometry and slot contract.