Summary

• skip materializing bundled agent TOMLs when Orca already registers the role from a foreign runtime path
• remove only previously LazyCodex-managed local copies whose contents still match the previous staged TOML
• preserve user-owned or user-modified same-name agent files
• keep the shipped dist/cli.js behavior in sync with the TypeScript source

Root cause

Orca mirrors [agents.<name>] entries into its runtime CODEX_HOME/config.toml, pointing at another runtime's agent file. LazyCodex's bootstrap filtered the config update but still copied the same bundled TOML into the active CODEX_HOME/agents/ directory. Codex then auto-discovered both paths and reported duplicate agent roles.

Validation

• node --test plugins/omo/test/bootstrap-*.test.mjs: 51 passed
• node --check plugins/omo/components/bootstrap/dist/cli.js: passed
• shipped CLI QA: managed copy removed; replaced user file preserved; unmanaged user file preserved
• node components/bootstrap/scripts/build.mjs: exit 0; this sparse checkout emits pre-existing unresolved sibling-import warnings and retains the existing bundled dist

Fixes #150
Related: #149

Summary by cubic

Prevents duplicate agent roles when Orca mirrors agents into config.toml. We now skip staging mirrored roles, remove only previously managed copies, and preserve user files.

• Bug Fixes
  • Skip staging bundled *.toml when config.toml already points to a foreign runtime path.
  • Remove only LazyCodex-managed copies that still match previously staged content; leave user-owned or modified files.
  • Track installed agents via .installed-agents.json to safely prune only managed duplicates.
  • Keep plugins/omo/components/bootstrap/dist/cli.js in sync with the TypeScript source and add tests for idempotent runs and user-file preservation.

Written for commit 5651d0e. Summary will update on new commits.