fix: resolve bundled text assets relative to the require module

[cracer4869]

Starting @cometix/claude-code@2.1.261 from a project directory fails with ENOENT for loopAutonomousPreamble-5hfhrxrk.md, even though the file exists in the installed package. The runtime-path rewrite now emits relative paths, but the .md/.txt branch passes them directly to readFileSync, which resolves against process.cwd().

Resolve text paths through the module-scoped require.resolve() before reading them, matching the resolver used for other require targets.

• Add regression fixtures for both BunFS path forms, flat and nested module layouts, and paths containing spaces, #, and Unicode. Check execution from inside and outside the package, same-named files in the working directory, absolute text paths, and ordinary JSON loading.
• Run the tests on Node 24 on Windows and Ubuntu.
• Run release smoke checks outside the package directory so the original cwd-dependent behavior cannot pass unnoticed. Capture help output before printing its first lines.

Validation:

• GitHub Actions: Node 24 regression tests pass on both Windows and Ubuntu.

• All four regression tests fail with ENOENT before the fix and pass afterward on Windows / Node 24.18.0.

• An isolated copy of the installed 2.1.261 package reproduces the error with node <package>/cli.js --help from an external directory. Replacing only its generated require shim makes the same command exit 0. The global installation was left unchanged.

• node --check scripts/esm-chunk-patch.mjs, node --check test/esm-text-assets.test.mjs, workflow YAML parsing, release verification shell syntax, and git diff --check pass.

The full cross-platform release build was not run locally.

[cracer4869]

我又来啦！！！彗星佬