Local sync

Use local sync only when the user explicitly asks to refresh the local STIG development workspace and the installed stig plugin and its skills. It is not a sixth submit path: do not create commits, push, update a PhASAR pin, select a release marker, or run submit-path verification gates.

Run steps 1–4 from the stig-project root. Run the installation in step 5 from the sibling stig/ source root.

1. Before changing anything, confirm that ../stig and ../stig-project-real-oss-template exist and have clean working trees. Confirm that this consumer's tracked gradle.properties has no user changes. Stop and report any failed preflight; never stash, reset, or merge to make the sync proceed.

2. Fetch STIG's tags, including tags created by a GitLab pipeline, and fast-forward its current branch:

   git -C ../stig fetch --tags origin git -C ../stig pull --ff-only git -C ../stig tag --points-at HEAD git -C ../stig describe --tags --always --long

   Report the resulting commit and tag information, but do not infer the STIG version from a tag name.

3. Fast-forward the real OSS template's current branch:

   git -C ../stig-project-real-oss-template pull --ff-only

   Do not independently rewrite the template's stigVersion; its release pipeline owns that fallback pin, and the pull obtains any published update.

4. Resolve the consumer's actual STIG version after the pulls:

   ./gradlew stigPrintVersion --console=plain

   Set this repository's existing gradle.properties stigVersion to the exact stigVersion reported by that task, for example 2.1.2-SNAPSHOT. The property is the published-plugin fallback when no sibling ../stig checkout is present. A sibling composite build overrides it, so the task output, rather than the nearest Git tag or the old pin, is authoritative.

5. Install the refreshed plugin and all three skills from the STIG source root:

   # Working directory: stig/ ./gradlew installSkill --console=plain --info

   The source-root installer packages this checkout directly; it does not need an installation command in stig-project. The local sibling override makes this the STIG build used by the consumer version check above. An explicit local sync request authorizes this user-scoped plugin installation. Consumers without a STIG source checkout can separately use their stigInstallSkill task.

6. Report the resolved version, the stigVersion update, the installer result, installed directory, and content SHA-256. The skills can be used immediately in the current conversation; an IDEA restart or a new thread is not normally required. Offer the installer's verification prompt when the user wants to check a repeated SNAPSHOT update. See installation and update verification for the content check and troubleshooting when an update does not appear.

Stop after any failed fetch, pull, version check, property update, or install, and report the completed and pending steps. Do not use an unpinned fallback or bypass a failed command.