sync-from-core

sync-from-core

When to use

Manually, after check-for-updates reports a new version is available. Or unconditionally to pull the latest upstream changes.

Inputs

• target_version (optional; default: latest non-prerelease release tag from upstream).
• branch (optional; default: opos-update-<tag>).
• check_only (optional bool; default false): if true, runs copier update --dry-run and prints the diff without creating a branch or modifying files. Useful for previewing changes.

Steps

1. Resolve repo root via git rev-parse --show-toplevel. Ensure the working tree is clean (git status --porcelain returns empty). If not: ABORT with instruction to commit or stash first. Do NOT proceed with a dirty tree — copier update would mix consumer's in-progress edits with upstream changes.
2. Read <repo-root>/.copier-answers.yml. Extract _src_path. Classify it with the same four-shape logic as check-for-updates step 4 (remote GitHub → <owner>/<repo>; existing local clone → warn "local path, non-portable" and resolve tags via git -C <path> tag; missing local path or unparseable → ABORT with: _src_path '<value>' cannot be used for updates on this machine. Edit .copier-answers.yml and set _src_path to gh:<owner>/<repo> (leave _commit untouched), commit, and re-run.). If .copier-answers.yml is missing: ABORT with instruction to scaffold via copier copy first (this skill cannot bootstrap a repo).
3. Resolve target_version:
   • If --target_version passed: use it.
   • Else (remote shape): gh api repos/<owner>/<repo>/releases --jq '[.[] | select(.prerelease == false)] | first | .tag_name' (no leading slash — MSYS/Git-Bash path-mangling on Windows). Local-clone shape: git -C <path> tag --sort=-v:refname | grep -v -- '-' | head -1.
4. If --check_only is true (v0.8.1 rewrite — Copier has no --dry-run, and --pretend is ignored by copier update's patch-apply step, so a real preview needs a throw-away branch): git checkout -b opos-preview-<tag> → copier update --vcs-ref <tag> --defaults --conflict rej → print git status --porcelain (flag .rej files) and git diff --stat → git reset --hard && git clean -fd → git checkout - → git branch -D opos-preview-<tag>. Nothing is committed and the tree is left exactly as found. Skip steps 5–9.
5. Create the update branch: git checkout -b <branch> (default opos-update-<tag>).
6. Run copier update --vcs-ref <tag> --conflict rej --defaults. The --defaults flag is safe because copier.yml's only question (COMPANY_NAME) was answered at initial scaffold and persists in .copier-answers.yml; updates reuse the stored answer without re-prompting. --trust is NOT used today because copier.yml has no _tasks or _migrations. If future versions add tasks, add --trust in all THREE sync drivers: here, the auto-sync skill, and the Actions workflow (.github/workflows/sync-opos.yml). 6b. Reconcile consumer-owned settings (the _skip_if_exists delivery hole). copier update cannot touch .claude/settings.json — it is _skip_if_exists, so every framework settings change is otherwise undeliverable to an existing consumer, permanently. Run python3 shared/scripts/reconcile-settings.py --apply from the repo root. It applies only what shared/templates/required-settings.json (CORE, and therefore freshly updated by step 6) declares: managed keys are set to the framework value, additive keys are added only when absent so a consumer's own value always wins. Anything under permissions is never written — never-automate invariant 1 — the script reports such gaps instead, and they are applied only on a Confirm-tier approval from the user. Include the script's change lines verbatim in the step-8 summary so the user reviews them alongside the file diff. A non-zero exit other than 2 (unparseable settings.json) is surfaced, not swallowed: the script refuses to rewrite a file it cannot parse.