fix(codex): qualify lazycodex install commands

[minpeter]

Summary

• replace unsafe unqualified LazyCodex/Codex Light install examples with package-qualified bunx commands
• add docs and CLI-help regression coverage so bunx lazycodex install / unqualified bunx omo install do not reappear in user-facing install guidance
• update Git Bash recovery guidance and Codex Light package/component docs to point at resolvable packages

Why

lazycodex is currently unpublished on npm, while omo resolves to an unrelated package. The canonical install paths should force package resolution through @code-yeongyu/lazycodex or oh-my-openagent.

Verification

• bun test script/lazycodex-install-docs.test.ts src/cli/cli-program.test.ts script/publish-workflow.test.ts bin/oh-my-opencode.test.ts bin/platform.test.ts src/cli/install-platform-resolution.test.ts src/cli/install-codex/lazycodex-routing.test.ts src/cli/install-codex/git-bash.test.ts packages/omo-codex/scripts/install/git-bash.test.mjs packages/omo-codex/scripts/install-local-git-bash-preflight.test.mjs src/cli/install-codex/install-codex-git-bash-preflight.test.ts
• bun run build
• bun dist/cli/index.js install --help
• rg "bunx lazycodex install|bunx omo install|bunx lazycodex|bunx omo" ... now only matches the negative regression assertion

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.