fix: prevent local packages from shadowing hooks

[pDJJq]

Summary

• run lifecycle hooks through a distinct scoped npm alias so a consumer repository local @tokenroll/llmdoc dependency cannot shadow the published CLI
• validate the exact commands declared in hooks/hooks.json, including SessionStart, Stop, and PreCompact execution
• document the launcher boundary and release invariant, and bump all package/plugin surfaces to 3.5.3

Root cause

In repositories that depend on @tokenroll/llmdoc via file:cli, npx resolves that same-name local package first. A fresh npm ci does not expose node_modules/.bin/llmdoc for it, so the hook process exits 127 before the CLI fail-open logic can run.

Validation

• npm run lint
• npm run typecheck
• npm test (55/55)
• node scripts/check-codex-surface.mjs
• npm run check:prompts, including all three exact configured hook launchers
• npm run validate:dogfood
• launcher smoke tests with npm 8, 9, and 11
• llmdoc validate; final status: 0 impacted, 0 needs-review, 0 dirty