CLI: Enforce technical requirements during init

[yamcodes]

Follow-up to #913.

The documentation has been restructured to consolidate technical requirements (TypeScript version, module resolution, and runtime compatibility) into the docsite.

This issue tracks adding automated checks to the @arkenv/cli to verify these requirements during arkenv init:

• Verify TypeScript version is >= 5.1
• Verify moduleResolution is set to bundler, node16, or nodenext (or inferred correctly from module)
• Check for strict: true in tsconfig.json

Once implemented, the Compatibility section in the manual installation docs can be further streamlined.

[arkenv-bot]

🤖 Hi @yamcodes, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[arkenv-bot]

🤖 I'm sorry @yamcodes, but I was unable to process your request. Please see the logs for more details.

[yamcodes]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Add environment and dependency checks to the arkenv init process

Current behavior:
arkenv init proceeds even if the user has an incompatible Node.js version or missing peer dependencies, leading to failures later in the setup.

Desired behavior:
The CLI should perform early checks for Node.js version (matching engines in package.json), existence of package.json, and presence of required build tools.

Key interfaces:

• init command handler — logic to inject pre-flight checks.
• Requirement manifests — a central list of versions and tools to check.

Acceptance criteria:

• CLI exits with a clear error if Node.js version is < 18.
• CLI warns if package.json is missing in the target directory.
• Users can bypass checks with a --force flag.

Out of scope:

• Automatically installing Node.js or other system-level tools.