# visionaire-engine - Doramagic AI Context Pack > Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated. ## Sufficiency Principle - **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary. - **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work. ## How the Host AI Should Use This You are reading the AI Context Pack that Doramagic compiled for visionaire-engine. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project. ## Claim Consumption Rules - **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure. - **Minimum status for a fact**: `supported` - `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path. - `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying. - `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact. - `unverified`: Must not be used as fact; state clearly that evidence is insufficient. - `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf. ## Who It Fits Best - **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` Claim: `clm_0004` supported 0.86 ## What It Can Do - **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` Claim: `clm_0001` supported 0.86 - **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ## How to Start - `claude mcp add visionaire -- npx -y visionaire-engine` Evidence: `README.md` Claim: `clm_0005` supported 0.86 - `git clone https://github.com/mi60dev/visionaire-engine && cd visionaire-engine` Evidence: `README.md` Claim: `clm_0006` supported 0.86 - `npm install && npm run build` Evidence: `README.md` Claim: `clm_0007` supported 0.86 - `claude mcp add visionaire -- node "$PWD/dist/index.js"` Evidence: `README.md` Claim: `clm_0008` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Sandbox-trial permissions first - **Why**: The project has signals of install commands, host configuration, or local writes; do not go straight into your primary environment—trial it in isolation first. ### 30-Second Read - **What to do now**: Sandbox-trial permissions first - **Minimum safe next step**: Run Prompt Preview first; if you still want to install, trial only in an isolated environment - **Do not trust yet**: Tool permission boundaries cannot be trusted before install. - **Continuing will touch**: Command execution, Host AI configuration, Local environment or project files ### What You Can Trust Now - **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` Claim: `clm_0004` supported 0.86 - **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` Claim: `clm_0001` supported 0.86 - **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0002` supported 0.86 - **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0005` supported 0.86 ### What You Cannot Trust Yet - **Tool permission boundaries cannot be trusted before install.** (unverified): MCP/tool projects usually touch files, the network, the browser, or external APIs, so permissions and logs must be checked for real. - **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project. - **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment. - **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md` ### What Continuing Will Touch - **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md` - **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` - **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md` - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.) - **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.) - **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state. - **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually. - **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck. ## What Can Only Be Previewed - Explain who the project fits and what it can do - Demonstrate a typical conversation flow based on project docs - Help the user decide whether it is worth installing or researching further ## What Must Be Verified After Install - Actually installing the Skill, plugin, or CLI - Running scripts, modifying local files, or accessing external services - Verifying real output quality, performance, and compatibility ## Boundary & Risk Decision Card - **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0009` inferred 0.45 - **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0010` supported 0.86 - **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment. - **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments. ## Pre-Work Working Context ### Loading Order - First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset. - Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative. - Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match. - When you need to carry out a concrete task, check role_skill_index first, then evidence_index. - For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required. ### Task Routes - **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` Claim: `clm_0001` supported 0.86 - **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ### Context Scale - Total files: 199 - Important-file coverage: 40/199 - Evidence index entries: 71 - Role / Skill entries: 1 ### Handling Insufficient Evidence - **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts. - **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install. - **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run. - **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version. ## Prompt Recipes ### Fit assessment - Goal: Judge whether this project fits the user's current task. - Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation. ```text Based on the AI Context Pack for visionaire-engine, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id. ``` ### Pre-install experience - Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise. - Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language. ```text Treat visionaire-engine as a pre-install experience asset, not an already-installed tool or a real runtime environment. Output exactly four parts: 1. Ask me 3 necessary questions first. 2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow. 3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run. 4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project. Hard boundaries: - Do not claim you have installed, run, executed tests, modified files, or produced real results. - Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing". - If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...". - The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating". - Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment. - Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions. ``` ### Role / Skill selection - Goal: Pick the best-matching asset from the project's roles or Skills. - Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed. ```text Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs. ``` ### Risk pre-check - Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting. - Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items. ```text Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have. ``` ### Host AI kickoff instruction - Goal: Turn the project context into a host AI instruction for the start of a conversation. - Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI. ```text Based on the AI Context Pack for visionaire-engine, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results. ``` ## Role / Skill Index - Indexed 1 role / Skill / project-doc entries. - **visionaire-verify** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “visionaire-verify”, use it for a pre-install experience first, then decide whether to install. Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` ## Evidence Index - Indexed 71 evidence entries. - **Visionaire Engine** (documentation): Which rule, which file, which line — and why it wins. Evidence: `README.md` - **Package** (package_manifest): { "name": "visionaire-engine", "version": "0.7.0", "description": "Deterministic rendered-page \u2192 LLM context MCP server: which rule, which file, which line \u2014 and why it wins.", "type": "module", "bin": { "visionaire-engine": "dist/index.js" }, "main": "dist/index.js", "engines": { "node": " =20" }, "scripts": { "build": "tsc -p tsconfig.json", "dev": "tsx src/index.ts", "test": "vitest run", "bench": "tsx bench/run.ts", "demo": "tsx scripts/demo.ts" }, "keywords": "mcp", "css", "devtools", "debugging", "wordpress", "llm" , "license": "Apache-2.0", "dependencies": { "@jridgewell/trace-mapping": "^0.3.31", "@modelcontextprotocol/sdk": "^1.29.0", "puppeteer-core": "^24.43.1", "zod":… Evidence: `package.json` - **Architecture** (documentation): How visionaire-engine turns a rendered page into deterministic, attributable answers — and why it is built this way. Evidence: `docs/architecture.md` - **Install in your MCP client** (documentation): Visionaire is a standard stdio MCP server , so it works in any MCP-capable client — Claude, GitHub Copilot, Cursor, Google Antigravity, Windsurf, Zed, and others. The server is identical everywhere; only the registration differs. Evidence: `docs/clients.md` - **Tool reference** (documentation): Visionaire Engine exposes 28 MCP tools: three session tools connect , navigate , set viewport , sixteen inspection tools — ten for the frozen moment what the page looks like and why , three for the time dimension get listeners , explain animations , record interaction — what happens and why , plus three added in v0.4: interact drive the UI into a state and leave it there , measure element sub-pixel glyph/text-ink centering , and evaluate the escape hatch for genuinely bespoke reads — three fix-loop/pixel tools from v0.5–v0.6 inject css , check alignment , pick color , and six verification tools new in v0.7 : assert visual , visual diff , impact preview , diagnose , responsive sweep , captur… Evidence: `docs/tools.md` - **WordPress origin resolution** (documentation): Visionaire's headline trick: on a WordPress site, it doesn't just tell you which CSS rule wins — it tells you where that rule actually lives and where to go edit it , even when the "file" Chrome shows you is a generated artifact nobody should ever open. Evidence: `docs/wordpress.md` - **Contributing to Visionaire Engine** (documentation): Bug reports, feature requests, and pull requests are welcome — open an issue first for anything larger than a small fix. Field reports from real debugging sessions are especially valued — a description of where a tool got clumsy or gave the wrong context has driven most releases so far. Evidence: `CONTRIBUTING.md` - **When this applies** (skill_instruction): When this applies Any turn where you edited a file that affects rendering CSS/SCSS, styled-components, Tailwind classes, template/JSX markup, inline styles . If in doubt, verify. The loop do this every time, in order 1. BEFORE editing a shared selector a class used in more than one place , call impact preview { selector }. If it matches more than ~3 elements or spans multiple visual roles, tell the user what will be touched before you edit. 2. Make the smallest edit that could fix the issue. 3. AFTER the edit, verify — do NOT claim success from reading the code: - If a suite exists for this area, call assert visual { suite id }. - Otherwise state your claim as assertions, e.g. assert visual… Evidence: `harness/claude/skills/visionaire-verify/SKILL.md` - **License** (source_file): Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ Evidence: `LICENSE` - **Development guide** (documentation): Building, testing, and extending visionaire-engine. For what the tools do, see tools.md tools.md ; for how the pipeline works internally and the authoritative design reference, see architecture.md architecture.md . Evidence: `docs/development.md` - **The verify-after-edit harness** (documentation): An agent edits a stylesheet, reads its own diff, and declares "now the cards are equal height" — without ever seeing a rendered pixel. The user looks at the browser, the cards are still ragged, and the agent doubles down because the source "looks right". LLMs cannot see rendering; source code holds many candidate rules but only the live cascade decides which one wins. The harness in this directory closes that gap mechanically: after any edit to a rendering file, the agent is nudged to verify against the live page, and the turn is physically blocked from ending with an unverified "it's fixed" claim. Evidence: `docs/harness.md` - **Glama** (structured_config): { "$schema": "https://glama.ai/mcp/schemas/server.json", "maintainers": "mi60dev" } Evidence: `glama.json` - **Tsconfig** (structured_config): { "compilerOptions": { "target": "ES2022", "module": "NodeNext", "moduleResolution": "NodeNext", "lib": "ES2022", "DOM" , "strict": true, "esModuleInterop": true, "skipLibCheck": true, "declaration": true, "sourceMap": true, "outDir": "dist", "rootDir": "src", "resolveJsonModule": true, "forceConsistentCasingInFileNames": true }, "include": "src" } Evidence: `tsconfig.json` - **.dockerignore** (source_file): node modules dist test bench launch scripts .github .git .tgz Evidence: `.dockerignore` - **Demo** (source_file): import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { SessionManager } from '../src/session.js' import { explainStylesTool } from '../src/tools/explain-styles.js' import { pageSnapshotTool } from '../src/tools/page-snapshot.js' ⋮---- interface DemoArgs { url: string selector: string } ⋮---- function parseArgs argv: string : DemoArgs ⋮---- async function main : Promise Evidence: `scripts/demo.ts` - **Index** (source_file): import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js' import { createServer } from './server.js' import { SessionManager } from './session.js' ⋮---- async function shutdown signal: string : Promise Evidence: `src/index.ts` - **Vitest.Config** (source_file): import { defineConfig } from 'vitest/config' Evidence: `vitest.config.ts` - **Box Model** (source_file): import type { Protocol } from 'puppeteer-core' import type { Bounds, BoxSummary, ResolvedNode, ToolContext } from '../types.js' ⋮---- function round1 n: number : number ⋮---- function quadBounds quad: Protocol.DOM.Quad : Bounds ⋮---- function sideWidths inner: Protocol.DOM.Quad, outer: Protocol.DOM.Quad, : number, number, number, number ⋮---- export async function getBoxSummary ctx: ToolContext, node: ResolvedNode, : Promise Evidence: `src/engine/box-model.ts` - **Cascade** (source_file): import type { Protocol } from 'puppeteer-core' import type { DeclarationInfo, DeclOriginType, LossReason, PropertyVerdict, Specificity, } from '../types.js' import { compareSpecificity, computeSpecificity } from './specificity.js' ⋮---- function stripImportant value: string : string ⋮---- function isInheritable property: string : boolean ⋮---- type BucketOrigin = 'user-agent' 'inline' 'author' ⋮---- function bucketOf origin: BucketOrigin, important: boolean : number ⋮---- interface Candidate { decl: DeclarationInfo distance: number order: number bucket: number } ⋮---- interface RuleCtx { selector?: string specificity?: Specificity layerChain?: string media?: string styleSheetId?: string } ⋮… Evidence: `src/engine/cascade.ts` - **Color** (source_file): export type Rgba = number, number, number, number ⋮---- export function parseCssColor input: string : Rgba undefined ⋮---- export function toHex r, g, b : Rgba : string ⋮---- const h = v: number : string ⋮---- export function relativeLuminance r, g, b : Rgba : number ⋮---- const lin = c: number : number = ⋮---- export function contrastRatio a: Rgba, b: Rgba : number ⋮---- function srgbToOklab r, g, b : Rgba : number, number, number ⋮---- export function oklabDeltaE a: Rgba, b: Rgba : number ⋮---- export function contrastVerdict ratio: number : string Evidence: `src/engine/color.ts` - **Geometry** (source_file): export interface ContentBox { x: number y: number width: number height: number } ⋮---- export interface InkMetrics { textLeft: number baseline: number left: number right: number ascent: number descent: number advance: number empty: boolean } ⋮---- export interface MeasurePayload { content: ContentBox ink: InkMetrics font: string fontShort: string text: string } ⋮---- export function measureExpression : string ⋮---- export interface InkBox { left: number right: number top: number bottom: number width: number height: number centerX: number centerY: number } ⋮---- export function inkBox ink: InkMetrics : InkBox ⋮---- function round1 n: number : number ⋮---- function boxCenter box: ContentBox :… Evidence: `src/engine/geometry.ts` - **Specificity** (source_file): import type { Specificity } from '../types.js' ⋮---- export function computeSpecificity selector: string : Specificity ⋮---- export function compareSpecificity a: Specificity, b: Specificity : number ⋮---- function maxOfList list: string : Specificity ⋮---- function complexSpecificity sel: string : Specificity ⋮---- function isIdentStart ch: string : boolean ⋮---- function skipIdent s: string, i: number : number ⋮---- / From an opening bracket, return the index just past its balanced close. Quote- and escape-aware. / function skipBalanced s: string, openIdx: number, open: string, close: string : number ⋮---- function skipString s: string, quoteIdx: number : number ⋮---- / Split on a separat… Evidence: `src/engine/specificity.ts` - **Find Elements** (source_file): import type { Protocol } from 'puppeteer-core' import { z } from 'zod' import type { ToolContext, ToolDef } from '../types.js' import { sanitizePageText } from '../types.js' import { selectorHelp } from '../engine/suggest.js' ⋮---- interface MatchItem { tag: string classes: string id?: string text?: string href?: string x: number y: number w: number h: number } ⋮---- function searchExpression crit: z.infer : string ⋮---- function describeException details: Protocol.Runtime.ExceptionDetails : string ⋮---- function identityOf item: ⋮---- async function unpackNodeArray ctx: ToolContext, arrayObjectId: string, : Promise : number ⋮---- // A guessed selector that matches nothing is the common fai… Evidence: `src/tools/find-elements.ts` - **Node At Point** (source_file): import type { Protocol } from 'puppeteer-core' import { z } from 'zod' import type { ToolContext, ToolDef } from '../types.js' ⋮---- interface ChainItem { tag: string classes: string id?: string text?: string x?: number y?: number w?: number h?: number } ⋮---- function describeException details: Protocol.Runtime.ExceptionDetails : string ⋮---- async function unpackNodeArray ctx: ToolContext, arrayObjectId: string, : Promise< ⋮---- function chainEntry uid: string, item: ChainItem : string Evidence: `src/tools/node-at-point.ts` - **Page Origins** (source_file): import { z } from 'zod' import { estimateTokens } from '../types.js' import type { PlatformInfo, SheetInfo, ToolDef } from '../types.js' import { detectPlatformFromPage } from '../attribution/wordpress.js' ⋮---- function kb chars: number : string ⋮---- function renderPlatform p: PlatformInfo : string ⋮---- const compose = : string = Evidence: `src/tools/page-origins.ts` - **Page Snapshot** (source_file): import type { Protocol } from 'puppeteer-core' import { z } from 'zod' import type { Bounds, PageMeta, SnapshotNode, TargetSpec, ToolContext, ToolDef, ToolResult, } from '../types.js' import { COMPUTED WHITELIST } from '../types.js' import { resolveTarget } from '../uid.js' import { renderCensus } from '../format/census.js' import { detectPlatformFromPage } from '../attribution/wordpress.js' ⋮---- function snapshotToTree ctx: ToolContext, doc: Protocol.DOMSnapshot.DocumentSnapshot, strings: string , viewport: Bounds, scopeBackendId?: number, : SnapshotNode ⋮---- const str = i: number undefined : string undefined ⋮---- const tagOf = i: number : string ⋮---- // Pseudo-element rows ::before et… Evidence: `src/tools/page-snapshot.ts` - **Pick Color** (source_file): import { z } from 'zod' import type { ToolContext, ToolDef } from '../types.js' import { pairAttributes, resolveTarget } from '../uid.js' import { decodePng } from '../engine/png.js' import { contrastRatio, contrastVerdict, parseCssColor, toHex, type Rgba } from '../engine/color.js' ⋮---- async handler ctx, args Evidence: `src/tools/pick-color.ts` - **Manifest** (structured_config): { "id": 1, "file": "cases/case01-specificity-override.html", "user report": "I set the subscribe button's bottom margin to 8px but it still has a huge gap under it.", "target": { "selector": ".btn" }, "tool": "explain styles", "args": { "property": "margin-bottom" }, "expected": "WINNER", "32px", "case01.css:10", "lost specificity ", "8px", "case01.css:14" }, { "id": 2, "file": "cases/case02-source-order.html", "user report": "The nav links should be blue per my stylesheet but they render grey.", "target": { "selector": ".nav a" }, "tool": "explain styles", "args": { "property": "color" }, "expected": "WINNER", " 777777", "case02-skin.css:10", "lost order ", " 0055ff", "case02-base.css:10"… Evidence: `bench/manifest.json` - **Settings.Snippet** (structured_config): { "hooks": { "PostToolUse": { "matcher": "Edit Write MultiEdit", "hooks": { "type": "command", "command": ".claude/hooks/visionaire nudge.sh", "timeout": 10 } } , "Stop": { "hooks": { "type": "command", "command": ".claude/hooks/visionaire gate.sh", "timeout": 30 } } } } Evidence: `harness/claude/settings.snippet.json` - **internal design/development doc — not published** (source_file): internal design/development doc — not published SPEC.md launch/ Evidence: `.gitignore` - **syntax=docker/dockerfile:1** (source_file): syntax=docker/dockerfile:1 Build stage: compile TypeScript with dev deps, then prune to production. FROM node:20-slim AS build WORKDIR /app COPY package.json package-lock.json ./ RUN npm ci COPY tsconfig.json ./ COPY src ./src RUN npm run build && npm prune --omit=dev Evidence: `Dockerfile` - **Notice** (source_file): Visionaire Engine Copyright 2026 mi60dev https://github.com/mi60dev/visionaire-engine Evidence: `NOTICE` - **Run** (source_file): import fs from 'node:fs' import http from 'node:http' import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { findChromeExecutable, SessionManager } from '../src/session.js' import { explainStylesTool } from '../src/tools/explain-styles.js' import { inspectAncestorsTool } from '../src/tools/inspect-ancestors.js' import { inspectElementTool } from '../src/tools/inspect-element.js' import { pageSnapshotTool } from '../src/tools/page-snapshot.js' import type { ToolDef } from '../src/types.js' import { estimateTokens } from '../src/types.js' ⋮---- async function resolveTool name: string : Promise ⋮---- interface BenchCase { id: number file: string user repo… Evidence: `bench/run.ts` - **Harness Init** (source_file): import fs from 'node:fs' import path from 'node:path' import { fileURLToPath } from 'node:url' ⋮---- interface HarnessFile { src: string dest: string executable: boolean side: 'claude' 'cursor' } ⋮---- function templateRoot : string ⋮---- function installFile srcAbs: string, destRel: string, force: boolean, executable: boolean : void ⋮---- export async function initHarness argv: string : Promise Evidence: `src/harness-init.ts` - **Server** (source_file): import { createRequire } from 'node:module' import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js' ⋮---- import type { CallToolResult } from '@modelcontextprotocol/sdk/types.js' import { z } from 'zod' import type { SessionManager } from './session.js' import type { ToolDef, ToolResult } from './types.js' import { annotatedScreenshotTool } from './tools/annotated-screenshot.js' import { assertVisualTool } from './tools/assert-visual.js' import { captureProofTool } from './tools/capture-proof.js' import { checkAlignmentTool } from './tools/check-alignment.js' import { diagnoseTool } from './tools/diagnose.js' import { evaluateTool } from './tools/evaluate.js' import { impactPrev… Evidence: `src/server.ts` - **Session** (source_file): import { spawnSync } from 'node:child process' import fs from 'node:fs' import os from 'node:os' import path from 'node:path' import puppeteer from 'puppeteer-core' import type { Browser, CDPSession, LaunchOptions, Page, Protocol } from 'puppeteer-core' import { ScriptRegistry } from './attribution/scripts.js' import { StylesheetRegistry } from './attribution/stylesheets.js' import type { ToolContext } from './types.js' import { UidRegistry } from './uid.js' ⋮---- export function findPuppeteerCachedChrome baseDir: string : string undefined ⋮---- function puppeteerCacheChromeDirs : string ⋮---- async function enableDebugger cdp: CDPSession : Promise ⋮---- export function findChromeExecutable… Evidence: `src/session.ts` - **Uid** (source_file): import type { Protocol } from 'puppeteer-core' import type { ResolvedNode, TargetSpec, ToolContext, UidEntry, UidRegistryLike } from './types.js' import { sanitizePageText } from './types.js' import { selectorHelp } from './engine/suggest.js' ⋮---- function sanitizeMeta meta: Partial , : Partial ⋮---- export class UidRegistry implements UidRegistryLike ⋮---- assign backendNodeId: number, meta: Partial = ⋮---- get uid: string : UidEntry undefined ⋮---- byBackendId backendNodeId: number : string undefined ⋮---- clear : void ⋮---- export async function resolveTarget ctx: ToolContext, target: TargetSpec : Promise ⋮---- export function pairAttributes flat: string undefined : Map Evidence: `src/uid.ts` - **Animations.E2E.Test** (source_file): import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { findChromeExecutable, SessionManager } from '../src/session.js' import { explainAnimationsTool } from '../src/tools/explain-animations.js' ⋮---- const fixtureUrl = name: string : string ⋮---- async function explain selector: string : Promise Evidence: `test/animations.e2e.test.ts` - **Animations.Test** (source_file): import { describe, expect, it } from 'vitest' import { COMPOSITOR FRIENDLY PROPS, findAnimationIssues, NON ANIMATABLE PROPS, serializeAnimationsExpression, type AnimationIssueInput, } from '../src/engine/animations.js' import type { AnimationCensusEntry, AnimationFinding } from '../src/types.js' ⋮---- function entry partial: Partial = ⋮---- function run partial: Partial = ⋮---- const ofRule = findings: AnimationFinding , rule: AnimationFinding 'rule' : AnimationFinding Evidence: `test/animations.test.ts` - **Assert.E2E.Test** (source_file): import fs from 'node:fs' import os from 'node:os' import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { SessionManager, findChromeExecutable } from '../src/session.js' import { assertVisualTool } from '../src/tools/assert-visual.js' import type { AssertionResult } from '../src/engine/assert.js' ⋮---- const fixtureUrl = name: string : string ⋮---- interface Envelope { verdict: 'PASS' 'FAIL' summary: string results: AssertionResult suite id?: string truncated: boolean next offset?: number } ⋮---- const run = async args: Record : Promise = const byId = env: Envelope, id: string : Assertio… Evidence: `test/assert.e2e.test.ts` - **Assert.Test** (source_file): import { describe, expect, it } from 'vitest' import { ARITY, ASSERTION TYPES, OFFENDING UIDS CAP, evaluateAssertion, isAssertionType, overallVerdict, snapPx, summarize, type AssertionEvidence, type AssertionSpec, type MeasuredElement, } from '../src/engine/assert.js' import type { Bounds } from '../src/types.js' ⋮---- function el uid: string, content: Bounds, extra: Partial = ⋮---- function ev elements: MeasuredElement , extra: Partial = ⋮---- function spec type: string, partial: Partial = Evidence: `test/assert.test.ts` - **Blast.E2E.Test** (source_file): import { describe, it, expect, beforeAll, afterAll } from 'vitest' import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { SessionManager, findChromeExecutable } from '../src/session.js' import { explainStylesTool } from '../src/tools/explain-styles.js' import type { ToolContext } from '../src/types.js' Evidence: `test/blast.e2e.test.ts` - **Cascade.Test** (source_file): import { describe, expect, it } from 'vitest' import type { Protocol } from 'puppeteer-core' import { computeCascade } from '../src/engine/cascade.js' import { compareSpecificity, computeSpecificity } from '../src/engine/specificity.js' import type { PropertyVerdict } from '../src/types.js' ⋮---- type CSSProperty = Protocol.CSS.CSSProperty type CSSStyle = Protocol.CSS.CSSStyle type RuleMatch = Protocol.CSS.RuleMatch type Matched = Protocol.CSS.GetMatchedStylesForNodeResponse ⋮---- function prop name: string, value: string, extra: Partial = ⋮---- function style props: CSSProperty , extra: Partial = ⋮---- function ruleMatch selector: string, props: CSSProperty , extra: { origin?: Protocol.CSS… Evidence: `test/cascade.test.ts` - **Coldstart.Test** (source_file): import { afterEach, beforeEach, describe, expect, it } from 'vitest' import fs from 'node:fs' import os from 'node:os' import path from 'node:path' import { findPuppeteerCachedChrome, isSandboxBlocked } from '../src/session.js' ⋮---- function relBinary : string ⋮---- function platformDir : string ⋮---- function writeFakeChrome base: string, version: string : string Evidence: `test/coldstart.test.ts` - **Diagnose.E2E.Test** (source_file): import fs from 'node:fs' import os from 'node:os' import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { findChromeExecutable, SessionManager } from '../src/session.js' import { diagnoseTool } from '../src/tools/diagnose.js' ⋮---- const fixtureUrl = name: string : string ⋮---- interface Culprit { rank: number confidence: 'high' 'medium' 'low' cause: string plain: string evidence: Record } ⋮---- interface Envelope { summary: string symptom detected: string culprits: Culprit truncated: boolean } ⋮---- async function run args: Record : Promise Evidence: `test/diagnose.e2e.test.ts` - **E2E.Test** (source_file): import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { findChromeExecutable, SessionManager } from '../src/session.js' import { explainStylesTool } from '../src/tools/explain-styles.js' import { inspectAncestorsTool } from '../src/tools/inspect-ancestors.js' import { inspectElementTool } from '../src/tools/inspect-element.js' import { pageOriginsTool } from '../src/tools/page-origins.js' import { pageSnapshotTool } from '../src/tools/page-snapshot.js' import { resolveTarget } from '../src/uid.js' ⋮---- const fixtureUrl = name: string : string ⋮---- function uidFrom dossierText: string :… Evidence: `test/e2e.test.ts` - **Evaluate.E2E.Test** (source_file): import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { findChromeExecutable, SessionManager } from '../src/session.js' import { evaluateTool } from '../src/tools/evaluate.js' import type { ToolContext } from '../src/types.js' ⋮---- async function run args: Record : Promise Evidence: `test/evaluate.e2e.test.ts` - **Find.E2E.Test** (source_file): import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { findChromeExecutable, SessionManager } from '../src/session.js' import { findElementsTool } from '../src/tools/find-elements.js' import type { ToolContext } from '../src/types.js' ⋮---- const run = args: Record : Promise Evidence: `test/find.e2e.test.ts` - **Geometry.Test** (source_file): import { describe, expect, it } from 'vitest' import { centeringDeltas, inkBox, measureExpression, type ContentBox, type InkMetrics, } from '../src/engine/geometry.js' ⋮---- function box cx: number, cy: number, w: number, h: number : ContentBox ⋮---- function inkCenteredAt cx: number, cy: number, hw: number, hh: number : InkMetrics Evidence: `test/geometry.test.ts` - **Hardening.E2E.Test** (source_file): import { describe, it, expect, beforeAll, afterAll } from 'vitest' import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { SessionManager, findChromeExecutable } from '../src/session.js' import { pageSnapshotTool } from '../src/tools/page-snapshot.js' import { inspectElementTool } from '../src/tools/inspect-element.js' import type { ToolContext } from '../src/types.js' Evidence: `test/hardening.e2e.test.ts` - **Harness Gate.Test** (source_file): import { execFileSync } from 'node:child process' import fs from 'node:fs' import os from 'node:os' import path from 'node:path' import { afterEach, beforeEach, describe, expect, it } from 'vitest' import { initHarness } from '../src/harness-init.js' ⋮---- const runHook = script: string, input: string, env?: NodeJS.ProcessEnv : string ⋮---- const stubPath = names: string : string = Evidence: `test/harness-gate.test.ts` - **Harness Init.Test** (source_file): import fs from 'node:fs' import os from 'node:os' import path from 'node:path' import { afterEach, beforeEach, describe, expect, it } from 'vitest' import { initHarness } from '../src/harness-init.js' Evidence: `test/harness-init.test.ts` - **Impact.E2E.Test** (source_file): import { describe, it, expect, beforeAll, afterAll } from 'vitest' import fs from 'node:fs' import os from 'node:os' import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { SessionManager, findChromeExecutable } from '../src/session.js' import { impactPreviewTool } from '../src/tools/impact-preview.js' import { resolveTarget } from '../src/uid.js' ⋮---- const fixtureUrl = name: string : string ⋮---- interface ChangedRow { uid: string prop: string before: string after: string } ⋮---- interface Envelope { summary: string match count: number groups: Array dry run?: { would change count: number unaffected count: number changed: ChangedRow method: string not… Evidence: `test/impact.e2e.test.ts` - **Impact.Test** (source_file): import { describe, it, expect } from 'vitest' import { groupImpact, impliedRole, regionOf, type ImpactItem } from '../src/engine/impact.js' ⋮---- const item = over: Partial = ⋮---- const rectAtCenterY = cy: number = Evidence: `test/impact.test.ts` - **Inactive.Test** (source_file): import { describe, expect, it } from 'vitest' import { findInactiveDeclarations } from '../src/engine/inactive.js' import type { DeclarationInfo } from '../src/types.js' ⋮---- function decl property: string, value: string : DeclarationInfo ⋮---- function cm entries: Record = Evidence: `test/inactive.test.ts` - **Inject.E2E.Test** (source_file): import { describe, it, expect, beforeAll, afterAll } from 'vitest' import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { SessionManager, findChromeExecutable } from '../src/session.js' import { injectCssTool } from '../src/tools/inject-css.js' import { evaluateTool } from '../src/tools/evaluate.js' import type { ToolContext } from '../src/types.js' ⋮---- async function computedOf ctx: ToolContext, selector: string, prop: string : Promise Evidence: `test/inject.e2e.test.ts` - **Interact.E2E.Test** (source_file): import fs from 'node:fs' import http from 'node:http' import path from 'node:path' import { fileURLToPath } from 'node:url' import type { AddressInfo } from 'node:net' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { findChromeExecutable, SessionManager } from '../src/session.js' import { interactTool } from '../src/tools/interact.js' import { inspectElementTool } from '../src/tools/inspect-element.js' Evidence: `test/interact.e2e.test.ts` - **Interaction.E2E.Test** (source_file): import fs from 'node:fs' import http from 'node:http' import path from 'node:path' import { fileURLToPath } from 'node:url' import type { AddressInfo } from 'node:net' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { buildTimeline, renderTimeline } from '../src/engine/timeline.js' import { findChromeExecutable, SessionManager } from '../src/session.js' import { recordInteractionTool } from '../src/tools/record-interaction.js' import type { TimelineEvent } from '../src/types.js' ⋮---- const sleep = ms: number : Promise ⋮---- const ev = partial: Partial & ⋮---- const listener = : void = Evidence: `test/interaction.e2e.test.ts` - **Listeners.E2E.Test** (source_file): import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { findChromeExecutable, SessionManager } from '../src/session.js' import { getListenersTool } from '../src/tools/get-listeners.js' ⋮---- const fixtureUrl = name: string : string ⋮---- async function run args: Record : Promise Evidence: `test/listeners.e2e.test.ts` - **Measure.E2E.Test** (source_file): import path from 'node:path' import { fileURLToPath, pathToFileURL } from 'node:url' import { afterAll, beforeAll, describe, expect, it } from 'vitest' import { findChromeExecutable, SessionManager } from '../src/session.js' import { measureElementTool } from '../src/tools/measure-element.js' ⋮---- const fixtureUrl = name: string : string ⋮---- function delta text: string, axis: 'horizontal' 'vertical' : number ⋮---- function dims text: string, label: string : ⋮---- async function run args: Record : Promise Evidence: `test/measure.e2e.test.ts` - The remaining 11 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`. ## Rules the Host AI Must Follow - **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `package.json`, `docs/architecture.md` - **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `package.json`, `docs/architecture.md` ## Questions the User Should Answer First - Which host AI or local environment do you plan to use it in? - Do you just want to experience the workflow first, or are you ready to actually install? - What matters most to you: install cost, output quality, or conflicts with your existing rules? ## Acceptance Checks - Every capability claim can be traced back to a file path in evidence_refs. - AI_CONTEXT_PACK.md does not package previews as a real run. - The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes. --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview, Installation & Quick Start**: importance `high` - source_paths: README.md, package.json, docs/clients.md, scripts/demo.ts, src/index.ts - **System Architecture & Deterministic Pipeline**: importance `high` - source_paths: docs/architecture.md, src/engine/cascade.ts, src/engine/specificity.ts, src/engine/box-model.ts, src/engine/geometry.ts - **MCP Tools Reference & WordPress Integration**: importance `high` - source_paths: docs/tools.md, docs/wordpress.md, src/tools/page-snapshot.ts, src/tools/page-origins.ts, src/tools/find-elements.ts - **Deployment, Security, Benchmarking & Extensibility**: importance `medium` - source_paths: Dockerfile, glama.json, .dockerignore, package.json, tsconfig.json ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `876befd186cfaf0677e47aa89dba8e340d6bf4db` - inspected_files: `Dockerfile`, `README.md`, `package.json`, `docs/architecture.md`, `docs/clients.md`, `docs/development.md`, `docs/harness.md`, `docs/tools.md`, `docs/wordpress.md`, `src/attribution/scripts.ts`, `src/attribution/sourcemaps.ts`, `src/attribution/stylesheets.ts`, `src/attribution/wordpress.ts`, `src/engine/alignment.ts`, `src/engine/ancestors.ts`, `src/engine/animations.ts`, `src/engine/assert-collect.ts`, `src/engine/assert.ts`, `src/engine/box-model.ts`, `src/engine/cascade.ts` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: v0.6.1 — the pixel-perfect release - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.6.1 — the pixel-perfect release. Context: Observed when using node - Why it matters: Upgrade or migration may change expected behavior: v0.6.1 — the pixel-perfect release - Evidence: failure_mode_cluster:github_release | https://github.com/mi60dev/visionaire-engine/releases/tag/v0.6.1 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/mi60dev/visionaire-engine - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: downstream_validation.risk_items | https://github.com/mi60dev/visionaire-engine - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: risks.scoring_risks | https://github.com/mi60dev/visionaire-engine - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/mi60dev/visionaire-engine - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Maintenance risk requires verification - Trigger: release_recency=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/mi60dev/visionaire-engine - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Maintenance risk requires verification - Trigger: Developers should check this maintenance risk before relying on the project: v0.6.2 — Apache-2.0 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.6.2 — Apache-2.0. Context: Observed when using docker - Why it matters: Upgrade or migration may change expected behavior: v0.6.2 — Apache-2.0 - Evidence: failure_mode_cluster:github_release | https://github.com/mi60dev/visionaire-engine/releases/tag/v0.6.2 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.