ss-resolve

# Resolve effective StyleSeed context Use the bundled `scripts/resolve-context.mjs`; do not hand-compose the rule stack. 1. Resolve the project boundary first: if either `.styleseed/project.json` or `.styleseed/artifacts/index.json` exists, require a complete, valid registry. Do not fall back to `STYLESEED.md` on a registry error. Only use that lock when no registry exists. 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`. 6. Use `--check` to detect context drift without rewriting files. For installation or project-health questions, run the read-only diagnostic first: ```bash node <installed-ss-resolve>/scripts/styleseed-doctor.mjs --project-root . --json ``` It checks the local distribution inventory, project configuration, compiled rules, and stored evidence against current inputs. Use `--artifact <id>` to ...