cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

Epic: Stub Package Cleanup — Remove Ghost Packages and Empty Stub Modules #946

New Issue
Open
opened 2026-03-14 03:15:38 +00:00 by freemo · 0 comments
freemo commented 2026-03-14 03:15:38 +00:00
Owner
Copy Link
Copy Source

Background and Context

A codebase audit revealed several packages that exist only as empty stubs or ghost artifacts with no functional code. These packages occupy namespace, confuse IDE tooling, and misrepresent the implementation status of the system.

Specifically:

  • src/cleveragents/acp/ — Ghost package containing only __pycache__/ with 9 orphaned .pyc files and no .py source files. The ACP (Agent Communication Protocol) module was superseded by the A2A protocol (ADR-047) but was never properly removed.
  • src/cleveragents/runtime/ — Empty stub package with only __init__.py containing __all__ = [].
  • src/cleveragents/domain/repositories/ — Empty stub package with only __init__.py containing __all__ = [].
  • src/cleveragents/domain/plans/ — Empty stub package with only __init__.py containing __all__ = [].
  • src/cleveragents/application/workflows/ — Empty stub package with only __init__.py containing __all__ = [].

Per the specification and CONTRIBUTING.md, no half-done or placeholder implementations should exist in the source tree. Each of these must be either properly implemented (if the spec requires them) or cleanly removed (if they are dead code).

Expected Behavior

The source tree contains no ghost packages, no orphaned .pyc files without corresponding .py sources, and no empty stub packages that serve no architectural purpose. Every package in the source tree either contains functional code or is removed.

Acceptance Criteria

  • acp/ directory is fully removed including all __pycache__/ contents
  • runtime/ is either implemented per spec or removed with imports updated
  • domain/repositories/ is either implemented per spec or removed with imports updated
  • domain/plans/ is either implemented per spec or removed with imports updated
  • application/workflows/ is either implemented per spec or removed with imports updated
  • No orphaned .pyc files remain anywhere in the source tree without corresponding .py files
  • All import references to removed packages are updated or removed
  • nox passes (all default sessions) after cleanup

Definition of Done

This Epic is complete when all child issues are closed and merged. No ghost packages or empty stub packages remain in the source tree, and all tests pass.

## Background and Context A codebase audit revealed several packages that exist only as empty stubs or ghost artifacts with no functional code. These packages occupy namespace, confuse IDE tooling, and misrepresent the implementation status of the system. Specifically: - **`src/cleveragents/acp/`** — Ghost package containing only `__pycache__/` with 9 orphaned `.pyc` files and no `.py` source files. The ACP (Agent Communication Protocol) module was superseded by the A2A protocol (ADR-047) but was never properly removed. - **`src/cleveragents/runtime/`** — Empty stub package with only `__init__.py` containing `__all__ = []`. - **`src/cleveragents/domain/repositories/`** — Empty stub package with only `__init__.py` containing `__all__ = []`. - **`src/cleveragents/domain/plans/`** — Empty stub package with only `__init__.py` containing `__all__ = []`. - **`src/cleveragents/application/workflows/`** — Empty stub package with only `__init__.py` containing `__all__ = []`. Per the specification and CONTRIBUTING.md, no half-done or placeholder implementations should exist in the source tree. Each of these must be either properly implemented (if the spec requires them) or cleanly removed (if they are dead code). ## Expected Behavior The source tree contains no ghost packages, no orphaned `.pyc` files without corresponding `.py` sources, and no empty stub packages that serve no architectural purpose. Every package in the source tree either contains functional code or is removed. ## Acceptance Criteria - [ ] `acp/` directory is fully removed including all `__pycache__/` contents - [ ] `runtime/` is either implemented per spec or removed with imports updated - [ ] `domain/repositories/` is either implemented per spec or removed with imports updated - [ ] `domain/plans/` is either implemented per spec or removed with imports updated - [ ] `application/workflows/` is either implemented per spec or removed with imports updated - [ ] No orphaned `.pyc` files remain anywhere in the source tree without corresponding `.py` files - [ ] All import references to removed packages are updated or removed - [ ] `nox` passes (all default sessions) after cleanup ## Definition of Done This Epic is complete when all child issues are closed and merged. No ghost packages or empty stub packages remain in the source tree, and all tests pass.
freemo added the
MoSCoW
Could have
Points
8
Priority
Medium
State
Verified
Type
Epic
 labels 2026-03-14 03:15:44 +00:00
freemo added a new dependency 2026-03-14 03:19:38 +00:00
#947 fix(cleanup): remove ghost acp/ package and orphaned .pyc files
hurui200320 was assigned by freemo 2026-03-14 04:27:40 +00:00
freemo added this to the v3.2.0 milestone 2026-03-16 16:09:19 +00:00
hurui200320 was unassigned by freemo 2026-04-02 06:13:49 +00:00
freemo self-assigned this 2026-04-02 06:13:49 +00:00
freemo removed the
Priority
Medium
State
Verified
Type
Epic
 labels 2026-04-03 00:30:20 +00:00
freemo added a new dependency 2026-04-03 12:14:38 +00:00
#2262 chore(deps): update ruff dependency from 0.15.1 to 0.15.9
freemo added a new dependency 2026-04-05 06:19:01 +00:00
#3092 Refactor large files to adhere to the 500-line limit
HAL9000 added the
Priority
Medium
State
Unverified
Type
Epic
 labels 2026-04-13 01:53:51 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
 controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
 overdue
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
MoSCoW
Could have
Points
8
Priority
Medium
State
Unverified
Type
Epic
Milestone
No items
No Milestone v3.2.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees freemo
1 Participants
Notifications
Due Date
No due date set.
Blocks
#945 Legendary: Specification Alignment — Close All Gaps Between Implementation and Specification
cleveragents/cleveragents-core
Depends on
#947 fix(cleanup): remove ghost acp/ package and orphaned .pyc files
cleveragents/cleveragents-core
#948 refactor(cleanup): remove or implement empty stub packages (runtime, repositories, plans, workflows)
cleveragents/cleveragents-core
#2262 chore(deps): update ruff dependency from 0.15.1 to 0.15.9
cleveragents/cleveragents-core
#3092 Refactor large files to adhere to the 500-line limit
cleveragents/cleveragents-core
#3102 chore(deps): update behave dependency pin to allow future patch/minor upgrades
cleveragents/cleveragents-core
#3417 UAT: domain/models/__init__.py exports only legacy models — spec-required domain entities missing from public API
cleveragents/cleveragents-core
#3451 fix(plan_generation): remove dead code — unused `_extract_path_from_prompt` and `_find_matching_context` methods
cleveragents/cleveragents-core
#3680 UAT: Pervasive `# type: ignore` suppression in repositories.py violates no-type-suppression rule
cleveragents/cleveragents-core
#3809 UAT: infrastructure/database/repositories.py is 6035 lines — violates 500-line file size limit from CONTRIBUTING.md
cleveragents/cleveragents-core
#3816 UAT: DefaultValidationRunner in validation_apply.py is a stub/placeholder that does not invoke actual validation tools
cleveragents/cleveragents-core
#3852 UAT: Production code in `application/container.py` imports from `mocks/` test directory
cleveragents/cleveragents-core
#3955 UAT: `new_repositories.ResourceRepository` uses wrong field names — will raise `AttributeError` at runtime when creating or querying resources
cleveragents/cleveragents-core
#4011 UAT: `shared/__init__.py` docstring advertises "Logging utilities", "Metrics collection", "Validation helpers", "Date/time utilities" but none of these are implemented
cleveragents/cleveragents-core
#4114 UAT: infrastructure/database/repositories.py exceeds 500-line limit at 6,035 lines — must be split into focused modules
cleveragents/cleveragents-core
#4125 UAT: application/services/plan_apply_service.py violates clean architecture — imports from cli (presentation) layer at line 344
cleveragents/cleveragents-core
#4138 UAT: runtime/ module directory is empty (no __init__.py) — ghost package pollutes module namespace
cleveragents/cleveragents-core
#8932 chore(cleanup): remove acp/ ghost package and all orphaned .pyc files from source tree
cleveragents/cleveragents-core
#8935 chore(cleanup): remove or implement empty stub packages (runtime, domain/repositories, domain/plans, application/workflows)
cleveragents/cleveragents-core
#8938 chore(cleanup): verify all imports updated and nox passes after stub package removal
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#946
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?