Skip to content

Audit and remove obsolete legacy release/distribution surface #129

@cbusillo

Description

@cbusillo

Objective

Reduce the repo surface area we have to own by auditing and removing obsolete release/distribution code, workflows, scripts, docs, and metadata that only support legacy overlay or public-package publishing paths we no longer intend to use.

Current Status

State: Waiting
Next action: Complete the release model decision in #126, then audit stale release/distribution references and remove or quarantine obsolete pieces in focused PRs.
Blocked by: #126 release workflow decision.
Last verified: 2026-05-24 after deciding npm/Homebrew are not required for auto updates and GitHub Releases should be the update source.

Scope

  • In: Legacy Binary Release workflow remnants, overlay release-note scripts, obsolete tag-prefix handling, stale docs, unused npm/Homebrew release scripts, stale metadata in .github/github.json, and references that imply public distribution is required for internal updates.
  • Out: Removing active upstream attribution, deleting import/sync mechanisms needed for Check upstream changes from just-every/code and openai/codex #124, broad source-tree rewrites, or changing runtime behavior without a specific follow-up issue.

Acceptance Criteria

  • Search repo for stale release/distribution terms such as Binary Release, overlay-v, every-code-v, npm publish, Homebrew publish, and local overlay release notes.
  • Classify each finding as active, update, remove, or leave with rationale.
  • Remove obsolete files/steps rather than carrying dead code where safe.
  • Update .github/github.json so workflow and docs metadata match the actual release model.
  • Update docs to describe GitHub Releases as the internal update source.
  • Preserve clear attribution to Every Code and OpenAI Codex CLI.
  • ./build-fast.sh passes for any code/workflow-impacting cleanup.

Relationships

Depends on #126.
Related to #121 and #122, which should remain deferred unless package-manager distribution becomes intentional again.
Related to #124, because upstream import/sync mechanisms must be preserved.
Related to #85, because reducing legacy surface is part of making the fork maintainable as our own internal tool.

Notes

The intent is not a deletion spree. The goal is to remove dead or misleading surfaces so future release/update work has fewer traps and less ambiguous ownership.

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issue

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions