lcx-contribute-bug-fix

# lcx-contribute-bug-fix Use this skill to debug a concrete LazyCodex or Codex defect, implement the smallest correct fix in a fresh temporary workspace, and deliver it. Work in English, keep the body short, and support every claim with runtime or source evidence. Route ownership the same way as `$lcx-report-bug`, but the deliverable differs by target: - `code-yeongyu/lazycodex` for LazyCodex, lazycodex-ai, omo-codex, bundled skills, hooks, MCP wiring, installer behavior, marketplace sync, docs, or packaging. Deliverable: a verified-fix issue with the patch embedded. NEVER open a PR or push a branch against this repo — its contents are regenerated from the source tree on every release, so PRs there cannot be merged and will be closed. - `openai/codex` for upstream Codex CLI bugs that reproduce without LazyCodex or come from Codex core behavior. Deliverable: a PR from a fork. ## Required Outcome For `openai/codex`, create a fork PR that includes: - a focused branch from a fresh `/tmp` clone/worktree - reproduction logs from before the fix - the smallest implementation that fixes the defect - verification logs from after the fix - apply `lazycodex-generated` when label management is available - the required LazyCodex footer tag `Tag: lazycodex-generated` - cleanup of temporary worktrees and clones For `code-yeongyu/lazycodex`, create an issue (never a PR) that includes: - reproduction logs from before the fix - the root cause with source evidence - the verified patch as...