docs(#108,#109): pin replace-body body rules and quote the import spec example

[bigknoxy]

Problem

Two invocation rules were discoverable only by experiment, and both fail in ways an agent cannot see:

#108 — replace-body owns the braces and the indentation of the body it writes. Passing them back is accepted, and the result still parses:

argument	result
return a * 2;	✅ return a * 2;
{ return a * 2; }	❌ { return a * 2; } — a nested block, the old body gone but replaced by a block
return a * 2;	❌ return a * 2; — double-indented

The quickref described the argument as "New body (or @file)".

#109 — the quickref's add-import example was '{ Foo } from ./bar'. The spec is parsed as source, so the unquoted path is a PARSE_ERROR when copied.

Fix

• --help text for <new-body> / --new-body now says "statements only — no braces, no indentation"; <import-spec> / --import-spec now shows the quoted form. Quickref regenerated.
• Two new gotcha sections in docs/CLI-QUICKREF.md, each with a ✅/❌ pair and the multi-line re-indentation behaviour spelled out.
• README command table rows for both commands.

Verification

• tests/quickref-body-import-contract.test.ts — 8 tests. Four pin the actual replace-body bytes (bare, braced, pre-indented, multi-line), two pin quoted-vs-unquoted add-import (PARSE_ERROR, file untouched), two assert the quickref itself states the rules and that from ./bar appears only on a ❌ line.
• Falsified against main: the two doc-assertion tests fail (the behaviour tests pass, as expected — this is a documentation defect, not a behaviour one).
• Full suite 853 pass / 0 fail. bun run lint:docs clean.

Closes #108
Closes #109

🤖 Generated with Claude Code

[bigknoxy]

🎉 This PR is included in version 4.4.15 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀