eforge-stack

# /eforge:stack:sync Manually synchronize the git-spice stack for this project. Use `--dry-run` to preview what commands would run without executing them. Stack sync is a daemon-owned operation that runs from the project root. The daemon calls `git-spice repo sync` followed by `git-spice stack restack`. Triggers include: this command (`/eforge:stack:sync`), the CLI (`eforge stack sync`), the `eforge_stack_sync` tool, and — when `stacking.sync.afterBuild: true` is configured — automatically after each build completes. ## Requirements Stack sync requires `stacking.enabled: true` in `eforge/config.yaml` and git-spice initialized in the repository (`git-spice repo init`). If stacking is not enabled the daemon returns `outcome: "skipped"` with a reason. ## Step 1: Detect dry-run flag Check `$ARGUMENTS` for `--dry-run`. If present, set `dryRun: true` in the tool call. ## Step 2: Run the sync Call the `eforge_stack_sync` tool with `{ dryRun: <true|false> }`. ## Step 3: Interpret the response The tool returns a structured sync report. Interpret each field: | Field | Meaning | |-------|---------| | `outcome` | One of `"skipped"`, `"complete"`, `"deferred"`, `"failed"`, `"conflict"` | | `reason` | Human-readable reason (always present for skipped/deferred/failed/conflict) | | `stackingActive` | Whether stacking is enabled and active for this project | | `dryRun` | Whether this was a preview-only run | | `localTrunkSha` | SHA of the local trunk branch | | `originTrunkSha` | S...