Audit and retire obsolete legacy code paths

[cbusillo]

Objective

Reduce the code surface we have to understand, test, and own by auditing legacy runtime/source paths and removing pieces that no longer serve the internal fork direction.

Current Status

State: Waiting
Next action: Build an inventory of legacy code paths after the release/distribution cleanup direction in #126 and #129 is settled.
Blocked by: #126 release model decision and enough upstream-intake context from #124 to avoid deleting code we still need for imports/compatibility.
Last verified: 2026-05-24 after deciding this repo should remain an internal fork/dogfood tool rather than a public takeover/rebrand.

Scope

• In: Obsolete compatibility shims, unused CLI aliases/install paths, stale package-manager code, dead release/runtime helpers, old overlay-specific behavior, abandoned provider/model routing branches, docs-promoted features that no longer exist, and code paths kept only because of historical upstream layout.
• Out: Removing active upstream attribution, deleting codex-rs mirror/import mechanisms without a replacement, broad renames without tests, or removing behavior still needed for current dogfooding workflows.

Acceptance Criteria

• Inventory suspected legacy code paths with file references and current usage evidence.
• Classify each item as active, remove now, deprecate first, keep for upstream sync, or needs owner decision.
• Prefer deleting dead code over preserving unsupported feature flags or compatibility branches.
• Split removals into focused PRs with tests or targeted reproductions where behavior risk exists.
• Preserve Discord, Launchplane/LaunchDarkly, agent, Code Bridge, and current dogfood workflows unless a separate decision says otherwise.
• Keep codex-rs read-only mirror/import purpose intact until Reduce codex-rs/code-rs search and layout confusion #88 or a follow-up layout plan replaces it safely.
• Run ./build-fast.sh for implementation PRs.

Suggested First Audit Areas

• Release/distribution leftovers tracked in Audit and remove obsolete legacy release/distribution surface #129.
• npm/Homebrew/package-manager install paths if Configure npm publishing token for Release workflow #121/Fix Homebrew tap publish credential for Release workflow #122 stay deferred or are superseded.
• Binary/package aliases that imply public distribution rather than internal dogfooding.
• Old overlay naming/tag-prefix helpers after Reconcile legacy Binary Release workflow with main Release path #126.
• Prompt/system instruction files that still describe upstream product identity instead of current internal fork reality.
• Duplicate or stale paths caused by the codex-rs mirror plus code-rs product source layout.

Relationships

Related to #85 for internal fork/product direction.
Related to #88 for codex-rs/code-rs layout confusion.
Related to #124 for upstream intake; do not delete import-critical surfaces blindly.
Related to #129 for the release/distribution subset of this cleanup.

Notes

The goal is less owned surface area, not churn. Each deletion should have evidence that the path is dead, misleading, or outside the current internal dogfood model.

[cbusillo]

Unblocked enough to start now that #129 is closed.

Updated working state:

• State: Active
• Next action: inventory suspected legacy runtime/source paths, classify each with usage evidence, and split only proven-safe removals into focused PRs.
• Guardrails: preserve codex-rs import/mirror purpose, upstream attribution, Launchplane/Code Bridge/current dogfood workflows, and active tooling pins unless separate evidence shows they are dead.

I am starting with a read-only repo inventory pass before deleting anything else.

[cbusillo]

Progress update after the first cleanup wave:

Completed focused removals:

• Remove legacy GitHub release helpers #147 removed obsolete code-rs/scripts/create_github_release* helpers and updated the TUI release rehearsal sample to the current protected Release workflow.
• Remove code-rs migration scaffold docs #148 removed migration-era code-rs crate-copy scaffold docs/helpers: MIGRATION_GUIDE.md, MIGRATION_QUICK_REFERENCE.md, migrate-crate.sh, and the nested code-rs/justfile.

Validation:

• Remove legacy GitHub release helpers #147: local ./build-fast.sh, Blob size policy passed, post-merge Release run 26426383268 passed 8/8.
• Remove code-rs migration scaffold docs #148: local ./build-fast.sh, Blob size policy passed, post-merge Release run 26427317297 passed 8/8.
• Current repo state: clean main; no open PRs; latest release remains v0.6.105; code update-check reports local 0.6.105 up to date.

Inventory notes:

• Keep active upstream/tooling surfaces: codex-rs mirror/import scripts, rusty-v8 release pins, argument-comment-lint DotSlash assets, Python SDK rust-v compatibility, Code Bridge, Launchplane worker, and current agent workflows.
• Remaining high-value audit area: npm/package wrapper surface under codex-cli (package.json, postinstall.js, optional platform dependencies, npm-managed env hints). This is not safe to delete blindly because codex-cli/package.json still drives Release version metadata.

Next action: decide whether to keep codex-cli as version/package compatibility metadata, or replace Release version sourcing first and then retire the npm wrapper surface in smaller PRs.