[clabonte]

Closes #170.

Two scripts land in scripts/specfuse/ through init and upgrade. Both are generic versions of RestoManager's production scripts.

generate.sh

• Bundles OpenAPI once, and AsyncAPI when asyncSpecifications is set. Then runs specfuse authoring generate generate --progress --group <g> once per group.
• Groups are picked by name (case-insensitive), by --lang (repeatable; aliases cs/dotnet, py, flutter, ts, docs), or with an explicit all. Also supports --list, --dry-run, --skip-validation and --spec-version.
• Safety: lists every group whose destination is in another git repo, with that repo's branch. Refuses to run if that repo has uncommitted changes, unless --allow-dirty is passed.
• Hook: a project-owned scripts/post-generate.sh (outside scripts/specfuse/, so upgrades leave it alone) runs after each group with <group> <language> <destination> <basePackage>. The README has a Dart build_runner example.
• At the end, names the repos that need a regen PR and warns not to commit the regen's stateDir changes.

advance-state.sh

• Wraps the generator's baseline command.
• Keeps a group's new baseline only when its destination repo is clean, on its default branch (origin/HEAD, else main, or --branch) and level with origin. Every other group's state file is restored, including groups that write into the spec repo itself.
• Refuses to start if stateDir has uncommitted changes. Supports --dry-run, --repo and --no-fetch.
• Reads stateDir from the project file.

Differences from RestoManager's scripts

• Reads JSON with python3 instead of jq, so there's no CRLF guard to maintain.
• Doesn't tolerate exit 1 from baseline. It exits 0 on success (checked).
• Restores state files for groups that write into the spec repo itself, which RestoManager's script left modified.
• No built-in Dart or verify-generated step; those go in the hook.

Tested locally with /bin/bash 3.2 on two repos: hello-orders as the spec repo, plus a sibling Backend repo with a bare origin.

• generate.sh: --list; all --dry-run; refusal on a dirty repo; unknown group; a real all run with the hook getting the right arguments.
• advance-state.sh:
  • refuses when stateDir is dirty
  • skips while the regen is uncommitted, and while it's committed but not pushed
  • after the push: --dry-run keeps nothing; the real run keeps only Domain.json and drops the in-repo Local group's file
  • a rerun after committing reports nothing to commit
  • --repo filters correctly
• Shellcheck reports nothing at warning level. The new CI step passes locally against a project scaffolded from this branch.

Notes

• Based on main, not stacked on feat(generator): per-project generator pin with checksum, plus an unpinned local-jar override #175. The scripts go through specfuse authoring generate, so they use a project pin automatically once feat(generator): per-project generator pin with checksum, plus an unpinned local-jar override #175 merges.
• The CI step sits in the middle of ci.yml because feat(generator): per-project generator pin with checksum, plus an unpinned local-jar override #175 also appends one at the end, and two end-of-file additions would conflict.
• Follow-up after docs: component-repo setup guide #173 and fix(generate): pass the generator's own verb; drive groups from the project file #174 merge: point the component-repos guide and the /generate skill at generate.sh. I didn't do that here to avoid conflicts.

🤖 Generated with Claude Code