/wong-sync

Get the latest WongStack source, run its payload preflight, and invoke /plan only for an update.

Read .claude/.wong-stack.json for the installed version, upstream, and local choices. No record, or a seed with null version and commit, means setup is incomplete: invoke wong-setup from the source checkout. Never sync the source repo with itself.

Follow latest source, read the payload inventory, and run the helper once from the source, not the install, so an old install gets the current classifier:

node "<source path>/.claude/skills/wong-sync/scripts/preflight.mjs" \
  --target "<target root>" \
  --source "<source path>" \
  --record "<record path relative to target>"

It fetches and writes nothing. Follow exactly one route, by the status in its versioned JSON:

• current — report the source version and commit, selected-unit count, and preflight time; stop. No /plan or /explore, no change, no record edit.
• update — keep the whole report in context and invoke /plan, never stopping at Plan it?. Start from changes; expand only for a named dependency or impact, never re-compare the full payload.
• error — report every diagnostic and stop: no partial "current", no broad AI scan, no /plan.

An unknown schema version or status, truncated output, failed command, or invalid JSON is an error; never infer missing fields.

Invoke /plan with this description, filled in, plus any user instructions:

Update this repo to WongStack <version> at <source path>, commit <commit>; it now runs <installed version, or unknown>. The preflight found this complete set of changed payload units: <preflight report>. Start there and expand only for a named dependency or target impact. Keep local adaptations and renamed skills. If CLAUDE.md is a real file, not a link to AGENTS.md, plan its move per <source path>/.claude/skills/wong-sync/references/payload-manifest.md#the-agent-folder. Follow <source path>/.claude/skills/wong-sync/references/payload-manifest.md#planning-an-update for catch-up moves, skipped releases' hand steps, the merge check, and plain wording. Plan the useful updates through the normal workflow. As the last task, after implementation, record the source version in the install record.

Pass prior user decisions as context, an old verdict record's too. Use installed skills by their recorded names, else the source's; resolve source resources in the source checkout while working in the target. Provision a missing part by setup's provisioning runbook from the source checkout.

/plan owns the artifacts and review; its bounded /explore owns investigation and questions. Ask in the ask format. A bare sync stops at the plan's review.html with the next step; a request to implement or ship continues through that verb (just ask). Write no verdict file; prescribe no proposal format.