create-yss-spec 2.2.10 → 3.0.1

package/template/.hermes/skills/archify/references/brand-marks.md

@@ -1,65 +0,0 @@
-# Brand marks
-
-Use a brand mark only when a real product, provider, model family, channel, or
-service identity helps the reader. Semantic `type` still explains what the node
-does; `brand` explains whose product it is.
-
-## Agent decision path
-
-1. Search the built-in catalogue when the request names a recognizable brand:
-
-   ```bash
-   node bin/archify.mjs brands "Claude" --json
-   ```
-
-2. Put the returned canonical ID in the node, participant, or state:
-
-   ```json
-   {
-     "id": "planner",
-     "type": "backend",
-     "label": "Claude",
-     "brand": "claude"
-   }
-   ```
-
-3. If there is no catalogue match and the user supplied the official website,
-   capture its icon explicitly:
-
-   ```bash
-   node bin/archify.mjs brands capture "https://partner.example.com" --json
-   ```
-
-   Put the command's digest-pinned `brand` value in the authored node:
-
-   ```json
-   {
-     "id": "partner",
-     "type": "external",
-     "label": "Partner portal",
-     "brand": {
-       "url": "https://partner.example.com",
-       "sha256": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
-     }
-   }
-   ```
-
-4. If there is no match and no user-provided URL, omit `brand`. Do not invent a
-   URL or silently assign a visually similar company.
-
-Known-brand URLs resolve to the bundled vector instead of using the network.
-Unknown URL capture accepts only bounded raster image formats, blocks
-credentials, nonstandard public ports, and private or link-local destinations,
-uses bounded concurrency and one total deadline, and returns the captured
-content digest. Later render and validate operations require that exact digest;
-blocked, unavailable, changed, oversized, or unsafe content fails closed instead
-of silently changing the artifact.
-
-The final artifact never fetches a brand asset when opened. Preset vectors and
-digest-verified captured site icons remain embedded in SVG, PNG, WebP, JPEG,
-Share Card, and WebM exports.
-
-Use `node bin/archify.mjs brands --json` to inspect all canonical IDs, aliases,
-categories, domains, and provenance. Current categories cover AI, cloud,
-engineering, data, collaboration, business systems, channels, languages, and
-frameworks.

package/template/.hermes/skills/archify/references/delivery-contract.md

@@ -1,112 +0,0 @@
-# Delivery contract
-
-## Validate and deliver
-
-Use `validate` after every candidate edit. Use final atomic delivery only after the candidate is frozen:
-
-```bash
-node bin/archify.mjs deliver <type> <candidate.json> <output.html> --quality showcase --json
-```
-
-Deliver reads the specification once, writes those exact bytes to a private same-directory candidate snapshot, renders that snapshot, runs the complete artifact checker, and only replaces the target after all artifact checks pass. The JSON receipt includes SHA-256 and byte counts for both `specification` and `artifact`. Renderer, checker, receipt, or commit failure exits non-zero, removes private state, preserves the previous trusted artifact, and never invokes an opener.
-
-Run `visual-check` only after `deliver` exits zero for the current candidate. If
-delivery fails and the output path already exists, that path still names the
-previous trusted artifact; running `visual-check` then would measure and capture
-stale output, not the rejected candidate. Report the delivery diagnostics and
-repair the source before collecting new visual evidence.
-
-The delivery interface exposes three separate claims:
-
-1. `deliver` proves deterministic artifact checks and byte identity.
-2. `visual-check` collects automated browser evidence from the exact artifact.
-3. Perceptual visual review records a human or image-capable reviewer's judgment.
-
-Passing one claim never implies either of the others. Never claim that the deterministic receipt includes visual review. It does not include browser evidence either.
-
-## Automated browser evidence
-
-After delivery, inspect the exact trusted HTML without rerendering or modifying
-it:
-
-```bash
-node bin/archify.mjs visual-check <output.html> --json
-```
-
-The zero-dependency command uses Chrome/Chromium through the DevTools pipe. It
-measures light-theme containment at 1440×900, 1600×1000, 1920×1080, and
-2048×1320, then captures light/dark screenshots at 1440×900 and 2048×1320. It
-writes four PNG sidecars, one relative-path HTML contact sheet, and one JSON
-receipt beside the artifact. The receipt binds the source artifact SHA-256 and
-byte count, identifies `evidenceKind: "automated-browser"`, records READ plus
-Still runtime state, and always reports `visualReview: "pending"`; automated
-browser evidence cannot claim perceptual review.
-
-`browser_evidence` in the handoff records only the outcome of this automated command:
-
-- `passed` maps from exit 0 and receipt `status: "pass"` only after every required measurement and capture completes and passes.
-- `failed` maps from exit 1 and receipt `status: "fail"` when the inspection finds a defect, the command fails, or a runtime/capture error leaves the evidence incomplete.
-- `skipped` maps only from exit 2 and receipt `status: "skipped"` when Chrome/Chromium is unavailable and the inspection does not run.
-
-Runtime or capture failures leave incomplete evidence and must not be normalized to `skipped`. Failed or skipped capture runs remove stale
-image/contact-sheet sidecars rather than presenting prior evidence as current.
-They do not invalidate an already successful deterministic delivery, and they
-do not turn a perceptual visual review into passed or failed. Retry an
-environmental failure through the supported command in a browser-capable
-execution context when practical. Keep the packaged transport unchanged unless
-the failure reproduces through that seam in a capable environment.
-
-## Optional opening
-
-Add `--open` only when the user wants an immediate local preview. It runs after that atomic commit, uses one argument-array OS opener with a five-second bound, and records `open.status`. Keep it off for CI, unattended agents, and non-interactive environments. Failure or unsupported opening does not invalidate delivery; its status proves only whether the local opener invocation succeeded.
-
-## Last-Good Live Preview
-
-For an active desktop authoring loop only:
-
-```bash
-node bin/archify.mjs preview <type> <input>.json <output>.html --quality showcase
-```
-
-Preview watches one explicit input on loopback, binds each stable digest to a private snapshot, and advances only after the existing verified delivery pipeline passes. Invalid, half-written, deleted, or superseded input leaves the previous verified revision on screen and on disk. Identical bytes do not rebuild or reload.
-
-The preview runtime ships inside the zero-dependency Skill ZIP and must work without `node_modules`.
-
-Never start it by default. Do not use it for CI, unattended agents, remote sharing, or mobile use. `--no-open` is only for a user who will open the printed local URL or for loop testing. Stop it with Ctrl-C before handoff. Server state, port, source path, diagnostics, error text, and reload tokens must never enter the generated artifact or any export.
-
-## Perceptual delivery gate
-
-Automated validation and browser evidence cannot prove visual polish. After deterministic delivery, inspect the actual HTML in a capable browser or render the evidence screenshots with an image reader. Check both themes when changed, the default READ view, line crossings/corridors, label masks, node/card fit, focus/search/passport closure, and export cleanliness.
-
-For the default standalone desktop viewer, measure 1440×900, 1600×1000, and 1920×1080. When the artifact is intended for a large desktop display, also measure 2048×1320. A first-screen pass requires `document.documentElement.scrollWidth <= window.innerWidth` and `scrollHeight <= window.innerHeight` at every checked size. At the largest checked viewport, inspect the rendered composition for a conspicuous empty lower band: the main panel and necessary conclusion cards should use the available height as a balanced whole, not collapse into a shallow strip. If a desktop viewport overflows, repair the authored composition by removing only genuinely redundant content or compacting spacing before shrinking nodes, labels, or the main panel. Do not hide overflow, clip content, introduce an internal diagram scroller, or reduce node/label typography to make the measurement pass. Narrow/mobile containment may retain vertical page scrolling.
-
-A manual browser record is supplementary to the automated status. Reproducing the same coverage requires all four exact viewport measurements, both endpoint themes, and an artifact-bound record of the inspected SHA-256 and byte count. It never changes `browser_evidence`: when Chrome/Chromium is unavailable, that status remains `skipped` even when the manual browser record is complete and `visual_review: passed`; an automated `failed` result likewise remains `failed`. An unconstrained browser glance can support perceptual review only.
-
-Report exactly one truthful status:
-
-- `visual_review: passed` — only after inspecting the rendered artifact.
-- `visual_review: skipped (image reader unavailable)` — when no capable visual surface exists.
-- `visual_review: failed` — with the concrete visible defect.
-
-Use `correction_rounds: 0`, `correction_rounds: 1`, or `correction_rounds: 2`; never exceed a maximum of two focused correction rounds. Never report `visual_review: passed` without inspecting the artifact.
-
-If visual review changes the candidate, validation and delivery must run again because the prior frozen specification receipt is no longer current.
-
-## Handoff receipt
-
-Return:
-
-```text
-diagram_type: architecture|workflow|sequence|dataflow|lifecycle
-output: /absolute/path/to/file.html
-specification_sha256: <receipt value>
-artifact_sha256: <receipt value>
-validation: 9/9 showcase, 0 errors, 0 warnings
-browser_evidence: passed|failed|skipped
-visual_review: passed|skipped (image reader unavailable)|failed
-correction_rounds: 0|1|2
-```
-
-Derive `browser_evidence` only from the latest artifact-bound `visual-check` receipt. Record any manual browser work separately with its artifact binding, viewport/theme scope, and observations; never use it or `visual_review` to overwrite the automated status.
-
-Opening, preview status, Share Cards, and other viewer exports are not validation claims.

package/template/.hermes/skills/archify/references/viewer-runtime.md

@@ -1,45 +0,0 @@
-# Viewer Runtime reference
-
-Read this only when the user asks for a reader-facing capability. Ordinary generation does not require implementing or re-documenting these features; they are already in the generated HTML.
-
-## Exploration
-
-- Diagram Guide lists current actions and shortcuts.
-- Reading Depth starts at READ at the default 100% scale, reveals FULL detail at 175%, and falls back to MAP only below 100%. Focus, story, route, and semantic interactions reveal their exact facts at any scale.
-- Semantic Lens summarizes selected node/relationship kinds without changing authored geometry.
-- Intent Trace previews a fine-pointer or keyboard target before committed focus.
-- Node Finder searches labels and stable IDs.
-- Semantic Passport opens on focus, shows authored upstream/downstream facts, supports a copyable deep link, has an explicit close action, closes on true outside activation and Escape, and never enters canonical export.
-- Semantic Radar mirrors the visible viewport and authored graph without becoming a second source of truth.
-- Direct Relationship Pin makes a unique compiled relationship operable while preserving the authored line and stable relationship identity. It must fail closed on conflicting source/target/label/ID metadata.
-- Route Probe resolves exactly two endpoints over authored directed relationships. It never infers a route from geometry.
-
-## Guided views and story
-
-`meta.views` may define at most five curated chapters using stable node IDs. The Named Chapter Rail, Chapter Delta Preview, Story Beat Navigator, Story Follow Camera, Story Director Strip, Story Horizon, and Shareable Story Moment links all derive from that one authored array; none owns parallel topology or layout.
-
-Story transitions classify only the exact relationship between adjacent authored stops: forward, reverse, multiple, or grouped/no direct link. Never infer a transitive edge, verb, causality, or runtime behavior from proximity, kinds, or story order. Playback is reader-started, bounded, stale-safe, and motion-governed.
-
-## Motion and presentation
-
-`meta.animation: "trace"` enables a finite reader-controlled Live/Still trace. Static is the default. Still, reduced motion, page hiding, print, and canonical export preserve complete static meaning. Presentation Stage changes viewer chrome and framing, never authored geometry. This is not a mobile product feature; narrow layouts get containment only.
-
-## Canonical exports
-
-The export menu can copy/download full-diagram PNG, download JPEG/WebP, download a dual-theme SVG, and record a trace-enabled WebM. Viewer state—Guide, Lens, finder, focus, route, story, camera, radar, presentation, motion ownership, and temporary overlays—must be removed from canonical export.
-
-### Share Card
-
-The optional 1200×630 Share Card PNG is for README, release, social, or launch previews. It uses the current theme and visual preset, contains the complete canonical diagram without cropping, and never claims validation. Copy Share Card reuses the same canonical PNG when clipboard image writes are supported.
-
-### Route Share Card
-
-After a real directed Route Probe resolves, the reader may use **Export → Route Share Card**. It reuses the exact ordered route snapshot and the shared Share Card seam: `format=share-card`, `variant=route`. The isolated clone may use only static `data-share-route-*` decoration. It is download-only, fails closed for stale/unreachable/conflicting routes, and never becomes the canonical artifact.
-
-### Reach Share Card
-
-After a non-empty authored reachability query, the reader may use **Export → Reach Share Card**. It consumes the already resolved upstream/downstream node and edge set without rerunning traversal: `format=share-card`, `variant=reach`. The isolated clone may use only static `data-share-reach-*` decoration. It is download-only. Call it authored reachability—not impact, blast radius, breakage, or runtime causality.
-
-## Truth boundary
-
-Viewer exports are communication assets. They do not replace the checked HTML, the deterministic delivery receipt, or a real visual review. Do not add a hosted service, storage surface, dependency, schema branch, or mobile product surface for these viewer-only capabilities.

package/template/.hermes/skills/archify/renderers/architecture/grid.mjs

@@ -1,62 +0,0 @@
-/** Grid placement for architecture IR (#8). Not auto-layout — fixed cell math only. */
-
-export const DEFAULT_GRID = {
-  mode: 'grid',
-  origin: [40, 80],
-  cols: 4,
-  gapX: 30,
-  gapY: 40,
-  cellW: 130,
-  cellH: 64,
-};
-
-export function gridLayout(arch) {
-  const raw = arch.layout;
-  if (!raw || raw.mode !== 'grid') return null;
-  return { ...DEFAULT_GRID, ...raw };
-}
-
-export function resolveComponentPos(component, grid) {
-  if (Array.isArray(component.pos) && component.pos.length === 2) {
-    return component.pos;
-  }
-  if (!grid) return [NaN, NaN];
-  if (!Number.isInteger(component.row) || !Number.isInteger(component.col)) {
-    return [NaN, NaN];
-  }
-  const [ox, oy] = grid.origin;
-  const stepX = grid.cellW + grid.gapX;
-  const stepY = grid.cellH + grid.gapY;
-  return [ox + component.col * stepX, oy + component.row * stepY];
-}
-
-export function validateGridPlacement(arch, grid, problems) {
-  if (!grid) return;
-  if (arch.layout !== undefined && arch.layout.mode !== 'grid') {
-    problems.push('layout.mode must be "grid" when layout is set (free placement omits layout entirely).');
-    return;
-  }
-  const seen = new Map();
-  for (const c of arch.components ?? []) {
-    const hasPos = Array.isArray(c.pos) && c.pos.length === 2;
-    const hasCell = Number.isInteger(c.row) && Number.isInteger(c.col);
-    if (hasPos) continue; // pos wins; row/col are optional hints only
-    if (!hasPos && !hasCell) {
-      problems.push(`Component "${c.id}" needs pos [x,y] or grid row/col when layout.mode is "grid".`);
-      continue;
-    }
-    if (c.row < 0 || c.col < 0) {
-      problems.push(`Component "${c.id}" row/col must be non-negative integers.`);
-      continue;
-    }
-    if (c.col >= grid.cols) {
-      problems.push(`Component "${c.id}" col ${c.col} exceeds layout.cols ${grid.cols} (valid: 0..${grid.cols - 1}).`);
-    }
-    const key = `${c.row},${c.col}`;
-    if (seen.has(key)) {
-      problems.push(`Components "${seen.get(key)}" and "${c.id}" share grid cell row ${c.row} col ${c.col}.`);
-    } else {
-      seen.set(key, c.id);
-    }
-  }
-}