Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Split `forgelm/cli/_pipeline.py` into a sub-package (`_state`, `_events`, `_verify`)

Open
  • Is something wrong?
#909 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
cli, tooling

Research direction

Start with forgelm/cli/_pipeline.py and the _DEFERRED_SPLITS entry in tools/check_module_size.py, then the deferral row near line 261 of docs/roadmap/risks-and-decisions.md. The split seams are recorded only in that doc, so read them before moving code. Done means a behaviour-neutral sub-package where every public name still imports from the old path, test patch targets retargeted, and the module-size check passing. Coordinate with #714 and #667/#668 first.

Written by the indexing model from the issue text.

Description

area: pipeline severity: low source: roadmap wave: 4

Deferred work · F-W20260729-OPS-10-budgets: _pipeline.py · severity Low · cost ~4-8 h · recorded in docs/roadmap/risks-and-decisions.md:261

Summary

forgelm/cli/_pipeline.py is a deferred module split: the multi-stage pipeline orchestrator's state, event emission and verification live in one CLI-side file. The module-size guard holds it to a fatal no-growth budget, but nothing pays the debt down until someone takes the split. #714 (CR-A04-086) separately asks for the orchestrator's business logic to move out of cli/; decide the two together.

Condition or budget

The Phase 14.5 manifest-verification rewrite has landed (it shipped in v0.10.0) — already met, so this split can be taken now.

State today (re-checked 2026-10-09)

1332 code lines against a budget of 1332; the split was blocked only by the Phase 14.5 rewrite, which shipped in v0.10.0.

Related

#667 and #668 track how the module-size guard counts lines and accepts budget raises; decide them before relying on a module's budget.

Acceptance criteria

  • The module becomes a sub-package along the recorded seams, behaviour-neutral, with every public name still importable from its current path.
  • Its _DEFERRED_SPLITS entry is removed from tools/check_module_size.py and every resulting module is under the normal ceiling.
  • Test patch targets that named the old module are retargeted to the module that resolves the name at call time (the forgelm/verify.py split found five that silently moved).
  • The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).

Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.

Dominant language
Python
Stars
9
Forks
1
Avg merge
8h 10m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HodeTech/ForgeLM

All issues in HodeTech/ForgeLM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.