@tryvitris/website-harness 0.0.0-stage → 0.1.0-beta.6

package/agent/refs/research.md

@@ -0,0 +1,7 @@
+# Targeted business research
+
+Use research to resolve specific gaps in the business interpretation: what is sold, who it serves, how engagement works, and which claims have usable evidence. Start with captured source copy; consult official business pages or attributable primary sources when necessary.
+
+Save relevant excerpts and their source URLs in a local evidence file, then cite that file from business.json. Keep observation dates for changing information. Distinguish a published claim, an inference, a third-party review, and an unknown. A review count or star rating must have current attributable evidence before entering public copy.
+
+Do not broaden this into an unrelated SEO or social-media audit. A completed boolean is not acceptance; the business contract and independent factual review decide whether evidence is sufficient. Never invent missing contact information, prices, credentials, service areas, outcomes, or booking behavior.

package/agent/refs/sections.md

@@ -0,0 +1,6 @@
+# sections
+
+Compatibility entrypoint. Workflow graph uses direction.md for this task; load it only when needed. The selected site direction governs aesthetic choices. Preserve factual accuracy, usable interactions, and accessible markup. Do not add section/image quotas or a fixed motif count.
+
+
+Whole-page motion responsibility: for new/reauthored routes use motionPlan v2 and read `motion-page`. Cover every authored route, including expansion/contact; locate opening, development, connected quiet intervals and closing in actual IDs. Keep essential content/actions static and readable. Representative runtime success or two colocated effects is insufficient. Inspect normal desktop/mobile full journeys and reduced/static views; critique distribution, continuity, inert stretches, competition and meaningful differences among routes with located evidence. Return actionable repairs, preserving operator off and historical records. Human preference stays unset.

package/agent/refs/seo.md

@@ -0,0 +1,9 @@
+# Search and migration
+
+Use [Google's SEO starter guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) for discovery and [site-move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) for URL changes. Neither document promises rankings.
+
+Give each page a title and description that match the visible page. Do not treat a character count or exactly one H1 as a search-engine rule. Preview may be noindex. Production noindex on a page meant to be found is a defect.
+
+For every discovered material URL, record keep, redirect, consolidate, or retire in the storyboard. Do not send a real page to the homepage by accident. Sitemap URLs in production are absolute and omit redirects and nonindexable pages.
+
+Use Organization unless a real address supports LocalBusiness. Do not invent ratings, awards, reviews, or service areas.

package/agent/refs/storyboard.md

@@ -0,0 +1,27 @@
+# Narrative and composition
+
+For an opted-in reference release, read the accepted `reference-analysis.referenceSelection.plannedRelationships` and direction identity invariants. Express the accepted introduction, proof, pace, interior development and action relationships in the page/section sequence, density, media prominence and mobile transformation. Use the selected dossiers or original `reference-study-*` expansions to resolve a concrete uncertainty; do not restart discovery at every page or treat a business tag as a mandatory skeleton. Teaching facts/media never become customer facts/media.
+
+Map every legitimate original route to a disposition. Preserve meaningful content and conversion capabilities; merging routes needs a reason, not a shorter-site quota.
+
+Write `designContractVersion` 1. For each page, write `role`, `visitorOutcome`, and purpose, then sections with a question, message, `role`, `purpose`, opportunity and decision ids, fact IDs, media IDs, action behavior, emphasis plus `emphasisReason`, `layoutFamily`, `density`, `mediaProminence`, `repetitionRationale` when a repeat is deliberate, `mobileTransformation`, and transition. Layout names are not a mandatory sequence. Plan the homepage and a representative interior first as a complete visitor experience, not a compact study. Include each section's visitor question, message, fact/media IDs, visual emphasis, composition, transition, and action. Do not impose a universal section count or invent material to make the page longer. The interior must answer its own purpose instead of repeating the homepage.
+
+Write storyboard version 3. Map each selected (use) media asset to a purposeful section or an explicit globalMedia header/footer placement with assetId, placement, planned routes, and reason. Only evidenced customer logos and brand artwork qualify for global placement. The storyboard owns final media-selection.json: each selected slot names its route and placement; section slots also name sectionId. A shared slot needs one selection row per route. Inventory routes are early intentions. Reopen media for changes to inspection, identity evidence, or candidate inventory.
+
+When `launch.json` selects `composition-v1`, keep version 3 and `designContractVersion: 1`, then add `compositionContractVersion: 1` and the pinned `compositionLessonRelease`. Give each page a short `compositionIntent.organizingRelationship` and `readingSequence` of existing section IDs. For consequential sections, use stable `elementPlan` IDs with references to known facts, approved media, or the section message/action; add meaningful `relationships`, lesson applications, and `renderObservations`. Copy is written later, so do not require future copy IDs at this stage. An ordinary simple section needs no invented element or lesson count. Cross-section relationships may connect planned elements on the same route. The observations should state what a reviewer can see or test at relevant widths and states.
+
+Plan required mobile proof and action order in the page/section sequence. If that order cannot serve the visitor, record and review a justified plan revision before implementing a different sequence.
+
+Evaluate rhythm across scale, density, media prominence, alignment, background, and interaction. Changing grid to split is not enough if every section feels equally weighted. Repeat brand motifs while varying emphasis according to the narrative. Choose blocks only after the composition has a purpose.
+
+For people and work pages, explicitly map evidenced portraits and projects to the sections they substantiate. Explain intentional omissions of central source evidence. Keeping an image in the inventory does not by itself preserve its value to visitors; scattering unrelated originals across a page does not establish business fit.
+
+
+For scroll motion, use the stage-scoped `motion.md` contract. Choose business-specific scenes and quiet intervals; preserve operator policies. Carry motionPlan v2 for every new/reauthored route (historical v1 remains compatible) from direction/storyboard to unique native/component target IDs, then inspect before/during/after normal and reduced scrolling. Temporal claims require live observations or recordings; agent review is not human preference.
+
+Motion decision for new authoring: explicitly consider business character, useful emphasis and quiet intervals; compose the opening, development and closing of every authored route; static choices require explicit operator restrictions or connected quiet intervals. Preserve operator off and existing customer policies. Load only the selected motion-count/numeric/text/image/process/sequence recipe from agent/refs. Review actual scrolling for purpose, comprehensible pacing, immediate reading/actions, competing effects, enough stillness, intentional mobile treatment and repeated entrances. Bind scenes and statistic facts to stable compiled IDs; revise intent explicitly when it changes.
+
+
+Whole-page motion responsibility: for new/reauthored routes use motionPlan v2 and read `motion-page`. Cover every authored route, including expansion/contact; locate opening, development, connected quiet intervals and closing in actual IDs. Keep essential content/actions static and readable. Representative runtime success or two colocated effects is insufficient. Inspect normal desktop/mobile full journeys and reduced/static views; critique distribution, continuity, inert stretches, competition and meaningful differences among routes with located evidence. Return actionable repairs, preserving operator off and historical records. Human preference stays unset.
+
+When a service or action needs an icon, load `icons.md`, search and inspect the candidate. Choose by meaning, reserve the recommended size, and retain the service label. Technical illustrations and studio families need more space; compact navigation may use a simpler core symbol or text alone. Do not plan unsupported family/icon combinations.

package/agent/refs/template-adaptation.md

@@ -0,0 +1,42 @@
+# Adapting a selected template
+
+Direct input: `vitris site create --from URL --template "catalog ID, name, or hosted URL" --content "exact text"` (or `--content-file FILE`) records the chosen template upfront; `vitris run` and `npm run go -- ...` accept the same template/content options. A recorded direct request has `adaptation.checkpoints: "automatic"`, `sections: "agent-decides"`, and `aiImages: "no-ai"`. Continue the active-agent loop through local preview without asking for picker selection, adaptation setup, missing-content decisions, or representative feedback. Read `onboarding/additional-content.md` alongside harvested evidence, preserving supplied wording and explicit corrections. Inspect and inventory the chosen template, retain its defining relationships, and keep all critic, fidelity, browser and quality gates. Use the representative comparison to repair defects before expansion. Missing facts become visible fill-ins and still block launch. This is an operational continuation contract, not a fabricated answer or human design endorsement. The interactive instructions below apply when automatic checkpoints have not been explicitly requested; exact image/removal policies and any saved feedback still apply.
+
+New redesign scaffolds enable `launch.json.templateAdaptation: {version:2}` and template selection. This adds a common checkpoint for picker, chat, CLI and imported choices. A choice without adaptation preferences stops before reference authoring and offers preserve-and-ask and ask-each suggestions. Suggestions never become answers automatically. Existing selections retain their policies until explicitly opting in; managed upgrades preserve launch.json and do not manufacture migration answers.
+
+The workflow writes pending questions to `agent/template-questions.json` before creating a stage lease or consuming an attempt. Ask related content questions together, show each exact image treatment separately, and retain existing session authorization. Record a prior explicit answer verbatim when it already resolves the current question. Use `vitris-themes answer --site ABSOLUTE_SITE --file ABSOLUTE_RESPONSE_JSON`, with `{id,proposalHash,source:"user-chat"|"user-ui",instruction:"exact answer",value:...}`. Policy value is the preference object below; content value is `defer`, `provided`, or `request-removal`; image value is `approve` or `decline`. Keep supplied notes in instruction. `defer` completes the decision while retaining a designed fill-in. Removal requests stop dependent work until the exact removal proposal is revised and its existing human instruction recorded. Retries retain answers; changed questions require new answers. Test simulations use the distinct test-simulation source and never establish human preference.
+
+Before direction, the separate `template-reference-review` critic examines `onboarding/template-inventory.json` against every pageId in the selected catalog revision. The reference-analysis owner writes `{version:1,selectionHash,evidence:[{path,sha256}],pages:[{key:"catalog pageId",url,sections:[{id,label,role,mediaRole,rhythm}]}]}`. Section IDs are globally unique, including recurring navigation, opening, development, case modules and closing. Evidence hashes bind real inspected captures. Independently inspect the reference and evaluate page/section coverage, media roles, personality/rhythm and customer mapping. Do not call an author inventory complete without checking it against the live reference. Every adaptation section includes `referenceIds`; several related reference sections may map to a useful customer section with an explained relationship. Missing inventory pages or unmapped section IDs fail. The critic writes a standard version-2 review bound to the current inventory, adaptation and selection via `vitris-eval --subject`, with located checks for `page-coverage`, `section-coverage`, `media-roles`, `personality-and-rhythm`, and `customer-mapping`. A critic assessment remains distinct from human approval.
+
+For each AI image proposal in version 2, include `commissionHash: digest(exact VisualCommission)` and `references: [{assetId,path,sha256}]` (an empty list for an original illustration). Plan the full commission alongside the proposal so the eventual asset brief reproduces it. Hashes cover purpose, treatment, identity, commission and reference bytes; the decision store separately binds the selected template. Generation dispatch checks authorization before calling the host adapter or writing a generation record, and registration checks again. Changed commission or source bytes require a revised proposal and answer. Valid earlier exact image decisions remain valid; declined proposals retain the agreed placeholder or alternative. A host image tool called directly outside the harness must follow the same human instruction; the harness cannot intercept unrelated external calls.
+
+Before copy expansion, show the actual representative homepage and interior with the current reference comparison and ask for feedback. Save `representative-feedback` with `continue` or `refine`. Refinement feedback is retained and blocks expansion until a repaired comparison receives a new response. No author lease or repeated attempt is consumed while waiting. `vitris-themes queue --site ABSOLUTE_SITE` derives a current content refinement queue with route, target, owner, status, exact decision and next action. For archived experiments ask about original context, historical process and lessons; do not imply an active project or require current results. Unfinished sections continue to block launch.
+
+When a selection has `adaptation: {version:1, sections, aiImages, priorities}`, treat it as the user's adaptation contract. The picker asks these questions before saving. Chat choices use `vitris-themes select ... --adaptation-file ABSOLUTE_JSON`; keep exact wording in notes and priorities. Legacy selections without this field remain compatible. Test simulations and agent delegation never establish human preference.
+
+During reference-analysis, inspect the actual selected template, including its interior pages and interactions. Write `onboarding/template-adaptation.json`:
+
+```json
+{
+  "version": 1,
+  "selectionHash": "currentSelectionHash from the selection store",
+  "reference": {"url": "https://hosted-template/", "evidence": ["onboarding/reference-home.png"]},
+  "qualities": [{"id": "cinematic-opening", "relationship": "Describe the actual visual/emotional relationship", "implementation": "Locate the customer equivalent and its interaction"}],
+  "sections": [{"id": "selected-work", "referenceSection": "Selected work browsing", "disposition": "adapt", "route": "/", "targetId": "selected-work", "content": "placeholder", "nextStep": "Ask the owner to supply project scope and results; retain until answered"}],
+  "images": [{"id": "project-cover", "purpose": "Work preview", "treatment": "Exact proposed art direction", "identity": "Concept artwork, not a customer project photograph", "status": "proposed"}]
+}
+```
+
+Inventory every major reference section and recurring experience, including footer, navigation, project browsing and case-page development. Do not reduce a rich template to a palette, large heading and two rows. Preserve its relationships, density changes, media roles, motion and quiet intervals. An intentional customer adaptation can change labels and facts while preserving that experience. Missing source material calls for a content question, draft copy or a placeholder, with a concrete next action. Inspect retained raw markup before claiming the source has no content.
+
+For `sections: preserve-ask`, every removal needs a direct human answer. For `aiImages: ask-each`, propose each image's purpose, treatment and identity separately and wait for that answer before generating. `no-ai` prohibits AI production. Approved proposals and removals are recorded in `agent/template-decisions.json` as `{version:1,selectionHash,decisions:[{kind:"generate-image"|"remove-section",id,proposalHash,source:"user-chat"|"user-ui",instruction:"exact answer"}]}`. Compute proposalHash with `templateProposalHash`; changed image treatment/identity or changed selection invalidates the answer. Do not write that decision file from an authoring stage or fabricate an answer. Image status alone is not approval. Declined/proposed images retain their visual place using a placeholder or agreed alternative.
+
+Bind retained sections to real route target IDs. Visible content gaps carry `data-content-gap="SECTION_ID"` and a readable fill-in prompt; no hidden dummy content or fictional achievements. Author drafts as explicitly unfinished local-preview content and keep them separate from verified business facts. A local preview may have these gaps; launch preflight blocks them until resolved. Record the content owner/question in nextStep. Follow existing source/media provenance and accessibility requirements.
+
+Before expansion, compare the representative page with the selected reference and show the comparison to the user for feedback. During representative-review and visual-review, add `templateFidelity: {selectionHash,distHash,qualities:[{id,referenceEvidence,implementedEvidence,observation,verdict:"pass"|"fail"}]}` to the normal review. Include every brief quality, actual reference captures and current implementation captures. Explain the visual relationship observed, and capture before/during/after for temporal claims. Passing a mechanical motion check does not establish expressive motion, and an agent review does not establish human approval. Repair lost relationships before expansion.
+
+During refinement, resolve the recorded gaps one by one: fill, revise or ask before removal. Preserve the original brief and decision history through supported workflow invalidation/managed-kit upgrades.
+
+For directions defined by movement, follow [the temporal comparison contract](template-motion.md). Keep its plan, captures, critic observations and actual human feedback distinct.
+
+An answer may include a durable `operationId` to distinguish a new instruction from a replay. Exact retries do not change history; a new explicit reversal becomes the current response for that proposal. Refine feedback returns ownership to representative authoring through normal workflow invalidation. A removal request returns to reference-analysis to revise the exact mapped proposal and record the existing instruction. These are agent repairs, not new unanswered human questions. Counter history and prior responses remain intact.

package/agent/refs/template-from-url.md

@@ -0,0 +1,91 @@
+# Build a library template from a website reference
+
+This workflow reviews a public website, records a buildable specification and handoff, and executes it as a reusable demonstration in the existing Cloudflare library. Read `agent/refs/template-library.md` for the authoritative bundle and storage contract and `design-system/MASTER.md` for applicable design requirements. Follow repository instructions and preserve unrelated working changes.
+
+## Start and establish scope
+
+- Require one clear reference URL. Accept optional page scope, fidelity, template name, and publishing mode without repeatedly asking for already specified choices.
+- Default to close layout and interaction fidelity, fictional demo identity, every distinct public page layout, and publication after verification. Use representative examples for repeated content. Record discovered URLs, inspected URLs, grouped layouts, planned demo routes, and excluded or inaccessible routes; do not claim an exhaustive review from a sample. If a user requests every URL, honor that scope and discuss a concrete access or scale constraint before reducing it.
+- Inspect the supplied URL, the home page, navigation/footer destinations, and an available sitemap. Follow relevant same-site public links. Avoid unbounded calendar, search, filter, tracking, locale, and pagination variants unless they expose a distinct layout or behavior. Record consequential variants.
+- Check the live catalog using the existing gallery/catalog tooling. Choose a new unique theme ID unless the user requested a revision. An ID collision does not authorize replacing an existing template. Choose a release newer than the live catalog using the publisher's release convention, not a hardcoded date.
+- Create a dedicated transient directory, for example `artifacts/template-staging/<id>-<timestamp>/`. Resolve and record its absolute path. Never use a repository root, existing historical artifact, junction, or `src/agent/industry` as the bundle root.
+- Store the inspection evidence, review, plan, handoff, original authored source, recipe files, and assets inside that bundle. The publisher privately archives all bundle files before verified cleanup. After success retain only compact publication metadata locally; complete plans, evidence, media, and recoverable source belong in Cloudflare.
+
+## Inspect rendered pages and behavior
+
+Use an available browser tool and follow its applicable usage instructions. Fetching HTML, a screenshot of the hero, or search summaries alone cannot establish hover, motion, or mobile behavior. Repository browser tooling may support measurements and captures; inspect its interface before using it. Do not report a state or passing check that was not actually observed.
+
+Inspect the full length of each distinct layout at matching desktop and mobile viewports, with tablet and narrow-width checks where layout changes. Useful initial widths are 1440, 768, and 390 CSS pixels; check 320px and determine actual breakpoint behavior by resizing around transitions. Let the reference determine breakpoints rather than treating these sample widths as its CSS breakpoints.
+
+For each page and shared component, record:
+
+| Area | Required observations |
+| --- | --- |
+| Identity and structure | Source URL, page purpose, section order, header/footer variants, links, content hierarchy and relationships |
+| Visual design | Fonts and weights, type scale and line height, content widths, grids, spacing, colors, borders, radii, shadows, image crop/aspect ratio, icons and decoration |
+| Navigation | Hover and focus, dropdown/mega-menu states, sticky/shrinking behavior, active states, mobile drawer open/close, nested navigation, escape and focus behavior |
+| Interactive components | Buttons/cards, accordions, tabs, carousels, filters, galleries/lightboxes, form validation and local demo feedback where applicable |
+| Motion | Fresh-navigation opening, repeat visit, scroll triggers, sticky/pinned sequences, route transitions, hover/pointer effects, timing, easing, distance, overlap, loops and quiet intervals |
+| Responsive behavior | Columns, order, wrapping, visibility, spacing/type changes, crop changes, overflow, touch alternatives, mobile navigation and sticky elements |
+| Accessibility | Semantic controls, keyboard paths, visible focus, names/labels, readable contrast, reduced-motion behavior and access to final content |
+
+Capture full-page and useful detail screenshots with source URL, viewport, state, and timestamp in an evidence index. For defining animations record clips or before/during/after frames with reproducible triggers. Observe the opening from navigation start before readiness waits consume it. Exercise actual interactions; do not invent them from appearance. Inspect normal and reduced-motion modes. Read `agent/refs/template-motion.md` when motion defines the reference, applying its comparison principles without treating customer-site checkpoint files as required template-bundle files.
+
+Separate observed facts, measured/estimated values, inferred implementation choices, and unavailable evidence. Record access failures and the URLs affected. If a critical layout or defining interaction cannot be inspected, complete the independent work and request the needed input; do not publish a supposedly verified replacement based on guesses. Missing noncritical details may use explicitly documented fallbacks.
+
+## Write the review, plan, and handoff
+
+Create `review.md`, `plan.md`, `handoff.md`, and an evidence index inside the bundle. These are substantial artifacts, not just a chat summary.
+
+The review contains:
+
+- A source-to-demo route map covering discovery, layout groups, included variants, and exclusions.
+- A shared design system specification, with evidence references and uncertainty attached to relevant values.
+- Each page's ordered sections and component variants, including text hierarchy, visual relationships, asset requirements, desktop/mobile differences, and destinations/actions.
+- An interaction matrix: page/target, trigger, starting state, resulting state, timing where relevant, keyboard/touch alternative, responsive variation, and evidence reference.
+- A media/font inventory with source, reuse status, licensing/provenance, intended use, and required replacements. Keep observations about reference assets distinct from assets actually cleared for the published demo.
+
+The plan maps those observations to authored pages, shared components, design tokens, assets, and working interactions. Include a route coverage checklist and testable acceptance criteria for each distinctive layout and defining behavior. Document deliberate departures and why they are needed. Sequence implementation by shared shell and representative page, then remaining layouts, interactions, responsive refinement, browser comparison, and publication. Avoid reducing the site to a generic five-page suite or adding unrelated effects.
+
+The handoff must be self-contained enough for another agent to continue from the archived bundle. Include the source URL, agreed scope and defaults, bundle path, review/evidence references, route map, visual and behavior requirements, asset decisions, implementation sequence, acceptance criteria, current status, and the exact existing publish/verify commands. Tell the executing agent to continue through the authorized completion state. Update its status if execution reveals material changes. Writing a handoff does not authorize sending it to another chat.
+
+## Build the complete template
+
+Execute the plan immediately unless the user requested a review or plan only. Use the harness template format, not an unrelated website hosting workflow.
+
+- Author every agreed demo route with complete content and shared design relationships. Use a coherent fictional business; preserve the reference's visual density and content roles while replacing identity, claims, testimonials, contact details, and transactional destinations as appropriate.
+- Use original or appropriately licensed replacement assets with recorded provenance. Do not assume a publicly accessible image or font grants reuse rights. Package demo assets and font notices according to the library contract; avoid hotlinks and dependencies on the reference site's runtime.
+- Implement working local interactions. Forms show clearly fictional/local feedback without contacting the reference business. A demo purchase, booking, or login interaction stays local unless separately requested. Preserve accessible links, keyboard support, touch alternatives, and reduced-motion readability.
+- Provide editable source plus `template.json` and complete `{original, brand}` page recipes. The `original` variant means the authored demo palette, not a copy of the reference's proprietary source. Both variants must function across all routes.
+- Supply valid theme tokens and design metadata, browse/search metadata, route/page roles and priorities, asset digests/byte sizes/provenance, and required font license records. Validate route manifests with the existing harness validator.
+- Use `__VITRIS_PAGE_PAGEID__` for internal links, `__VITRIS_RETURN__` for the gallery return, and the library's brand placeholders in branded recipes. Use content-addressed Cloudflare URLs for media in final recipes. Build a transient preview that resolves these tokens/assets for local checks; never rewrite final recipes into local-only addresses.
+- Inspect a materially different customer brand palette/name/logo in the branded variant to verify that branding is reusable and keeps contrast, typography, spacing, and links working.
+
+## Verify and refine before publication
+
+Write a browser QA report in the bundle. Compare the reference and authored demo at matching viewport sizes and states. Review the complete pages and their defining motion, not only initial screenshots.
+
+Check every demo route and both recipe variants for navigation, keyboard operation, interactive states, mobile/touch usability, narrow-width overflow, missing media/fonts, layout shifts, console/runtime failures, and reduced-motion content access. Verify distinctive interactions against the review's matrix and record tested routes, viewports, states, failures, fixes, and intentional departures.
+
+Fix material visual, behavioral, responsive, and accessibility problems and recheck the affected pages. The existing publisher checks route completeness and loading of selected featured pages at desktop/mobile widths in reduced-motion mode; it does not replace full interaction and visual QA. Do not label untested routes as passed. Preserve failed evidence until it is archived with the successful bundle.
+
+If preview-only or approval-before-publishing was requested, finish the reviewable preview and report its URL, plan/handoff paths, completed checks, and concrete remaining publication step. Otherwise continue without an extra approval question.
+
+## Publish and confirm completion
+
+From the repository root run:
+
+```text
+npm run templates -- publish --bundle ABSOLUTE_STAGING_DIRECTORY
+npm run templates -- verify --id TEMPLATE_ID
+```
+
+Use the exact bundle path and ID for this run. The publisher uploads immutable assets/routes and private recoverable source, verifies hosted routes/loading, conditionally merges the live catalog, updates local metadata, and removes only verified matching staging files. Let it perform cleanup; never manually remove unpublished source or recursively delete artifact junctions.
+
+If a catalog concurrency conflict occurs, read the latest catalog, check whether this run already published, preserve the unique ID and scope, adjust the release if required, and retry the existing publisher once. For other failures diagnose and fix the concrete issue; do not repeatedly mutate the catalog or create duplicate templates to conceal a failed run. If blocked, retain the bundle and report the exact failure and resumable state.
+
+After successful publication, open the default gallery (`npm run templates:gallery`, `http://127.0.0.1:4390/`) and confirm the entry and its hosted routes. Check hosted defining interactions and mobile behavior as well as the command verification. New entries appear through the gallery's live refresh without rebuilding it.
+
+Record compact metadata under `artifacts/templates/`: reference URL, template ID/name, release/revision, hosted demo links, sourceArchive key, route count, and check status. Do not retain a second permanent local template or evidence library. If post-publication checks reveal a defect, restore source into a new transient directory and publish a corrected immutable revision through the existing workflow.
+
+Finish with the template name, gallery/demo links, scope covered, verification outcome, deliberate departures or unresolved limitations, and source archive/restore information for retrieving the detailed review, plan, handoff, and source. Distinguish built, published, and verified states if a step could not finish.

package/agent/refs/template-library.md

@@ -0,0 +1,32 @@
+# Cloudflare template library
+
+The authoritative template library is Cloudflare R2 `vitris-assets/templates/`, served by `https://vitris-templates.jack-896.workers.dev`. The default artifact is `artifacts/templates/gallery.html`; open it through `npm run templates:gallery` (`http://127.0.0.1:4390/`) or `npm run templates -- gallery`. It reads the live remote catalog on opening, every minute while visible, and on focus/network return, so new publications appear automatically. The artifact contains only the gallery UI, its UI font and display/search logic. `src/agent/theme-cloud.json` remains a metadata snapshot for harness selection and accepted design identities; the default artifact does not read that snapshot. Source archives are private R2 objects; the public Worker never serves them. Historical compatibility source retained in the repository is original Vitris material; local template media is not included.
+
+Use this workflow for every new or revised demonstration. Author complete routes, CSS, interactions, photographs, fonts, license notices, original downloads and provenance in a **dedicated transient staging directory**, outside `src/agent/industry`. Do not accumulate permanent local specimen folders, generated originals, portable copies, package snapshots or thumbnail caches. Cloudflare is the final storage destination.
+
+The staging bundle contains `template.json`, page recipe JSON, original source and local asset files. `template.json` contains:
+
+```json
+{
+  "entry": {
+    "theme": { "id": "industry-name", "release": "2026-10-10.1", "name": "Template Name", "description": "...", "tokens": {}, "principles": [], "image": "...", "motion": "...", "freedoms": "...", "brandRule": "...", "license": "..." },
+    "browse": { "family": "Contemporary", "primaryIdentity": "Warm", "identities": ["Warm", "Direct"], "primaryCollection": "Industry templates", "collections": ["Industry templates"], "industry": "Industry", "industries": ["Industry"], "media": "photo-led", "tasks": ["call"], "fit": ["industry"], "order": 0, "new": true },
+    "business": "Fictional Business", "audience": "...", "industry": "Industry", "fonts": [],
+    "pages": [{ "pageId": "home", "path": "/", "label": "Homepage", "role": "home", "group": "Explore", "featured": true, "compareRole": "home", "previewPriority": 0 }]
+  },
+  "recipes": { "home": "pages/home.json" },
+  "assets": [{ "id": "template-photo", "localFile": "media/photo.webp", "file": "photo.webp", "mime": "image/webp", "kind": "image", "sha256": "SHA256_OF_FILE", "bytes": 123, "source": "PROVENANCE", "license": "LICENSE" }]
+}
+```
+
+The example omits full tokens and substantive pages for readability; supply all required design tokens and a validated complete route manifest. Font records additionally supply `licenseFile`, `licenseLocalFile`, `licenseHash`, `family`, `weights` and applicable provenance. Page JSON has `{ "original": "COMPLETE_HTML", "brand": "COMPLETE_HTML" }`; both documents include styles and scripts. Media URLs are immutable `ORIGIN/templates/assets/SHA256/FILE`. Use `__VITRIS_PAGE_PAGEID__` for internal links, `__VITRIS_RETURN__` for gallery return, and `__VITRIS_LOGO__`, `__VITRIS_BRAND_NAME__`, `__VITRIS_CSS_VARS__` in the customer-branded document. Preserve fictional notices and local-only interactions. Do not transfer demo facts or its sitemap into a customer site.
+
+Template maintenance is optional. To maintain your own hosted library, provision your own Cloudflare Worker and R2 bucket using `cloudflare/wrangler.templates.jsonc`; set `VITRIS_TEMPLATE_ORIGIN` to your Worker HTTPS origin and `VITRIS_TEMPLATE_BUCKET` to your bucket. Supply your own `CF_ACCESS_KEY_ID`, `CF_SECRET_ACCESS_KEY`, and `CF_S3_API_ENDPOINT` in ignored local environment configuration. These credentials are never supplied by the harness. The built-in Vitris gallery is a public read service; it grants no account access.
+
+With explicit publication authorization, run `npm run templates -- publish --bundle ABSOLUTE_STAGING_DIRECTORY`. The publisher verifies asset digests and font notices, stores recoverable source privately, uploads content-addressed pages and manifests, checks every public route plus desktop/mobile loading, and changes the catalog pointer only after validation. It uses an ETag condition to avoid replacing concurrent catalog changes. Existing immutable versions remain in R2. It removes only staging files whose bytes still match the verified snapshot. Never delete before publication or manufacture preference labels. The default artifact refreshes the published catalog automatically; no gallery restart is required.
+
+Run `npm run templates -- verify` to check the hosted catalog. For edits, `npm run templates -- restore-source --id ID --out NEW_TRANSIENT_DIRECTORY` retrieves verified source, then republish and discard staging. Preserve frozen baselines. Legacy multipart recovery remains private maintainer tooling.
+
+The gallery requires network access for hosted templates. Display-brand thumbnails are captured in memory when requested; original-palette thumbnails live in Cloudflare. The harness never writes migrated demo thumbnails to its local disk cache, and never silently substitutes an original thumbnail for a customer-branded one.
+
+For an explicitly authorized Unicode-icon migration, restore the template into transient staging, run `npm run templates:icons -- --bundle ABSOLUTE_DIRECTORY` to inspect the plan, then add `--apply` to change the recipe sources. Inspect original and branded pages, desktop/mobile controls, CSS pseudo-elements and dynamic states before publishing a new immutable revision with the existing publisher. The migration keeps arithmetic, keyboard notation and plain-text download content as text. Existing static SVG artwork and typography remain unchanged. Every recipe includes only its used inline SVG or CSS masks; no catalog or icon runtime is loaded. For a media-preserving migration, complete editable recipe documents may reference the existing immutable assets and prior private authoring archive; record that lineage in the new bundle rather than copying template media into harness source.

package/agent/refs/template-motion.md

@@ -0,0 +1,44 @@
+# Preserve a selected template's choreography
+
+When movement defines the chosen direction, inspect the pinned reference in motion before adapting it. Compare pace, easing, travel, overlap, pauses and incoming/outgoing continuity. A working effect or a static screenshot cannot establish expressive equivalence.
+
+At representative/pages, write `agent/decisions/template-motion.json`: version 1, current selectionHash, pinned HTTPS referenceUrl, and moments with id, kind, intent, width, reference/implementation `{path,target,observe}`, and an explained departure where necessary. Supported kinds are load, marquee, pointer-follow, magnetic, scroll, route, drawer and sequence. Locate defining interactions rather than counting effects. Missing reference targets are failures; correct the plan or explain the actual constraint.
+
+Inspect a genuinely fresh browser session from navigation start, then inspect a repeat visit. First-visit greetings, cover lifts and entrance sequences can finish before network/font settlement: use a `load` moment for them, whose recording starts at navigation rather than after readiness. Follow route cover, label/hold, document handoff, incoming lift and destination settlement as one sequence; matching only the outgoing cover misses a major part of the experience. Also inspect an interior portrait and the biography's individual line offsets. Human feedback that the site still feels weaker reopens refinement even when technical checks pass; record the exact rejected moments and never reuse an earlier positive reaction as acceptance.
+
+Every motion comparison plan requires a fresh-session `load` moment. This requires observing the opening, not adding an entrance effect: when the reference is intentionally still, locate its available opening and explain that preserved stillness as a departure rather than inventing a greeting.
+
+When a reference exposes transition states, each side can specify `requiredPhases` (for example `covering`, `revealing`, `idle`). The browser records actual phase changes across document navigation and rejects missing phases. Select the relevant phases from observed behavior; do not invent reference state labels. Scroll setup places a below-fold target just outside the viewport, so preparation does not consume its entrance before recording.
+
+Exercise a keyboard link activation during the first-visit reveal, not only clicks after settlement. Arrival and outgoing covers must serialize; the shared runtime queues that request until arrival settles. A live reduced-motion or pause change cancels decorative travel. Settled focus/layout checks wait for the real arrival to finish, while navigation-start recordings retain its opening evidence.
+
+Browser verification records paired WebM clips, before/during/after frames and sampled browser states at the same viewport/input. Current plan, selection, build and capture bytes are bound into the report. Preserve failed attempts. Critic reviews add `templateMotion:{planHash,distHash,moments:[{id,verdict,timing,easing,continuity,inputAlternatives}]}`. Open the actual captures before writing observations. Diagnose slow or abrupt pacing, jumpy followers, generic entrances, reveal cuts and motion that competes with reading. A pass without located temporal evidence fails. Explain deliberate departures; never manufacture human preferences.
+
+Show the paired comparison and usable preview to the owner, and carry their actual response into refinement. Engineering checks, agent assessment and human acceptance remain separate.
+
+Use the opt-in `data-island="experience"` runtime only for choreography selected by the direction. Markers support bounded pointer/keyboard chapter previews, restrained magnetic actions, portrait drift, pixel-speed marquee settlement and reversal, supporting intro lines, and guarded route-cover navigation. An optional arrival marker also enables a shared first-visit greeting and complete incoming lift across native document navigation. Customer HTML/CSS still owns the composition, responsive inline imagery, menu and sequence. The kernel supplies no customer claims, images or design approval. Its motion policy, media-query and disposal handling must accompany customer pause, reduced-motion and immediate static content. Retain ordinary navigation when storage/runtime support fails; assess that departure explicitly.
+
+Motion plans are downstream authoring outputs. They must not reopen reference analysis, direction or copy planning. Use supported prepare/complete and repair routing; never rewrite workflow state or evidence to bypass a gate.
+
+To show a current comparison, run "vitris-motion-view --site SITE --out ARTIFACT_DIRECTORY --report browser --port PORT". The viewer verifies capture bytes before copying QA media; use a new output directory for each run. It contains no reusable template demo assets.
+
+Whole-route recordings now sample actual opening render states before waiting for font settlement. This preserves evidence for fast opening accents without accepting inert targets; geometry and forward traversal still wait for settled fonts.
+
+Shared marker examples (the authored CSS supplies layout and final/static states):
+
+| Relationship | Markup |
+| --- | --- |
+| Chapter cover | Link with `data-experience-image="/media/cover.webp"` and `data-experience-name="Chapter"`; fixed preview container with `data-experience-preview`, a decorative `img`, and `data-visible="false"` |
+| Faster action disk | Separate `data-experience-cursor` container with `data-experience-label` text |
+| Magnetic action | `data-experience-magnetic` on the actual usable link/button |
+| Portrait depth | `data-experience-drift=".13"`, a crop-safe `data-experience-drift-max`, and the parent section ID in `data-experience-trigger` |
+| Interior portrait | `data-experience-drift-mode="center"` with `.07` drift and forty-pixel travel; clip an overscanned image inside its frame |
+| Marquee pace | `data-experience-marquee-speed` on a CSS-animated track with two equal copies; choose the measured reference speed |
+| Closing seam | `data-experience-seam` on a section; CSS transitions its decorative edge when `.experience-seen` is added |
+| Supporting introduction | `data-experience-intro` around the selected `data-experience-line` children |
+| Route cover | `data-experience-transition` on a decorative fixed cover; an optional link `data-experience-title` supplies its destination label |
+| First visit and full route arrival | Add `data-experience-arrival="Hello."` to that cover. The compiler arms a before-paint bootstrap; CSS must show the resting cover under `html[data-experience-arrival]`. Runtime holds a first-visit greeting for 420ms and lifts the curve for 800ms; later route handoffs lift immediately. The bootstrap fails open after 3.5s if runtime loading fails. |
+| Saved global pause | The arrival cover's optional `data-experience-pause-key` names the customer's localStorage pause key (default `vitris-experience-paused`); its value `true` skips the cover before first paint. |
+| Opening movement | Selected `data-experience-opening` children move thirty-two pixels over one second as the cover lifts; final text remains available and this must not become a whole-page reveal. |
+
+Floating previews are limited to fine hover inputs wider than 1024px by default. Supply responsive inline covers and keep ordinary semantic links. Mark decorative duplicated identity text and preview imagery as hidden from assistive technology. Set `document.documentElement.dataset.motionPolicy="off"` when the user's global pause is active; customer CSS must also settle hover, seam, marquee and native document transitions. Reduced motion alone is not the complete input policy.

package/agent/refs/theme-selection.md

@@ -0,0 +1,13 @@
+# Selected visual identity (opt-in)
+
+`launch.json.themeSelection: {version: 1, enabled: true}` adds a persisted prerequisite before reference analysis. Absence keeps the existing workflow. Harvest and the existing media audit identify branding; business/narrative work remain shared.
+
+For general template browsing, use the default `artifacts/templates/gallery.html` through `npm run templates:gallery` at `http://127.0.0.1:4390/`. It reads Cloudflare's live catalog and automatically includes future publications; retired local galleries are on D:. For authoring or revising library demonstrations, follow `agent/refs/template-library.md` and publish complete demos/assets to Cloudflare. A library export does not submit a choice to a customer site; use the site's picker or the supported select/import commands below to record an explicit choice.
+
+An `awaiting_user` result is normal. Open the returned picker, or use `vitris-themes serve --site ABSOLUTE_SITE`. Return control to the user without repair attempts, polling, extra agents or an inferred choice. A draft is not submission. To record an explicit chat choice use `vitris-themes select --site ABSOLUTE_SITE --theme ID --notes-file ABSOLUTE_FILE --source user-chat`. Preserve the exact note. Delegated choices require `--source agent-delegated --delegation "exact authorization"`; simulations use `test-simulation` and never represent human preference.
+
+The picker saves input locally. The next supported workflow invocation consumes it; saving does not invoke a model. New picker choices include adaptation answers about section preservation, AI images and emotional priorities. Read `refs/template-adaptation.md` when those answers are present. Image/removal approvals follow the recorded user policy. Imported JSON uses the same validation via `vitris-themes import --site ABSOLUTE_SITE --file ABSOLUTE_JSON`; legacy selections remain compatible.
+
+Use the selected identity and effective semantic tokens in CURRENT.md. Write theme/defaults.json during direction, within that node's normal ownership. Optional typeStep0 through typeStep5 and sectionY extend the legacy compiler defaults. Match typography, rhythm, surfaces and geometry; preserve original logo and required brand colors. A derived readable companion is permitted while retaining the exact brand accent elsewhere. Re-author factual content and visitor tasks. A selected template's emotional relationships, major sections and interactions are design requirements when the adaptation answers preserve them; sparse source content must not silently erase them. Never import fictional specimen claims. Textual --theme, assigned directions and later explicit user amendments retain authority. Explain material conflicts.
+
+Theme revisions use the same select/import command with a new operation and the current previousSelectionHash. Normal reconciliation invalidates affected design work and reviews without resetting attempts, capture bytes or history. Do not change STATE by hand or rerun harvest to choose different typography.

package/agent/refs/ui-ux.md

@@ -0,0 +1,7 @@
+# UI and UX
+
+Service and professional visitors need to understand suitability, judge trust, compare the options that matter, see the process, find practical details, and take the next step. Not every journey becomes its own section, and a contact form is not required.
+
+Use plain labels, predictable controls, and feedback the visitor can act on. [Nielsen's heuristics](https://www.nngroup.com/articles/ten-usability-heuristics/) are principles, not a layout. Keep the accepted direction. Do not add a section quota or a motif quota.
+
+When images are scarce, explain the work. When one service matters more, show that difference. Repetition is fine when each repeat does the same job.

package/agent/refs/usability.md

@@ -0,0 +1,5 @@
+# Usability
+
+Help the visitor finish a task. Name the action in their words. Show what happens after they take it. If a field fails, say what to fix.
+
+Keep the mobile order the same as the task: the reason, then the action. Do not hide the practical fact inside a slogan. A restrained page is a valid design. An unusual composition still has to be operable.

package/agent/refs/variant-directions.md

@@ -0,0 +1,20 @@
+# Variant direction set
+
+You are planning five complete website directions for one business. You are not implementing pages and you are not choosing a winner.
+
+Read the frozen shared evidence, the narrative brief, the versioned reference-analysis, inspected media, and any operator theme request. Each brief must be an evidenced business idea for this customer.
+
+Do not start from a mandatory five-category costume list (quiet editorial, bold product, dense index, photographic, type-led). Those labels are optional vocabulary after the idea exists. A candidate that exists only to fill a style bucket fails. Typography, color, density, and motifs follow the idea. Two strong interpretations may share a typeface while differing in hierarchy and media.
+
+For each brief state: centralIdea; the strongest real evidenceIds that support it; visitorExperience; the hierarchy it produces; visualExpression of that hierarchy; plus the remaining visual-system fields. Explain why the direction fits this business and its actual assets. Do not invent staff, customers, projects, or testimonials.
+
+An operator `--theme` is first-class. Preserve the exact request text. Scope is explicit in operator-request.json:
+- `themeScope=one`: exactly one brief may center that request; the others remain different ideas for the same facts.
+- `themeScope=all`: every brief must honor the request.
+Do not silently convert an explicit theme into an at-most-one rule when the operator asked for all, and do not invent a theme when none was requested.
+
+Shared facts, offers, routes, and media inventory stay identical. Diversity is judged on meaningful choices and later on rendered production representatives, not on five typeface names.
+
+Private HTML sketches may be written when requested. They are not finished variants and cannot be quality-approved. Production homepage plus interior compiled through the site pipeline is the quality artifact.
+
+Write exactly five briefs to the path given in CURRENT.md.

package/agent/refs/write.md

@@ -0,0 +1,6 @@
+# write
+
+Compatibility entrypoint. Workflow graph uses copy.md for this task; load it only when needed. The selected site direction governs aesthetic choices. Preserve factual accuracy, usable interactions, and accessible markup. Do not add section/image quotas or a fixed motif count.
+
+
+Whole-page motion responsibility: for new/reauthored routes use motionPlan v2 and read `motion-page`. Cover every authored route, including expansion/contact; locate opening, development, connected quiet intervals and closing in actual IDs. Keep essential content/actions static and readable. Representative runtime success or two colocated effects is insufficient. Inspect normal desktop/mobile full journeys and reduced/static views; critique distribution, continuity, inert stretches, competition and meaningful differences among routes with located evidence. Return actionable repairs, preserving operator off and historical records. Human preference stays unset.

package/agent/request.json

@@ -0,0 +1,11 @@
+{
+  "mode": "build",
+  "theme": "",
+  "priorities": [
+    "design quality",
+    "faithful migration",
+    "functionality",
+    "low intervention",
+    "time and cost"
+  ]
+}

package/agent/workflow.json

@@ -0,0 +1,4 @@
+{
+  "schemaVersion": 1,
+  "executionMode": "active-agent"
+}

package/bin/api/agent/artifacts.js

@@ -0,0 +1,38 @@
+import {
+  QUALITY_DIMENSIONS,
+  SOURCE_PATHS,
+  STUDY_CAPTURE_HEIGHT,
+  STUDY_CAPTURE_VIEWPORTS,
+  acquirePathLock,
+  cleanStaleTmp,
+  files,
+  fingerprint,
+  isPidDead,
+  json,
+  recoverPendingTransactions,
+  recoverableReplace,
+  replacePath,
+  save,
+  sha256,
+  sourceHash,
+  within
+} from "../../chunks/chunk-T6PE4KN4.js";
+export {
+  QUALITY_DIMENSIONS,
+  SOURCE_PATHS,
+  STUDY_CAPTURE_HEIGHT,
+  STUDY_CAPTURE_VIEWPORTS,
+  acquirePathLock,
+  cleanStaleTmp,
+  files,
+  fingerprint,
+  isPidDead,
+  json,
+  recoverPendingTransactions,
+  recoverableReplace,
+  replacePath,
+  save,
+  sha256,
+  sourceHash,
+  within
+};

package/bin/api/agent/evaluate.js

@@ -0,0 +1,55 @@
+import {
+  PARENT_DIVERSITY_AXES,
+  PARENT_DIVERSITY_REF_PATHS,
+  REVIEW_CRITERIA,
+  directionRenderSubject,
+  evaluateParentStudyRender,
+  evaluateV2,
+  parentDiversityIdentities,
+  parentDiversityIdentityPaths,
+  parentDiversityReviewSubject,
+  parentDiversitySourceSubject,
+  reviewSubject,
+  validateParentDiversityReview
+} from "../../chunks/chunk-3CTBXY5K.js";
+import "../../chunks/chunk-DSS2U2OM.js";
+import "../../chunks/chunk-M4LNHYYR.js";
+import "../../chunks/chunk-DRJQ4OOU.js";
+import "../../chunks/chunk-PRLL7B63.js";
+import "../../chunks/chunk-5OOPJNGN.js";
+import "../../chunks/chunk-BBV7PMFC.js";
+import "../../chunks/chunk-TY33XMHW.js";
+import "../../chunks/chunk-R7YELY3C.js";
+import "../../chunks/chunk-BIEDSEL2.js";
+import "../../chunks/chunk-T7DGRVTP.js";
+import "../../chunks/chunk-AUO5I56E.js";
+import "../../chunks/chunk-6H3T46F5.js";
+import "../../chunks/chunk-M2ETYSVJ.js";
+import "../../chunks/chunk-FOXUQXTV.js";
+import "../../chunks/chunk-IKNMBGGD.js";
+import "../../chunks/chunk-WEFDVXFX.js";
+import "../../chunks/chunk-E5Y46VBX.js";
+import "../../chunks/chunk-4GZCAWWK.js";
+import "../../chunks/chunk-ANMJRJQ5.js";
+import "../../chunks/chunk-HNORQ74T.js";
+import "../../chunks/chunk-YCVGD2CG.js";
+import "../../chunks/chunk-LKN75JGA.js";
+import "../../chunks/chunk-YYPYYOEV.js";
+import "../../chunks/chunk-GZDLXYZV.js";
+import "../../chunks/chunk-G7MNMULR.js";
+import "../../chunks/chunk-T6PE4KN4.js";
+import "../../chunks/chunk-7FS67SRF.js";
+export {
+  PARENT_DIVERSITY_AXES,
+  PARENT_DIVERSITY_REF_PATHS,
+  REVIEW_CRITERIA,
+  directionRenderSubject,
+  evaluateParentStudyRender,
+  evaluateV2,
+  parentDiversityIdentities,
+  parentDiversityIdentityPaths,
+  parentDiversityReviewSubject,
+  parentDiversitySourceSubject,
+  reviewSubject,
+  validateParentDiversityReview
+};

package/bin/api/agent/grade.js

@@ -0,0 +1,51 @@
+import {
+  gradeAll,
+  gradeBrand,
+  gradeComponents,
+  gradeHarvest,
+  gradeInterpret,
+  gradeLaunch,
+  gradeNode,
+  gradePages,
+  gradePreview,
+  gradeResearch
+} from "../../chunks/chunk-3CTBXY5K.js";
+import "../../chunks/chunk-DSS2U2OM.js";
+import "../../chunks/chunk-M4LNHYYR.js";
+import "../../chunks/chunk-DRJQ4OOU.js";
+import "../../chunks/chunk-PRLL7B63.js";
+import "../../chunks/chunk-5OOPJNGN.js";
+import "../../chunks/chunk-BBV7PMFC.js";
+import "../../chunks/chunk-TY33XMHW.js";
+import "../../chunks/chunk-R7YELY3C.js";
+import "../../chunks/chunk-BIEDSEL2.js";
+import "../../chunks/chunk-T7DGRVTP.js";
+import "../../chunks/chunk-AUO5I56E.js";
+import "../../chunks/chunk-6H3T46F5.js";
+import "../../chunks/chunk-M2ETYSVJ.js";
+import "../../chunks/chunk-FOXUQXTV.js";
+import "../../chunks/chunk-IKNMBGGD.js";
+import "../../chunks/chunk-WEFDVXFX.js";
+import "../../chunks/chunk-E5Y46VBX.js";
+import "../../chunks/chunk-4GZCAWWK.js";
+import "../../chunks/chunk-ANMJRJQ5.js";
+import "../../chunks/chunk-HNORQ74T.js";
+import "../../chunks/chunk-YCVGD2CG.js";
+import "../../chunks/chunk-LKN75JGA.js";
+import "../../chunks/chunk-YYPYYOEV.js";
+import "../../chunks/chunk-GZDLXYZV.js";
+import "../../chunks/chunk-G7MNMULR.js";
+import "../../chunks/chunk-T6PE4KN4.js";
+import "../../chunks/chunk-7FS67SRF.js";
+export {
+  gradeAll,
+  gradeBrand,
+  gradeComponents,
+  gradeHarvest,
+  gradeInterpret,
+  gradeLaunch,
+  gradeNode,
+  gradePages,
+  gradePreview,
+  gradeResearch
+};

package/bin/api/agent/graph.js

@@ -0,0 +1,16 @@
+import {
+  initialState,
+  invalidate,
+  isPreviewReady,
+  nextNode,
+  parseGraphYaml,
+  validateGraph
+} from "../../chunks/chunk-BBV7PMFC.js";
+export {
+  initialState,
+  invalidate,
+  isPreviewReady,
+  nextNode,
+  parseGraphYaml,
+  validateGraph
+};