## What changed
The website currently suggests installing `hapi` directly from npm, which
resolves to the deprecated `hapi@18.1.0` package (with known security issues).
This PR updates the installation command to use the correct CLI package:
`@twsxtd/hapi`.
## Why
Running `npm install -g hapi` triggers a deprecation and security warning:
> This version contains severe security issues and defects and should not be used
This is confusing for users and may lead them to believe HAPI itself is insecure.
## Result
- Users install the correct package
- No npm security warning
- Instructions now match the actual CLI package name
