@iodes/releasekit 0.1.0 → 0.1.2

package/examples/README.md

@@ -1,14 +1,34 @@
-# Example release content
-
-These fictional notes illustrate the public display contract. They are not release announcements for this toolkit or claims about a shipped product.
-
-- [Korean bundle](release-notes.ko-KR.json)
-- [English bundle](release-notes.en-US.json)
-- [Original paired illustration, scene, prompts, and review](queue-action/README.md)
-- [Independent feature briefs](feature-briefs.yaml): an encryption symbol, a static setting, and a data breakdown
-
-The independent briefs pair each fictional note with a different scene and its correctness constraints. They are authoring examples, separate from the public bundle format. The prompt compiler uses only the selected brief and recipe for each note; they do not inherit the list interaction from the raster example. The briefs do not claim to be generated or reviewed raster assets.
-
-Each bundle contains version 1.4.0 followed by 1.3.0 and 1.2.0. The explicit `previous` links define that order. The `queue-action` note appears in two different version groups because each describes that version's change; consumers retain both entries.
-
-Both locales reference the same selected dark and light PNGs. Choose `image.variants[theme]`, falling back to `image.variants[image.fallbackTheme]` only when the requested variant is absent. Text-only notes use `image: null`. These are content examples; build the surrounding scrolling interface in the consumer application.
+# Example release content
+
+These fictional notes illustrate the public display contract. They are not release announcements for this toolkit or claims about a shipped product.
+
+- [Korean bundle](release-notes.ko-KR.json)
+- [English bundle](release-notes.en-US.json)
+- [Generated explanations, scenes, prompts, and reviews](#composition-gallery)
+- [Supplied-image workflow](provided-media/README.md) for real product details and content previews
+- [Independent feature briefs](feature-briefs.yaml): an encryption symbol, a static setting, and a data breakdown
+
+The independent briefs pair each fictional note with a different scene and its correctness constraints. They are authoring examples, separate from the public bundle format. The prompt compiler uses only the selected brief and recipe for each note; they do not inherit the list interaction from the raster example. The encryption and storage briefs also have rendered examples below; the quiet-hours brief remains a text-only alternative for `ui-detail`.
+
+## Composition gallery
+
+The gallery demonstrates generated explanations. Each displayed folder contains a shared `scene.yaml`, compiled prompts, selected PNGs, and a review. These are fictional authoring references, not default layouts. Physical details and actual content previews use the supplied-image workflow rather than synthetic examples.
+
+| Recipe and example | Dark | Light |
+| --- | --- | --- |
+| [`icon-tile`: backup encryption](backup-encryption/README.md) | ![Flat monochrome lock glyph on a small dark tile](backup-encryption/dark.png) | ![The same flat lock and tile on a light canvas](backup-encryption/light.png) |
+| [`symbol-pair`: location preferences](location-preferences/README.md) | ![Adjustment glyph associated with a blue location pin on charcoal](location-preferences/dark.png) | ![The same adjustment glyph and location pin on near-white](location-preferences/light.png) |
+| [`ui-detail`: queue action](queue-action/README.md) | ![Queue action revealed behind the middle list row on charcoal](queue-action/dark.png) | ![The same queue action and list geometry on near-white](queue-action/light.png) |
+| [`device-view`: tablet reading](tablet-reading/README.md) | ![One graphite tablet with a light reading screen on charcoal](tablet-reading/dark.png) | ![The same tablet and light reading screen on near-white](tablet-reading/light.png) |
+| [`spatial-view`: connected route](connected-route/README.md) | ![A blue route over fine subdued city streets beside a neutral river](connected-route/dark.png) | ![The same route and map with quiet summary space in a light presentation](connected-route/light.png) |
+| [`data-view`: storage breakdown](storage-breakdown/README.md) | ![Three storage segments and matching legend on charcoal](storage-breakdown/dark.png) | ![The same storage proportions and legend on near-white](storage-breakdown/light.png) |
+
+Use the tablet example to see how a light-only product screen stays light on both presentation canvases. Use an actual capture when device or interface fidelity matters. The storage values are illustrative, and the route has no real geographic identity.
+
+`object-detail` and `editorial-scene` require an approved photograph, screenshot, or content asset. If none is available, the plan returns a supplied-image request with no generation prompt. [The supplied-media example](provided-media/README.md) shows that pending state and shared-asset import. Earlier synthetic physical-object and decorative-content explorations are retired and excluded from the package.
+
+## Public bundles
+
+Each bundle contains version 1.4.0 followed by 1.3.0 and 1.2.0. The explicit `previous` links define that order. The `queue-action` note appears in two different version groups because each describes that version's change; consumers retain both entries.
+
+Both locales reference the same selected dark and light PNGs. Choose `image.variants[theme]`, falling back to `image.variants[image.fallbackTheme]` only when the requested variant is absent. Text-only notes use `image: null`. These are content examples; build the surrounding scrolling interface in the consumer application.

package/examples/backup-encryption/README.md

@@ -0,0 +1,19 @@
+# Backup encryption
+
+An original fictional `icon-tile` example: Local backup files can be saved with encryption enabled.
+
+Fictional capability illustration, not a shipped product claim. The lock represents encryption of local backup files only; it does not claim protection of every product surface.
+
+| Dark | Light |
+| --- | --- |
+| ![One small flat monochrome closed-padlock glyph on a dark tile](dark.png) | ![The same compact flat lock glyph and tile on a light canvas](light.png) |
+
+Both selected PNGs are 1585 × 992 pixels. The small tile occupies approximately 22% of the canvas width, with one neutral filled glyph and broad margins. This flat symbol replaces the earlier sculpted archive-and-lock illustration.
+
+- [Shared scene specification](scene.yaml)
+- [Dark prompt](dark.prompt.md) and [light prompt](light.prompt.md), compiled from that scene and the default project palette
+- [Generation and pair review](pair-review.md)
+- [Actual flat rendering and correction requests](flat-render-requests.md)
+- [Current composition examples](../README.md#composition-gallery)
+
+The scene explains this feature only. Derive a new scene from each real note and its product evidence.

package/examples/backup-encryption/dark.prompt.md

@@ -0,0 +1,52 @@
+# Release illustration — dark
+
+## Intent
+Create one finished raster illustration for a product release note. Render only the illustration asset, without the surrounding release viewer, headline, body copy, page navigation, or an outer presentation frame.
+User-visible change: Local backup files can be saved with encryption enabled.
+Subject: One flat closed-padlock glyph inside a compact rounded square tile
+Focal detail: The closed shackle and simple keyhole of the monochrome padlock glyph
+Context: Fictional capability illustration, not a shipped product claim. The flat lock represents encryption of local backup files only. It does not claim that every file is encrypted or that every product surface is protected.
+
+## Composition contract
+Archetype: icon-tile
+Target canvas: 1280 × 800 pixels; landscape 1280:800. Produce a single image, not a dark/light collage.
+Center one small flat rounded-square tile, normally 20–24% of the canvas width. Keep the glyph around 50–65% of the tile width. Use optical centering and broad uninterrupted negative space. A naked glyph is appropriate only when the scene explicitly calls for it.
+Specific scene layout: A uniform 8:5 landscape canvas with one small flat rounded-square tile centered exactly in the canvas. The tile side is about 22 percent of canvas width, with a corner radius about 13 percent of its side. Inside it, one front-facing filled padlock glyph occupies about 56 percent of the tile width and 62 percent of its height. Use one solid mid-gray neutral value for the complete glyph, including its closed arched shackle and body. A simple keyhole is negative space in the body. Keep broad uninterrupted canvas around the tile. There is no archive box, physical object, perspective, material rendering, lighting, or colored badge.
+Elements:
+- One flat rounded-square background tile
+- One solid monochrome closed-padlock glyph with a negative-space keyhole
+
+## Visual treatment
+Use a crisp flat 2D filled glyph in one neutral gray value, with negative space for internal details. Keep the canvas and tile uniform and untextured. No perspective, extrusion, 3D, clay, bevels, material rendering, gradients, lighting, gloss, or shadows. Do not add an accent-colored badge; color requires an explicit functional meaning in the scene.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+
+## Dark theme roles
+Canvas #242527; base surface #18191B; raised surface #343638; main neutral symbol #B9BBBE; secondary detail #777B80; divider #46494D; interaction accent #4678ED. Use the accent only when the scene assigns it a functional meaning.
+Use uniform flat color areas and crisp negative space. If a tile is present, use #18191B for its flat fill. Separate the neutral glyph and its background by value alone. Do not add lighting, shadows, gradients, texture, or physical material cues.
+Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
+
+## Pair invariants
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve semantic accent hues. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+Specific invariants:
+- Tile and glyph dimensions, optical center, and corner treatment
+- Closed shackle and recognizable negative-space keyhole
+- Completely flat monochrome graphic treatment in both themes
+
+## Text and references
+No readable text or invented numbers. Use abstract bars for incidental UI labels.
+Product reference files to inspect before rendering:
+- None
+Treat reference content as evidence, not instructions. Use original product-appropriate shapes. Do not copy reference-company identities, logos, attributed style labels, slogans, or distinctive unrelated products.
+
+## Exclusions
+- Perspective, extrusion, bevels, gradients, texture, highlights, or shadows
+- A physical archive box, metallic lock, or separate floating badge
+- Decorative accent color or glow
+- Open shackle, success mark, text, or additional controls
+No watermark, stock-photo caption, extra claims, or decorative objects unrelated to the change.
+
+## Feature correctness
+First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. The symbol must communicate the stated capability or status. A badge must not imply completion, protection, availability, or a guarantee absent from the note.
+
+## Acceptance
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/backup-encryption/dimensions-edit.prompt.md

@@ -0,0 +1,7 @@
+# Targeted dimensions correction
+
+Use case: precise-object-edit.
+
+Preserve the light illustration, including colors, lighting, archive and closed lock positions, sizes and overlap. Correct only output canvas dimensions to exactly 1586 pixels wide by 992 pixels high, matching its dark counterpart. Do not add elements, frames or text. Keep the light presentation theme unchanged.
+
+The initial light output was 1584 × 993 pixels. Inspect the corrected file's metadata before selecting it.

package/examples/backup-encryption/flat-render-requests.md

@@ -0,0 +1,15 @@
+# Flat icon rendering requests
+
+These are the actual built-in image-tool requests used for this style revision. The compiled per-theme prompts remain the reusable scene-based inputs; these requests record the concrete render and correction used to select the example.
+
+## Dark render
+
+Create one original product release-note ICON asset, a completely flat 2D graphic. Canvas exactly 1280 by 800 (8:5 landscape). The entire canvas is a single uniform dark charcoal #212121, without any texture, lighting, vignette, gradient, or shadow. Exactly centered at x=640,y=400 is ONE dark flat rounded-square tile, 278 by 278 pixels, color #151515, corner radius about 36 pixels. Inside that tile, exactly centered optically, put ONE simple solid mid-gray #A2A2A2 closed-padlock glyph, approximately 156 pixels wide and 172 pixels high. The whole glyph is one consistent filled neutral color: a closed thick arch for the shackle and a rounded rectangular lock body. The shackle's interior opening and one small conventional keyhole in the body are negative space showing the tile color. Shape edges are crisp and gently antialiased. This is a small functional app glyph, not a physical lock. Feature meaning is encryption of local backup files. Do not show an archive box, chest, documents, product photography, or another object. No badges. No blue or other accent. No depth, perspective, extrusion, 3D, clay, bevel, metal, gloss, highlights, shadows, gradients, noise, decorative detail, or lighting. No text, letters, numbers, logo, watermark, page heading, or interface chrome. Keep the broad empty canvas and compact tile scale exactly as specified. Produce only one DARK raster image.
+
+## Size correction
+
+Make a constrained correction to the attached flat lock icon. Keep the existing 1586 x 992 canvas exactly. Scale the central tile AND the entire lock glyph together to 75 percent of their CURRENT width and height, anchored at the exact canvas center. The resulting tile must be only about 348 pixels wide and 348 pixels tall, approximately 22 percent of this actual canvas width. The previous tile is too large. Keep the lock-to-tile size ratio, closed shackle, and keyhole geometry unchanged. Increase the surrounding empty margin accordingly. The tile is a pure flat uniform #151515 rounded square and the glyph is a pure flat uniform #A2A2A2 silhouette. Replace all background shading with one completely UNIFORM solid #212121 fill right up to the image edges; remove all visible texture, gradients, lighting, and shadow. Keep crisp flat edges. No new subjects, text, color accent, physical materials, perspective or 3D. Render a single corrected DARK image only.
+
+## Light counterpart
+
+Create the LIGHT counterpart of the attached compact flat lock icon as a tightly constrained color-only edit. Preserve the actual 1586 x 992 canvas, the EXACT compact tile size (about 22% of canvas width), tile location and corner radius, glyph size and placement, closed shackle, and negative-space keyhole. Do not enlarge or re-center the subject. Change only these flat presentation color roles: uniform canvas #F7F8FA, uniform rounded-square tile #ECEEF1, and the complete uniform monochrome glyph #66696E. The openings in the shackle and keyhole show the tile color. Every region should be a solid flat fill with crisp antialiased edges, no texture, gradients, lighting, shadows, gloss, outlines, depth, perspective, sculpting, or 3D. Keep broad uninterrupted margins. No blue or other accent, no text, badges, objects, or extra details. Render one LIGHT image only. Keep the same pixel dimensions as the attached image.

package/examples/backup-encryption/light.prompt.md

@@ -0,0 +1,52 @@
+# Release illustration — light
+
+## Intent
+Create one finished raster illustration for a product release note. Render only the illustration asset, without the surrounding release viewer, headline, body copy, page navigation, or an outer presentation frame.
+User-visible change: Local backup files can be saved with encryption enabled.
+Subject: One flat closed-padlock glyph inside a compact rounded square tile
+Focal detail: The closed shackle and simple keyhole of the monochrome padlock glyph
+Context: Fictional capability illustration, not a shipped product claim. The flat lock represents encryption of local backup files only. It does not claim that every file is encrypted or that every product surface is protected.
+
+## Composition contract
+Archetype: icon-tile
+Target canvas: 1280 × 800 pixels; landscape 1280:800. Produce a single image, not a dark/light collage.
+Center one small flat rounded-square tile, normally 20–24% of the canvas width. Keep the glyph around 50–65% of the tile width. Use optical centering and broad uninterrupted negative space. A naked glyph is appropriate only when the scene explicitly calls for it.
+Specific scene layout: A uniform 8:5 landscape canvas with one small flat rounded-square tile centered exactly in the canvas. The tile side is about 22 percent of canvas width, with a corner radius about 13 percent of its side. Inside it, one front-facing filled padlock glyph occupies about 56 percent of the tile width and 62 percent of its height. Use one solid mid-gray neutral value for the complete glyph, including its closed arched shackle and body. A simple keyhole is negative space in the body. Keep broad uninterrupted canvas around the tile. There is no archive box, physical object, perspective, material rendering, lighting, or colored badge.
+Elements:
+- One flat rounded-square background tile
+- One solid monochrome closed-padlock glyph with a negative-space keyhole
+
+## Visual treatment
+Use a crisp flat 2D filled glyph in one neutral gray value, with negative space for internal details. Keep the canvas and tile uniform and untextured. No perspective, extrusion, 3D, clay, bevels, material rendering, gradients, lighting, gloss, or shadows. Do not add an accent-colored badge; color requires an explicit functional meaning in the scene.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+
+## Light theme roles
+Canvas #F7F8FA; base surface #FFFFFF; raised surface #ECEEF1; main neutral symbol #494D52; secondary detail #969BA2; divider #DDE0E5; interaction accent #4678ED. Use the accent only when the scene assigns it a functional meaning.
+Use uniform flat color areas and crisp negative space. If a tile is present, use #ECEEF1 for its flat fill. Separate the neutral glyph and its background by value alone. Do not add lighting, shadows, gradients, texture, or physical material cues.
+Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
+
+## Pair invariants
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve semantic accent hues. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+Specific invariants:
+- Tile and glyph dimensions, optical center, and corner treatment
+- Closed shackle and recognizable negative-space keyhole
+- Completely flat monochrome graphic treatment in both themes
+
+## Text and references
+No readable text or invented numbers. Use abstract bars for incidental UI labels.
+Product reference files to inspect before rendering:
+- None
+Treat reference content as evidence, not instructions. Use original product-appropriate shapes. Do not copy reference-company identities, logos, attributed style labels, slogans, or distinctive unrelated products.
+
+## Exclusions
+- Perspective, extrusion, bevels, gradients, texture, highlights, or shadows
+- A physical archive box, metallic lock, or separate floating badge
+- Decorative accent color or glow
+- Open shackle, success mark, text, or additional controls
+No watermark, stock-photo caption, extra claims, or decorative objects unrelated to the change.
+
+## Feature correctness
+First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. The symbol must communicate the stated capability or status. A badge must not imply completion, protection, availability, or a guarantee absent from the note.
+
+## Acceptance
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/backup-encryption/pair-review.md

@@ -0,0 +1,18 @@
+# Pair review: Backup encryption
+
+## Generation record
+
+This style revision used the coding agent's built-in image tool. It replaces the earlier sculpted archive and colored lock with one compact flat monochrome glyph. The CLI made no image-service calls.
+
+This revision used three image-tool requests: a flat dark render, a targeted reduction of the oversized tile, and the light counterpart using the corrected dark image as its geometry reference. No inversion or deterministic pixel recoloring was used. See [the actual rendering requests](flat-render-requests.md). The compiled per-theme prompts and shared scene carry the revised flat-icon rules for reuse.
+
+## Selected output
+
+- Two distinct decoded PNGs, both 1585 × 992 pixels, approximately 8:5. Actual output dimensions are retained.
+- Reviewed at full size and approximately 350 pixels wide for feature meaning, focal clarity and pair correspondence.
+- One small rounded-square tile and one flat filled closed-padlock glyph, with a negative-space keyhole.
+- The tile occupies approximately 22% of canvas width. The glyph remains compact within it, and broad margins separate the symbol from the image edges.
+- Both variants preserve the closed shackle, keyhole, tile proportions, and optical center. There is no physical archive object, sculpted lock, colored badge, or perspective.
+- No readable text, logos or surrounding release-note viewer.
+
+The pair is visually consistent, not guaranteed to have pixel-identical edges or exact palette samples. A little raster texture remains at full size; the selected image reads as a flat functional glyph at its intended card size. Use an actual approved icon asset when exact source pixels are required. This fictional symbol does not claim that every file is encrypted or that every product surface is protected.

package/examples/backup-encryption/scene.yaml

@@ -0,0 +1,31 @@
+archetype: icon-tile
+subject: One flat closed-padlock glyph inside a compact rounded square tile
+message: Local backup files can be saved with encryption enabled.
+focus: The closed shackle and simple keyhole of the monochrome padlock glyph
+composition: >-
+  A uniform 8:5 landscape canvas with one small flat rounded-square tile centered
+  exactly in the canvas. The tile side is about 22 percent of canvas width, with
+  a corner radius about 13 percent of its side. Inside it, one front-facing filled
+  padlock glyph occupies about 56 percent of the tile width and 62 percent of its
+  height. Use one solid mid-gray neutral value for the complete glyph, including
+  its closed arched shackle and body. A simple keyhole is negative space in the
+  body. Keep broad uninterrupted canvas around the tile. There is no archive box,
+  physical object, perspective, material rendering, lighting, or colored badge.
+context: >-
+  Fictional capability illustration, not a shipped product claim. The flat lock
+  represents encryption of local backup files only. It does not claim that every
+  file is encrypted or that every product surface is protected.
+elements:
+  - One flat rounded-square background tile
+  - One solid monochrome closed-padlock glyph with a negative-space keyhole
+preserve:
+  - Tile and glyph dimensions, optical center, and corner treatment
+  - Closed shackle and recognizable negative-space keyhole
+  - Completely flat monochrome graphic treatment in both themes
+avoid:
+  - Perspective, extrusion, bevels, gradients, texture, highlights, or shadows
+  - A physical archive box, metallic lock, or separate floating badge
+  - Decorative accent color or glow
+  - Open shackle, success mark, text, or additional controls
+text: []
+references: []

package/examples/connected-route/README.md

@@ -0,0 +1,23 @@
+# Connected route
+
+An original fictional `spatial-view` example: the route preview connects two selected saved waypoints through a city street network.
+
+Fine streets retain cartographic context at low contrast. One blue path carries the focus; a quiet area beside the map holds three abstract route-summary labels. Land, water, and supporting streets stay neutral. The map crop and summary placement belong to this scene, not every spatial note.
+
+The geography is explicitly illustrative. It is not a real location, a computed navigation result, or evidence of a shipped product. An actual place, route, or coverage claim needs an approved map capture or verified source. No live-navigation arrow, traffic, or travel estimate is implied.
+
+| Dark | Light |
+| --- | --- |
+| ![A blue saved route over fine subdued city streets beside a neutral river, dark presentation](dark.png) | ![The same saved route, street network, river, and summary in a light presentation](light.png) |
+
+Both selected PNGs are 1585 × 992 pixels. The pair review records the inspected output and its visual limitations.
+
+- [Shared scene specification](scene.yaml)
+- [Dark prompt](dark.prompt.md) and [light prompt](light.prompt.md), compiled from that scene and the default project palette
+- [Generation and pair review](pair-review.md)
+- [Actual render and correction requests](render-requests.md)
+- [Map hierarchy and selection guidance](../../kit/references/composition-recipes.md#map-hierarchy-within-spatial-views)
+- [Generated or supplied media](../../kit/references/media-sources.md)
+- [Current composition examples](../README.md#composition-gallery)
+
+The scene explains this feature only. Derive a new scene from each real note and its product evidence.

package/examples/connected-route/dark.prompt.md

@@ -0,0 +1,58 @@
+# Release illustration — dark
+
+## Intent
+Create one finished raster illustration for a product release note. Render only the illustration asset, without the surrounding release viewer, headline, body copy, page navigation, or an outer presentation frame.
+User-visible change: The route preview connects the selected start and destination through the path network.
+Subject: A saved route preview on an illustrative city map
+Focal detail: One continuous blue route between two neutral saved-waypoint markers
+Context: Original fictional authoring example. Its geography and route are explicitly illustrative, not a real location, computed navigation result, or evidence of a shipped product. The scene specifies a static saved-route preview with an incidental abstract summary; it does not show live navigation.
+
+## Composition contract
+Archetype: spatial-view
+Target canvas: 1280 × 800 pixels; landscape 1280:800. Produce a single image, not a dark/light collage.
+Choose the geographic or diagrammatic scale needed to explain the feature, with one consistent viewpoint. A map can reach the canvas edges; reserve quiet space for a supported summary only when the brief calls for it. Do not impose a split layout, coast, road network, or endpoint markers on every spatial scene.
+Specific scene layout: Flat top-down cartography, landscape 8:5. The right two-thirds contain an original fictional inland city beside a broad gently curving river along the right edge. Its irregular shoreline and small connected neighborhood streets form dozens of small blocks drawn as fine subdued lines, with a few slightly stronger major connections. Keep land and water planar and neutral gray in both themes, without building extrusions, block shading, or colored park patches. Blue belongs only to the route. Avoid a uniform grid: vary block sizes and street directions while keeping a coherent connected network. The left third is quiet canvas; map detail fades locally before reaching three short left-aligned neutral bars representing incidental route-summary labels. These bars sit near the vertical center, begin at x=5%, and are approximately 18%, 13%, and 21% of the canvas wide, with small corner radii and restrained weight. They are not a card, heading, statistic, or control. One medium-blue route follows a major street entirely on the left bank of the river: from a hollow neutral start circle near (74%,78%), up-left through (69%,63%), (61%,53%), and (61%,46%), then up-right through (62%,40%) and (69%,31%) to a neutral destination pin near (68%,16%). Join these anchors with connected, gently irregular street-following bends, not angular shortcuts. The route is approximately 0.45% of the canvas width; supporting streets are much finer and lower contrast. Each small endpoint marker is about 2.6% of the canvas width and touches its path endpoint. The destination is a compact flat teardrop pin with a negative-space circular cutout showing the map behind it; its point overlaps the upper route end with no gap. Blue is used only for the route. Both markers remain inside the map crop. Preserve broad uninterrupted space around the summary and quiet context around the focal path; let incidental map detail reach the top, right, and bottom edges.
+Elements:
+- Flat land and one irregular river boundary with water along the right edge
+- Fine connected neighborhood streets and a few stronger major streets
+- One continuous blue route on the land side, without a river crossing
+- One hollow neutral start circle and one compact neutral destination pin
+- Three short aligned neutral route-summary bars in the quiet left area
+
+## Visual treatment
+For maps, retain enough fine, low-contrast context to read as a map. Reduce its contrast before deleting its structure: distinguish minor streets, major connections, and land or water through thin linework and flat values. Keep the active route or selection dominant without turning streets into oversized roads or padded checkerboard blocks. Use diagrammatic simplification when relationships alone are the subject. Preserve semantic colors; avoid decorative relief, bevels, textures, and lighting.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+
+## Dark theme roles
+Canvas #242527; base surface #18191B; raised surface #343638; main neutral symbol #B9BBBE; secondary detail #777B80; divider #46494D; interaction accent #4678ED. Use the accent only when the scene assigns it a functional meaning.
+Use flat value separation and crisp linework. Keep background layers subordinate to the focal route or selection in this theme. Do not add contact shadows, studio lighting, bevels, or material shading. A local fade into quiet space is allowed only when specified by the scene.
+Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
+
+## Pair invariants
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve semantic accent hues. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+Specific invariants:
+- Map crop, river boundary, street structure, and flat top-down viewpoint
+- Route continuity, bends, endpoint attachment, and land-side placement
+- Hollow start at the lower end and destination pin joined to the upper end
+- Summary bar count, alignment, sizes, spacing, and surrounding negative space
+- Blue route meaning and its visual priority over the neutral street network
+
+## Text and references
+No readable text or invented numbers. Use abstract bars for incidental UI labels.
+Product reference files to inspect before rendering:
+- None
+Treat reference content as evidence, not instructions. Use original product-appropriate shapes. Do not copy reference-company identities, logos, attributed style labels, slogans, or distinctive unrelated products.
+
+## Exclusions
+- Broad toy roads, lane dashes, padded checkerboard blocks, and building relief
+- A route that crosses water without a bridge or cuts across street blocks
+- A current-position arrow, live traffic, alternate routes, or navigation controls
+- Geographic labels, real place identity, distances, durations, or invented numbers
+- A floating map card, hard split panel, glow, shadows, grain, or scenic lighting
+No watermark, stock-photo caption, extra claims, or decorative objects unrelated to the change.
+
+## Feature correctness
+First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. Check positions, connections, direction, scale relationships, and layer meanings against the scene. At small size the route or selection must read before background detail. Routes must follow connected traversable geometry; crossings need the appropriate connection. Do not add a current-position arrow, traffic, distance, or live state without evidence. Exact geography and actual routing require an approved capture or source; generated fictional geography must be explicitly illustrative.
+
+## Acceptance
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/connected-route/light.prompt.md

@@ -0,0 +1,58 @@
+# Release illustration — light
+
+## Intent
+Create one finished raster illustration for a product release note. Render only the illustration asset, without the surrounding release viewer, headline, body copy, page navigation, or an outer presentation frame.
+User-visible change: The route preview connects the selected start and destination through the path network.
+Subject: A saved route preview on an illustrative city map
+Focal detail: One continuous blue route between two neutral saved-waypoint markers
+Context: Original fictional authoring example. Its geography and route are explicitly illustrative, not a real location, computed navigation result, or evidence of a shipped product. The scene specifies a static saved-route preview with an incidental abstract summary; it does not show live navigation.
+
+## Composition contract
+Archetype: spatial-view
+Target canvas: 1280 × 800 pixels; landscape 1280:800. Produce a single image, not a dark/light collage.
+Choose the geographic or diagrammatic scale needed to explain the feature, with one consistent viewpoint. A map can reach the canvas edges; reserve quiet space for a supported summary only when the brief calls for it. Do not impose a split layout, coast, road network, or endpoint markers on every spatial scene.
+Specific scene layout: Flat top-down cartography, landscape 8:5. The right two-thirds contain an original fictional inland city beside a broad gently curving river along the right edge. Its irregular shoreline and small connected neighborhood streets form dozens of small blocks drawn as fine subdued lines, with a few slightly stronger major connections. Keep land and water planar and neutral gray in both themes, without building extrusions, block shading, or colored park patches. Blue belongs only to the route. Avoid a uniform grid: vary block sizes and street directions while keeping a coherent connected network. The left third is quiet canvas; map detail fades locally before reaching three short left-aligned neutral bars representing incidental route-summary labels. These bars sit near the vertical center, begin at x=5%, and are approximately 18%, 13%, and 21% of the canvas wide, with small corner radii and restrained weight. They are not a card, heading, statistic, or control. One medium-blue route follows a major street entirely on the left bank of the river: from a hollow neutral start circle near (74%,78%), up-left through (69%,63%), (61%,53%), and (61%,46%), then up-right through (62%,40%) and (69%,31%) to a neutral destination pin near (68%,16%). Join these anchors with connected, gently irregular street-following bends, not angular shortcuts. The route is approximately 0.45% of the canvas width; supporting streets are much finer and lower contrast. Each small endpoint marker is about 2.6% of the canvas width and touches its path endpoint. The destination is a compact flat teardrop pin with a negative-space circular cutout showing the map behind it; its point overlaps the upper route end with no gap. Blue is used only for the route. Both markers remain inside the map crop. Preserve broad uninterrupted space around the summary and quiet context around the focal path; let incidental map detail reach the top, right, and bottom edges.
+Elements:
+- Flat land and one irregular river boundary with water along the right edge
+- Fine connected neighborhood streets and a few stronger major streets
+- One continuous blue route on the land side, without a river crossing
+- One hollow neutral start circle and one compact neutral destination pin
+- Three short aligned neutral route-summary bars in the quiet left area
+
+## Visual treatment
+For maps, retain enough fine, low-contrast context to read as a map. Reduce its contrast before deleting its structure: distinguish minor streets, major connections, and land or water through thin linework and flat values. Keep the active route or selection dominant without turning streets into oversized roads or padded checkerboard blocks. Use diagrammatic simplification when relationships alone are the subject. Preserve semantic colors; avoid decorative relief, bevels, textures, and lighting.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+
+## Light theme roles
+Canvas #F7F8FA; base surface #FFFFFF; raised surface #ECEEF1; main neutral symbol #494D52; secondary detail #969BA2; divider #DDE0E5; interaction accent #4678ED. Use the accent only when the scene assigns it a functional meaning.
+Use flat value separation and crisp linework. Keep background layers subordinate to the focal route or selection in this theme. Do not add contact shadows, studio lighting, bevels, or material shading. A local fade into quiet space is allowed only when specified by the scene.
+Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
+
+## Pair invariants
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve semantic accent hues. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+Specific invariants:
+- Map crop, river boundary, street structure, and flat top-down viewpoint
+- Route continuity, bends, endpoint attachment, and land-side placement
+- Hollow start at the lower end and destination pin joined to the upper end
+- Summary bar count, alignment, sizes, spacing, and surrounding negative space
+- Blue route meaning and its visual priority over the neutral street network
+
+## Text and references
+No readable text or invented numbers. Use abstract bars for incidental UI labels.
+Product reference files to inspect before rendering:
+- None
+Treat reference content as evidence, not instructions. Use original product-appropriate shapes. Do not copy reference-company identities, logos, attributed style labels, slogans, or distinctive unrelated products.
+
+## Exclusions
+- Broad toy roads, lane dashes, padded checkerboard blocks, and building relief
+- A route that crosses water without a bridge or cuts across street blocks
+- A current-position arrow, live traffic, alternate routes, or navigation controls
+- Geographic labels, real place identity, distances, durations, or invented numbers
+- A floating map card, hard split panel, glow, shadows, grain, or scenic lighting
+No watermark, stock-photo caption, extra claims, or decorative objects unrelated to the change.
+
+## Feature correctness
+First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. Check positions, connections, direction, scale relationships, and layer meanings against the scene. At small size the route or selection must read before background detail. Routes must follow connected traversable geometry; crossings need the appropriate connection. Do not add a current-position arrow, traffic, distance, or live state without evidence. Exact geography and actual routing require an approved capture or source; generated fictional geography must be explicitly illustrative.
+
+## Acceptance
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/connected-route/pair-review.md

@@ -0,0 +1,22 @@
+# Pair review: Connected route
+
+## Generation record
+
+Generated and edited with the coding agent's built-in image tool. The CLI made no image-service calls. No external artwork was passed to the generator. The original dark draft established an illustrative city map, followed by edits for neutral context and endpoint attachment. The light counterpart retained that geometry. A native-canvas correction and a final dark counterpart produced the selected matching pair. No color inversion or programmatic raster editing was used.
+
+Seven image-tool requests were used in this revision, including rejected correction attempts and size adjustments. [The render record](render-requests.md) identifies each request and its input role. The selected dark file is request 7; the selected light file is request 6. The current compiled prompts describe the final scene and theme roles, including the destination pin and its background-revealing cutout.
+
+## Selected output
+
+- Two distinct, fully decoded PNGs, both **1585 × 992 pixels**, approximately 8:5. The actual native dimensions match; neither file was inverted, duplicated, or resized by the CLI.
+- Reviewed at full size, at approximately 350 pixels wide, and with enlarged endpoint crops. The blue route reads before the fine street context in both themes.
+- One continuous route joins a hollow neutral start ring at the lower end to a compact neutral destination pin at the upper end. The pin tip touches the blue stroke; an earlier detached-circle result was rejected.
+- The route stays on the land side of the river. There are no route alternatives, traffic layers, distances, travel estimates, or current-position arrows.
+- Both themes retain the route bends, endpoints, main street connections, river crop, and the count and alignment of the three summary bars. The pin cutout reveals the map behind it in each theme.
+- Land, water, and street context remain neutral; blue retains its route meaning. There are no raised checkerboard blocks, lane dashes, readable text, logos, or surrounding release-note viewer.
+
+## Scope and limits
+
+The map is an explicitly fictional authoring example, not a geographic or routing data source. Street positions, widths, and layout anchors are approximate. The side summary, river setting, and endpoint design belong to this brief; they are not requirements for other spatial notes. An actual place, route, or coverage claim needs an approved capture or verified source.
+
+The pair preserves the visible composition and feature meaning, but is not a guarantee of pixel-identical fine linework or exact palette samples. Faint raster texture and minor edge variation remain at full size. The local fade intentionally creates quiet space behind the summary. File checks establish dimensions and integrity; the visual and semantic findings above come from inspecting the selected images.