stack-effect@0.16.0

Minor Changes

• 3626e79: Compose catalogs with a repeatable --catalog flag. init and create save the selection to stack.effect.json, and later commands reuse it.

  For example, create a catalog project from the hosted author catalog:

  bunx stack-effect@latest create my-catalog --yes \
    --catalog official \
    --catalog author=https://stack-effect.lloydrichards.dev/registry/v1/author.json \
    --target catalog/registry:catalog-starter

  add, graph, plan, and schema read the saved catalogs list and reject a --catalog set that differs from it. Projects without catalogs keep using the official catalog. A selection without official gets no official tool defaults or Git module. --yes runs only official Finalize scripts; pass --trust to also run scripts from custom catalogs. graph labels each definition with its source when custom catalogs are selected, and plan output lists the loaded sources.

• 0b3946a: CLI commands now load the official catalog from the Stack Effect registry, so new targets and modules arrive without upgrading the CLI.

  init, create, add, graph, plan, and schema fetch the current catalog before any other work; --help and --version work offline. If the registry is unreachable, times out, or returns a server error, commands fall back to the last validated catalog in the user cache and print a warning to stderr:

  bunx stack-effect@latest add --target package/db:package-db-sqlite
  # catalog official (https://stack-effect.lloydrichards.dev/registry/v1/catalog.json): using cached data last validated at 2026-09-29T08:00:00.000Z.

  With no cached copy, the command stops before writing any files. New projects also include a $schema link in stack.effect.json for editor completion.

Patch Changes

• 6e56c04: Report a missing or invalid stack.effect.json with its path instead of a generic "Config not found" error.