ss-build

# Build with the composed StyleSeed method ## Registry-first artifact boundary When `.styleseed/project.json` and `.styleseed/artifacts/index.json` exist, resolve the requested artifact ID first, then read only `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json`. Never fall back to the global legacy bundle for a registry project. Legacy projects may use `.styleseed/effective-rules.md` only when no registry exists. The build method is the product. Score and screenshots are auxiliary evidence, not the source of design judgment. ## Step 1 — Establish the rule set before code If either `.styleseed/project.json` or `.styleseed/artifacts/index.json` exists, require a complete, valid registry and resolve the requested artifact with the installed resolver's `scripts/resolve-context.mjs --project-root . --artifact <artifact-id> --agent <agent>`. Read `.styleseed/bundles/<artifact-id>.md` and preserve `.styleseed/manifests/<artifact-id>.json` as provenance. Do not create `STYLESEED.md`, restart setup, or use a legacy bundle because a registry is incomplete, invalid, or lacks a compiled output. Resolve missing scope with the user. For changes spanning multiple artifacts, resolve and check each affected artifact separately. Only when neither registry file exists, use the legacy path: if `STYLESEED.md` is missing, run `/ss-setup` before UI code; otherwise preserve it. Invoke `/ss-resolve` (Claude Code) or `$ss-resolve` (Codex) with `--from-lock STYLESE...