fix(release): keep CLI and package versions aligned

[egagofur]

What changed

• The CLI now reads its version directly from package.json, removing the duplicate version that caused the v1.8.0 release check to fail.
• Release verification now checks the real public CLI output.
• A regression test prevents package and CLI versions from drifting again.
• The package is prepared as v1.8.1.
• npm publishing is now started manually instead of running automatically whenever a GitHub Release is published.

Steps to Reproduce & Testing (QA)

Steps to Reproduce

1. Set the package version while the old CLI version constant remains unchanged.
2. Run the v1.8.0 release check.
3. Observe the package/CLI mismatch.

How to Test

node scripts/verify-release.js v1.8.1
node bin/ai-engineering-loop.js --version
npm test
npm run doctor
npm run eval
npm run audit:package
npm pack --dry-run

Actual Result before the fix

The release workflow stopped because the CLI reported 1.7.0 while the package reported 1.8.0.

Expected Result after the fix

Both versions come from one source, the release identity check passes, and publishing a GitHub Release does not automatically publish npm.

Verification

• Release identity: passed for v1.8.1
• 207 tests passed
• Doctor READY
• Package privacy audit passed
• Package dry-run passed for 1.8.1