Skip to content

Nuclear review 2026-07-09: tracking issue #104

Description

@arzafran

Umbrella for the 2026-07-09 nuclear review (whole-codebase maintainability audit: 10 module reviewers + Codex cross-model pass + dependency audit). Verdict: NEEDS RESTRUCTURING — behavior and dependencies are healthy, but 17 files sit over 1,000 lines (five god-objects) and the dominant systemic defect is copy-paste duplication that has already drifted into real bugs.

Recommended attack order:

1. Correctness first (small, ship independently)

2. Pure deletions (same spirit as PR #81)

3. Biggest lines-moved-per-risk

4. Highest long-term leverage

5. Dedups

6. Mechanical file splits (any order, independent)

Ground rules carried from the review: typing-latency paths (TabItemView shape, hitTest gating, forceRefresh, keyDown) are file-move-only, never reshape; socket commands with no in-app callers are live (CLI/daemon); whoever lands fixes owes CHANGELOG entries per nuclear-review Phase 4. Full evidence with line ranges lives in the review workflow output; each issue is self-contained enough to hand to an agent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    nuclear-reviewFrom the 2026-07-09 whole-codebase nuclear reviewtech-debtKnown latent issue / maintenance debt

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions