Fix Prose CLI Codex runtime startup

[irl-dan]

Summary

• Prevent Codex/Claude harness prompts from recursively invoking the prose CLI wrapper.
• Resolve local file targets to their nearest project root before starting harnesses, so absolute paths work from non-repo directories.
• Give Codex harnesses practical runtime defaults: skip git repo checks, use workspace-write, add Codex home as writable, enable network for that sandbox, and inherit PATH.
• Prepare the patch release as @openprose/prose-cli@0.1.2 and update the install script default.

Why

A first real local run of prose run /absolute/path/to/responsibility.md exposed startup failures from recursive prose run execution inside Codex and sandboxed access to ~/.codex/sessions. It also surfaced PATH differences when Codex shells did not inherit the user's normal environment.

Empirical check

A bounded real-harness smoke using the built CLI from /Users/sl/code/openprose against the stargazer responsibility no longer reproduced:

• Codex cannot access session files at /Users/sl/.codex/sessions
• recursive prose run startup
• zsh: command not found: rg

The smoke reached responsibility execution and was intentionally capped before a full customer workflow run.

Verification

• npm run typecheck
• npm test
• npm run build
• go run github.com/rhysd/actionlint/cmd/actionlint@latest .github/workflows/cli-*.yml
• git diff --check