v1.7.1 — correct the restart claim (measurement disproved it)

Corrects a sentence in 1.7.0 that measurement disproved.

What was wrong

1.7.0 said: "a restart is required before the new version actually runs" — and the injected prompt told the model never to claim the new version is active before that restart.

Installing 1.7.0 over 1.6.1 showed both are wrong for this install path. Immediately after install_bundle returned application: applied, with no process restart:

Check	1.6.1	Observed
github_* tools live	8	9 (including github_update, 4 params)
projected Config schema	no updateCheck	has updateCheck / updateRepo / updateChannel / updateCacheDir
prompt section rules	6	7

All three exist only in the new generation, so the plugin manager re-activated the entry and the new code was already serving.

The opposite was also measured earlier in the same environment (installing 0.2.0 did not update the projected Config schema until a restart). Two opposite observations mean the boolean was never a fact — and a confident wrong guess is worse than a question, especially in a prompt that then makes the model deny a version which is already live.

What changed

next.restartRequired: true   →   "unverified"

• stage now says one step remains (install) and asks the caller to verify the running generation with a tool or Config key unique to the new version.
• The installed package.json is called out as not proof: pnpm replaces it before the module is necessarily reloaded, so pluginVersion() can report the new version while the old code runs.
• Prompt rule 7 compressed to stay inside the 2400-character budget; README and CHANGELOG corrected.

New test pins restartRequired === 'unverified' and the verification guidance; the live probe asserts the same.

Verification

158 offline tests · 211/211 parameter coverage · 114/114 guidance · 84/84 argv shapes by real gh · 180 deterministic snapshots · live update probe passing.