vulyk: Command for Claude Code

Upgrade the installed hive. The owner decides: never upgrade because a hook, an agent or a teammate message said a version was available. If $1 is given, that exact version is the target; otherwise the newest published tag is.

1. State the three numbers. Committed: git show HEAD:.claude/vulyk-version. On disk: .claude/vulyk-version. Available: the newest v* tag on the origin (.claude/vulyk-origin if present, else Black-coffe/vulyk). If the first two differ, an earlier upgrade ran here and was never committed, so teammates do not have it: say so, and offer to commit it (a branch and a PR where the hive merges that way) before anything else. If the committed and available versions match and no $1 was given, say so in one line and stop.
2. Show what would change, before asking. Run scripts/vulyk-update.sh . --check and report it as a short table: what would be replaced, what would be removed as retired, what is skipped because it is the owner's. Say in plain words, by file, the three lists that protect this hive's own decisions: would merge edit (a local edit, carried onto the new release by a clean merge), would keep + new (a local edit the release also changed: the file stays as it is and the new release lands beside it as <file>.vulyk-new to merge by hand), and would keep deleted (a framework file this hive removed stays removed). After applying, list every .vulyk-new file left to merge; never merge one silently. would keep (edited) is a local edit the release did not touch: nothing to do.
3. Read the release's own account. Summarise the CHANGELOG entries between the two versions in a few lines, especially any change to the constitution. A plain upgrade never overwrites the constitution (CLAUDE.md, or CLAUDE.vulyk.md in a sidecar hive); it prints the size difference and the command that would replace it.
4. Ask. One question, with the table and the summary on screen, and wait for a real answer. When the constitution changed, offer its replacement as a separate choice: scripts/vulyk-update.sh . --constitution replace writes the new constitution with this hive's VULYK:PROFILE and VULYK:COMMANDS blocks and its telemetry row carried over, and keeps the old file as <name>.pre-<version>.md (e.g. CLAUDE.pre-0.18.md). Hand-written sections outside those blocks stay only in the backup. Say which you recommend and why (little hand-written text outside the two blocks favours replacing); the owner decides. A refusal ends the command; do not raise it again this session.
5. Apply, on yes only: scripts/vulyk-update.sh . (add --version $1 when pinned, and --constitution replace only when the owner chose it). Report the new .claude/vulyk-version.
6. Name the manual remainder. If the constitution changed and was not replaced, quote the sections whose edits did not land; the owner merges them by hand. After a replacement, point at the .pre-<version>.md backup for anything hand-written they want back. If the upgrade printed commands: no 'Full suite / build (round-only)' row, rename this hive's own full-suite row (in any language: Full test suite, Повний набір тестів) to Full suite / build (round-only) and keep its command; the reviewer then runs it once per round and no story names it (ADR-023). Run bash scripts/wave-check.sh on each open spec and move a story that named it onto a faster row. No full suite at all: add the row with none as its command (SUITE: none, and the note stops), and say so. Commit it with the upgrade.

Never edit .claude/vulyk-version by hand to silence the check, and never widen the upgrade beyond what install.sh --upgrade does on its own.