@iodes/releasekit 0.1.6 → 0.2.0

package/dist/status.js

@@ -0,0 +1,52 @@
+import { Project } from './project.js';
+import { exists } from './files.js';
+import { refKey } from './refs.js';
+import { validate } from './validate.js';
+export async function listReleases(project, channel) {
+    await project.config();
+    if (channel !== undefined)
+        await project.requireChannel(channel);
+    const refs = (await project.allRefs()).filter(value => channel === undefined || value.channel === channel);
+    return Promise.all(refs.map(async (value) => {
+        const release = await project.release(value);
+        return { ...value, status: release.status, releasedAt: release.releasedAt, notes: release.notes.length, locales: release.locales };
+    }));
+}
+export async function projectStatus(project, selected, channel) {
+    if (!(await exists(await project.content('config.yaml')))) {
+        return { initialized: false, releases: [], next: ['releasekit init'] };
+    }
+    const config = await project.config();
+    const releases = selected ? [await project.release(selected)] : await listReleases(project, channel);
+    const results = await Promise.all(releases.map(async (release) => {
+        const validation = await validate(project, release);
+        const identity = refKey(release);
+        const args = `${release.version}${release.channel === undefined ? '' : ` --channel ${release.channel}`}`;
+        let next;
+        if (!validation.valid)
+            next = `Use releasekit-draft or releasekit-image for ${identity} to resolve the reported issues, then run releasekit validate ${args}.`;
+        else if (release.status === 'ready')
+            next = `releasekit export --current ${args} --out <new-directory>`;
+        else {
+            const predecessors = (await project.history(release)).slice(1).filter(item => item.status !== 'ready');
+            next = release.channel === undefined && predecessors.length
+                ? `Finalize earlier releases first: ${predecessors.reverse().map(refKey).join(', ')}.`
+                : `releasekit finalize ${args}`;
+        }
+        return { version: release.version, ...(release.channel === undefined ? {} : { channel: release.channel }), status: release.status,
+            notes: typeof release.notes === 'number' ? release.notes : release.notes.length,
+            valid: validation.valid, errors: validation.errors, warnings: validation.warnings, next };
+    }));
+    return { initialized: true, product: config.product, releases: results,
+        next: results.length ? [] : ['Use releasekit-draft with a version to select the Git range and write the first draft.'] };
+}
+export function formatStatus(result) {
+    const lines = [result.initialized ? `${result.product} — release status` : 'ReleaseKit is not initialized.'];
+    for (const release of result.releases) {
+        lines.push(`\n${refKey(release)}  ${release.status}  ${release.notes} notes  ${release.valid ? 'validation passed' : 'needs attention'}`);
+        lines.push(...release.errors.map(error => `  - ${error}`), ...release.warnings.map(warning => `  Warning: ${warning}`));
+        lines.push(`  Next: ${release.next}`);
+    }
+    lines.push(...result.next.map(next => `Next: ${next}`));
+    return lines.join('\n');
+}

package/dist/validate.d.ts

@@ -1,12 +1,15 @@
+import { type ReleaseId } from './model.js';
 import { type Release } from './model.js';
 import { Project } from './project.js';
 export interface Validation {
     version: string;
+    channel?: string;
     valid: boolean;
     errors: string[];
     warnings: string[];
     contentHash: string | null;
 }
 export declare function contentHash(project: Project, release: Release): Promise<string>;
-export declare function validate(project: Project, version: string): Promise<Validation>;
-export declare function finalize(project: Project, version: string): Promise<Validation>;
+export declare function validate(project: Project, version: ReleaseId): Promise<Validation>;
+export declare function validateMany(project: Project, versions: ReleaseId[]): Promise<Validation[]>;
+export declare function finalize(project: Project, version: ReleaseId): Promise<Validation>;

package/dist/validate.js

@@ -1,27 +1,47 @@
+import {} from './model.js';
+import { ref, refKey } from './refs.js';
 import { imageSource } from './model.js';
 import { Project, editable } from './project.js';
 import { canonical, digest, readNote, noteHash, identifier } from './files.js';
 import { readVisual, checkReferenceFiles } from './content.js';
 import { validateImages } from './images.js';
-import { checkPrevious, collect, collectSnapshot } from './git.js';
+import { collect, collectSnapshot } from './git.js';
 export async function contentHash(project, release) {
     const { status: _status, contentHash: _hash, ...metadata } = release;
     const parts = [metadata];
     for (const note of release.notes) {
         for (const language of release.locales)
-            parts.push(await readNote(await project.releaseFile(release.version, `notes/${note.id}/${language}.md`)));
+            parts.push(await readNote(await project.releaseFile(release, `notes/${note.id}/${language}.md`)));
         if (note.image)
-            parts.push(await readVisual(project, release.version, note.id));
+            parts.push(await readVisual(project, release, note.id));
     }
     return digest(canonical(parts));
 }
 export async function validate(project, version) {
+    return validateOne(project, version);
+}
+// Reuse structural validation within an export or move, without caching across mutations.
+export async function validateMany(project, versions) {
+    const checkedHistory = new Set();
+    if (versions.some(v => ref(v).channel !== undefined)) {
+        for (const release of await project.channelHistory())
+            checkedHistory.add(refKey(release));
+    }
+    for (const version of versions) {
+        if (!checkedHistory.has(refKey(version))) {
+            for (const release of await project.history(version))
+                checkedHistory.add(refKey(release));
+        }
+    }
+    return Promise.all(versions.map(version => validateOne(project, version, checkedHistory)));
+}
+async function validateOne(project, version, checkedHistory) {
     const errors = [], warnings = [];
     let hash = null;
     try {
         const release = await project.release(version);
-        if (release.initialContent && (release.source.fromSha !== null || release.source.fromRef !== null || release.previous !== null)) {
-            errors.push('Initial content requires a root baseline with no previous release.');
+        if (release.initialContent && (release.source.fromSha !== null || release.source.fromRef !== null)) {
+            errors.push('Initial content requires a root baseline Git range.');
         }
         // Summaries inspect only the baseline snapshot; ready releases use their finalized fingerprint.
         const summary = release.initialContent === 'summary';
@@ -74,19 +94,13 @@ export async function validate(project, version) {
             }
         }
         try {
-            await project.history(version, 1);
+            if (!checkedHistory?.has(refKey(version)))
+                await project.history(version, 1);
         }
         catch (error) {
             errors.push(error instanceof Error ? error.message : String(error));
         }
-        if (release.status === 'draft' && release.previous) {
-            try {
-                checkPrevious(project.root, await project.release(release.previous), release.source);
-            }
-            catch (error) {
-                errors.push(error instanceof Error ? error.message : String(error));
-            }
-        }
+        // Git scope was pinned independently; display links can change during moves.
         if (!errors.length)
             hash = await contentHash(project, release);
         if (release.status === 'ready' && release.contentHash !== hash && !errors.length)
@@ -95,7 +109,7 @@ export async function validate(project, version) {
     catch (error) {
         errors.push(error instanceof Error ? error.message : String(error));
     }
-    return { version, valid: errors.length === 0, errors, warnings, contentHash: hash };
+    return { ...ref(version), valid: errors.length === 0, errors, warnings, contentHash: hash };
 }
 export async function finalize(project, version) {
     const release = await project.release(version);
@@ -103,8 +117,8 @@ export async function finalize(project, version) {
     const result = await validate(project, version);
     if (!result.valid || !result.contentHash)
         throw new Error(result.errors.join('\n'));
-    const chain = await project.history(version, 100);
-    if (chain.slice(1).some(r => r.status !== 'ready'))
+    const chain = await project.history(version);
+    if (release.channel === undefined && chain.slice(1).some(r => r.status !== 'ready'))
         throw new Error('Finalize the previous releases before finalizing this release.');
     release.status = 'ready';
     release.contentHash = result.contentHash;

package/examples/README.md

@@ -17,15 +17,15 @@ The gallery demonstrates generated explanations. Each displayed folder contains
 | 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) | ![Neutral adjustment glyph associated with a neutral location pin on charcoal](location-preferences/dark-neutral.png) | ![The same neutral symbol pair on near-white](location-preferences/light-soft.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-soft.png) |
+| [`symbol-pair`: location preferences](location-preferences/README.md) | ![Neutral adjustment glyph associated with a neutral location pin on charcoal](location-preferences/dark-refined.png) | ![The same neutral symbol pair on near-white](location-preferences/light-refined.png) |
+| [`ui-detail`: queue action](queue-action/README.md) | ![Queue action revealed behind the middle list row on charcoal](queue-action/dark-accent.png) | ![The same queue action and list geometry on near-white](queue-action/light-accent.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) |
 
-The location pair and queue interaction include light variants reviewed against the current [neutral role palette](../kit/references/visual-language.md#assign-neutral-colors-by-role). Other examples retain the palettes recorded for their generation; use the saved project policy when creating new images instead of copying colors from an older PNG.
+The location pair and queue interaction demonstrate the current [independent theme treatments](../kit/references/theme-pairing.md#one-scene-two-presentation-treatments): compact balanced glyphs and quiet charcoal hierarchy in dark, with soft neutral values in light. Their reviewed originals and exact edit requests are linked from each example. All active scene prompts are compiled with current guidance; other raster examples retain their recorded treatments. Use the saved project policy when creating new images instead of copying colors from an older PNG.
 
-The location pair uses no accent: equal neutral treatment explains a static association. The route uses color to distinguish its path from the surrounding map.
+The location pair uses no accent: balanced neutral symbols explain a static association. The queue example uses the project accent on its primary action so readers can find the available operation quickly, while rows, thumbnails, and incidental bars stay neutral. The route uses color to distinguish its path from the surrounding map. Functional color can guide attention even when the scene remains understandable in grayscale.
 
 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.
 

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

@@ -17,16 +17,25 @@ Elements:
 - 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.
+Use a crisp flat 2D filled glyph 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. Generic capability and maintenance symbols normally use a neutral gray. When the scene depicts a specific action or state, its relevant glyph or component may use the project accent to direct attention. A newly announced capability alone does not imply an active state; do not invent a badge or status.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. 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.
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #242527 | Uniform illustration background |
+| surface | #18191B | Base or recessed interface panels |
+| raised | #343638 | Foreground panels, controls, and quiet tile fills |
+| primary | #B9BBBE | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #777B80 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #46494D | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Preserve this theme's independent charcoal hierarchy: canvas #242527, base surface #18191B, foreground surface #343638, primary #B9BBBE, and secondary #777B80. Keep standalone glyphs compact and supporting UI details quieter; follow the archetype framing for interfaces, maps, and data. Do not enlarge, thicken, or brighten every glyph and label bar. Retain the necessary separation between background, panels, and focal controls instead of compressing all dark values to match a softened light variant. Respect explicit project palette overrides.
+Use uniform flat color areas and crisp negative space. If a tile is present, use #18191B for its flat fill. Keep the glyph distinct from its background by value contrast, including when it uses a functional accent. 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.
+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 neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. 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
@@ -49,4 +58,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 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.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. 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/light.prompt.md

@@ -17,16 +17,25 @@ Elements:
 - 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.
+Use a crisp flat 2D filled glyph 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. Generic capability and maintenance symbols normally use a neutral gray. When the scene depicts a specific action or state, its relevant glyph or component may use the project accent to direct attention. A newly announced capability alone does not imply an active state; do not invent a badge or status.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. 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.
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #F8F8F8 | Uniform illustration background |
+| surface | #FFFFFF | Base or recessed interface panels |
+| raised | #ECECEC | Foreground panels, controls, and quiet tile fills |
+| primary | #999999 | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #B8B8B8 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #D9D9D9 | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Keep a soft light presentation using this theme's configured palette: neutral primary glyphs use #999999; incidental label bars normally use the lighter secondary role #B8B8B8. Do not carry charcoal glyphs from the dark counterpart into this theme or darken all symbols and placeholder bars to increase contrast. Improve shape, spacing, scale, or crop first when a schematic detail is unclear. Respect explicit project palette overrides.
+Use uniform flat color areas and crisp negative space. If a tile is present, use #ECECEC for its flat fill. Keep the glyph distinct from its background by value contrast, including when it uses a functional accent. 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.
+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 neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. 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
@@ -49,4 +58,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 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.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. 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/dark.prompt.md

@@ -21,15 +21,24 @@ Elements:
 
 ## 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.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. 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.
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #242527 | Uniform illustration background |
+| surface | #18191B | Base or recessed interface panels |
+| raised | #343638 | Foreground panels, controls, and quiet tile fills |
+| primary | #B9BBBE | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #777B80 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #46494D | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Preserve this theme's independent charcoal hierarchy: canvas #242527, base surface #18191B, foreground surface #343638, primary #B9BBBE, and secondary #777B80. Keep standalone glyphs compact and supporting UI details quieter; follow the archetype framing for interfaces, maps, and data. Do not enlarge, thicken, or brighten every glyph and label bar. Retain the necessary separation between background, panels, and focal controls instead of compressing all dark values to match a softened light variant. Respect explicit project palette overrides.
 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.
+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 neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. 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
@@ -55,4 +64,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 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.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. 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

@@ -21,15 +21,24 @@ Elements:
 
 ## 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.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. 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.
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #F8F8F8 | Uniform illustration background |
+| surface | #FFFFFF | Base or recessed interface panels |
+| raised | #ECECEC | Foreground panels, controls, and quiet tile fills |
+| primary | #999999 | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #B8B8B8 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #D9D9D9 | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Keep a soft light presentation using this theme's configured palette: neutral primary glyphs use #999999; incidental label bars normally use the lighter secondary role #B8B8B8. Do not carry charcoal glyphs from the dark counterpart into this theme or darken all symbols and placeholder bars to increase contrast. Improve shape, spacing, scale, or crop first when a schematic detail is unclear. Respect explicit project palette overrides.
 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.
+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 neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. 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
@@ -55,4 +64,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 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.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. 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/location-preferences/README.md

@@ -6,16 +6,18 @@ Original fictional example. The written scene is the complete product specificat
 
 | Dark | Light |
 | --- | --- |
-| ![A neutral adjustment glyph associated with a neutral location pin, dark presentation](dark-neutral.png) | ![The same neutral symbol pair, light presentation](light-soft.png) |
+| ![A neutral adjustment glyph associated with a neutral location pin, dark presentation](dark-refined.png) | ![The same neutral symbol pair, light presentation](light-refined.png) |
 
-Both selected PNGs are 1586 × 992 pixels. Both symbols use the same neutral treatment within each theme. This is a static association, so the image needs no accent or implied selected state.
+The pair uses compact glyphs with comparable filled ink weight and broad margins. Both symbols use the same neutral treatment within each theme. This is a static association, so the image needs no accent or implied selected state. Both selected PNGs are 1584 × 993 pixels; the pair review records the checks.
 
-The gallery selects `dark-neutral.png` and `light-soft.png`. The light revision uses the current medium-gray `primary` role for both symbols and `divider` for the separator, with a uniform neutral canvas. Earlier PNGs remain as revision sources.
+The gallery selects `dark-refined.png` and `light-refined.png`. The dark revision reduces the symbol footprint and balances the solid pin against the sparse adjustment glyph. The light counterpart retains this geometry with medium-gray `primary` glyphs and a subtle `divider`. Each theme uses its own saved values. Earlier PNGs remain as revision sources.
 
 - [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
 - [Concrete neutral-edit requests](neutral-edit-requests.md)
-- [Light palette edit request](light-palette-edit.prompt.md)
+- [Earlier light palette edit request](light-palette-edit.prompt.md)
+- [Dark refinement](dark-refinement.prompt.md), [size correction](dark-size-correction.prompt.md), and [ink-weight correction](dark-weight-correction.prompt.md)
+- [Light counterpart request](light-refinement.prompt.md)
 - [Generation and pair review](pair-review.md)
 - [Current composition examples](../README.md#composition-gallery)
 

package/examples/location-preferences/dark-refinement.prompt.md

@@ -0,0 +1,70 @@
+# Dark refinement request
+
+Actual built-in image-tool request. Edit target: dark-neutral.png. Candidate selection: dark-refined.png. See pair-review.md for the reviewed result.
+
+Use case: precise-object-edit. Input image 1 is the existing original DARK location-preferences illustration and is the edit target. Produce one PNG at exactly 1586 by 992 pixels. Revise only the symbol geometry and flatten the fills as specified below. Keep the adjustment-plus-location association, the three slider tracks with knobs left/right/left, the circular pin cutout, and the lack of accent. Make the symbols compact, separated, and optically balanced; the solid pin must not outweigh the sparse slider glyph. Each knob and its track form one uninterrupted flat fill, not a raised disc. Remove the existing cast shadows, highlights, texture, and seams. Use only the captured DARK role colors below. Do not import a light-theme gray or brighten everything. No text, extra objects, or comparison collage.
+
+# 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: Preferences can be saved for an individually selected location.
+Subject: An adjustment glyph associated with a saved location pin
+Focal detail: A balanced association between preferences and one location
+Context: Original fictional example. The written scene is the complete product specification for this example, not evidence of a shipped product.
+
+## Composition contract
+Archetype: symbol-pair
+Target canvas: 1586 × 992 pixels; landscape 1586:992. Produce a single image, not a dark/light collage.
+Place two compact symbols on one horizontal optical axis, centered as a group with generous space between them. Start with each glyph's longest dimension around 8–11% of canvas width, and the whole group around 40–48% of width; adapt to the scene and card-size clarity. Match visible ink weight rather than identical bounding boxes. A short low-contrast divider can separate them.
+Specific scene layout: Two compact symbols centered on one horizontal optical axis at half the canvas height. Place the adjustment glyph near 34 percent and the location pin near 66 percent of canvas width. The adjustment glyph is about 9 percent of canvas width and 8 percent of canvas width tall; the pin is narrower, about 7 percent of canvas width and 10 percent of canvas width tall. Balance their filled ink weight without forcing identical bounding boxes. Keep three slider tracks with knob positions left, right, left. Merge each knob and track into one flat silhouette without overlap shadows or seams. A thin divider at half the canvas width spans about 10 percent of canvas height. Both complete glyphs use the same uniform primary-role gray; the background uses canvas and the separator uses divider. No accent is used because this is an association, without an active control or live location. Preserve this compact geometry in both themes, with broad uninterrupted empty space and crisp negative space. No shading or material depth.
+Elements:
+- One three-slider adjustment glyph
+- One neutral location pin with a circular cutout
+- One short neutral vertical divider
+
+## Visual treatment
+Communicate one relationship with flat 2D filled glyphs. Match visual weight, corner treatment, and perceived size. Use an arrow only when direction itself is part of the feature. Use the same neutral gray for both symbols by default. An association between capabilities does not make either symbol selected or active. Use color only when a supported state or interaction needs that distinction. No rendered materials or sculpted 3D symbols.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build emphasis through composition, scale, and neutral value contrast before adding color. No accent is the default, and a fully neutral image is a finished result. Being new, important, or the focal subject does not itself justify color. 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
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #242527 | Uniform illustration background |
+| surface | #18191B | Base or recessed interface panels |
+| raised | #343638 | Foreground panels, controls, and quiet tile fills |
+| primary | #B9BBBE | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #777B80 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #46494D | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Optional project accent: #4678ED; this is available, not required. Use it only on the exact element whose supported state, action, or data meaning the scene says needs color. Otherwise use no accent. Keep unrelated glyphs, tiles, and supporting surfaces neutral; do not invent a colored state, badge, or marker to use the palette.
+Preserve this theme's independent charcoal hierarchy: canvas #242527, base surface #18191B, foreground surface #343638, primary #B9BBBE, and secondary #777B80. Keep the primary subject compact and supporting details quieter; do not enlarge, thicken, or brighten every glyph and label bar. Retain the necessary separation between background, panels, and focal controls instead of compressing all dark values to match a softened light variant. Respect explicit project palette overrides.
+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 neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. 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:
+- Left adjustment glyph and right location pin with equal optical weight
+- Compact symbol scale, separated centers, short divider, and broad margins
+- Three slider tracks and their left-right-left knob positions
+- Non-directional association; both symbols share one neutral gray in each theme
+- No accent color or implied active or selected state in either theme
+
+## 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
+- Arrows, routes, transfer or synchronization cues
+- Geofencing rings or automatic location triggers
+- Extra symbols or interface panels
+- Decorative accent color, gradients, texture, material depth, or shadows
+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 which two concepts are related and whether the relationship is directional. A connector must not imply transfer, synchronization, or automation unless supported by 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. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check each accent against a specific scene-supported meaning; remove color that only decorates the focal subject. 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/location-preferences/dark-size-correction.prompt.md

@@ -0,0 +1,5 @@
+# Dark size correction
+
+Actual second dark edit request. The first candidate retained the oversized source geometry and was rejected. This request corrects the symbol footprints before creating the light counterpart.
+
+Use case: precise-object-edit. Input image is the previous DARK location-preferences candidate. It did not apply the required scale correction. Make a targeted COMPOSITION correction now: reduce both symbols substantially and move their centers farther apart. Replace their old footprints; do not preserve old size or old positions. Use a canvas of 1584 x 992 pixels. On this canvas the left three-slider glyph must fit a box about 144 pixels wide and 128 pixels tall, centered at x=539,y=496. The right location pin must fit a box about 110 pixels wide and 158 pixels tall, centered at x=1045,y=496. It has one circular cutout. The center divider is only 100 pixels tall, from y=446 to 546, at x=792, about 3 pixels thick. Keep broad uniform empty charcoal around this small separated pair. These symbols together span only about 40% of canvas width; neither symbol may be as large as in the input. Keep slider knobs in left/right/left order. Render all three tracks and their knobs as merged 2D silhouettes without overlap shadows or raised disks. Background flat #242527, both glyphs flat #B9BBBE, divider #46494D. No blue, texture, glow, gradients, shadows, metal, 3D, typography, UI panels, or extra elements. One dark PNG only.

package/examples/location-preferences/dark-weight-correction.prompt.md

@@ -0,0 +1,5 @@
+# Targeted dark correction
+
+Actual built-in image-tool request; see pair-review.md for the candidate and selected result.
+
+Use case: precise-object-edit. Make one optical-weight correction to this DARK symbol pair. Keep the left adjustment glyph exactly as it is, including its position, size, three tracks and left/right/left knobs. The solid location pin currently contains much more filled area. Shrink ONLY the entire right pin, including its circular cutout, to 78% of its current width and height, keeping its center fixed at the same position. Its final outer silhouette should be about 93 pixels wide and 131 pixels high, comparable in height and total filled area to the left slider glyph. Keep the existing charcoal #242527 background, same flat #B9BBBE for both glyphs, divider #46494D, all other geometry, and broad empty space. No shadows, gradients, texture, colored accents, or new elements. Output exactly 1584 by 993 pixels, matching the input canvas. One PNG.