ss-resolve

# Resolve effective StyleSeed context Use the bundled `scripts/resolve-context.mjs`; do not hand-compose the rule stack. 1. Read `STYLESEED.md` when it exists. Confirm missing required selections with the user. 2. Keep the working directory at the user's project root. Invoke the script by its installed path; do not `cd` into the skill directory. 3. Legacy single-artifact projects should prefer `--from-lock STYLESEED.md`. Registry projects use `.styleseed/project.json` plus `.styleseed/artifacts/*.json` and must resolve with `--artifact` or `--all`; in registry mode, edit project-owned config instead of passing selection overrides. 4. Read the emitted bundle before building: legacy writes `.styleseed/effective-rules.md`; registry writes `.styleseed/bundles/<artifact-id>.md`. 5. Preserve the manifest output: legacy uses `.styleseed/manifest.json`; registry uses `.styleseed/manifests/<artifact-id>.json`. 5. Use `--check` to detect context drift without rewriting files. ```bash node <installed-ss-resolve>/scripts/resolve-context.mjs \ --from-lock STYLESEED.md \ --agent codex ``` Registry project: ```bash node <installed-ss-resolve>/scripts/resolve-context.mjs \ --project-root . \ --artifact app-dashboard \ --agent codex ``` Without a lock: ```bash node <installed-ss-resolve>/scripts/resolve-context.mjs \ --agent claude \ --grammar operations-console \ --adapter product-ui \ --domain saas \ --page dashboard \ --recipe enterprise-workbenc...