fix(ci): recover lazycodex npm checks

[code-yeongyu]

Summary

• Reverts the standalone lazycodex-ai wrapper change from fix(bin): distinguish ENOENT from other spawn failures #23, since this repository is not the source of truth for the real OMO Codex installer path.
• Narrows the no-Hangul public-surface check so generated plugins/omo/ internals are ignored.

Root Cause

The failed main run was NPM CI on merge commit 584bf29. The actual failing assertion was test/no-korean-text.test.mjs, which scanned generated OMO plugin test fixtures under plugins/omo/skills/visual-qa/scripts/*.ts. Those files intentionally contain Hangul to test East Asian width handling and are not public LazyCodex copy.

Validation

• npm test
• npm pack --dry-run --json

---

Summary by cubic

Fixes failing CI by narrowing the no-Hangul check and simplifying lazycodex-ai error handling. Generated OMO plugin fixtures are now ignored so tests pass on main.

• Bug Fixes
  • Ignore plugins/omo/ in test/no-korean-text.test.mjs (generated fixtures with Hangul).
  • Simplify spawn error handling in bin/lazycodex-ai.js by removing ENOENT-specific messaging.
  • Remove related test test/bin-spawn-error.test.mjs.

^{Written for commit 789f4d7. Summary will update on new commits.}

[code-yeongyu]

Thanks for opening this PR. The canonical LazyCodex source lives in oh-my-openagent, and the Codex Light implementation is under packages/omo-codex.

This PR is limited to recovering the LazyCodex repository CI after the accidental direct wrapper merge and to keeping generated marketplace internals out of the public-copy text check.

[cubic-dev-ai]

No issues found across 3 files

_{Re-trigger cubic}