Problem: Some genuinely pure helper functions live at the function level inside otherwise I/O-heavy files — for example, a pure regex-based parser living inside the very large D1-query-heavy repository-access file. A file-list-driven extraction plan misses these entirely.
Area: ORB / gittensory-engine
Proposal: Do a targeted sweep of the largest I/O-bound files (the repository-access layer, the queue processor, the GitHub-command layer) specifically for pure, side-effect-free helper functions that could be extracted independently of their containing file.
Deliverables:
- A list of identified stranded-pure-logic candidates, with at least the most valuable ones actually moved into the engine package as standalone functions.
Acceptance criteria:
Problem: Some genuinely pure helper functions live at the function level inside otherwise I/O-heavy files — for example, a pure regex-based parser living inside the very large D1-query-heavy repository-access file. A file-list-driven extraction plan misses these entirely.
Area: ORB / gittensory-engine
Proposal: Do a targeted sweep of the largest I/O-bound files (the repository-access layer, the queue processor, the GitHub-command layer) specifically for pure, side-effect-free helper functions that could be extracted independently of their containing file.
Deliverables:
Acceptance criteria: