Skip to content

audit: replay (644 LOC) + operator (447 LOC) + multirepo (~380 LOC) — keep, remove, or freeze? #52

@hadamrd

Description

@hadamrd

Three modules totalling ~1,500 LOC with no observable consumer in actual loop runs. Per the no-scaffold-theatre rule from #42:

  • replay.py: time-travel for past ticks. Never invoked.
  • operator.py: ask_operator MCP tool. No worker brief calls it.
  • multirepo: forge-loop repos list/disable/enable exist but no repos run; the run path can't actually serve N repos.

Decisions to make per module:
A) Remove (drop the code, free the maintenance budget).
B) Wire (add a real consumer; e.g. a brief that calls ask_operator).
C) Freeze (move under src/forge_loop/_experimental/ with a clear 'do not use' note + tests stop running).

Each module = one decision. File 3 sub-issues once decided.

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicMulti-PR umbrella tracking a major themeloop:blockedParked for human attentionpriority:p2Nice to have, opportunistictype:refactorCode reorg, no behaviour change

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions