chore(merge_configs): remove bot-introduced duplicate from runtime.py and restore canonical import #21
No reviewers
Labels
No labels
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#11 feat(merge_configs): expose public merge_configs(*dicts) API per §3.1 deep-merge algorithm
cleveragents/cleveractors-core
Reference
cleveragents/cleveractors-core!21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/remove-duplicate-merge-configs"
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?
Summary
Closes #11
Bot commit
e7a7d39(pushed directly tomasterafter PR #19 was merged) introduced a duplicatemerge_configsimplementation inruntime.pyand broke the__init__.pyexport wiring. This PR is a pure cleanup — no new functionality.What the Bot Did (undone here)
In
src/cleveractors/runtime.py, the bot added:merge_configs(*dicts)function (duplicate of the canonical one inconfig_utils.py)_deep_merge_two(base, override)helper# Config mergingsectionIn
src/cleveractors/__init__.py, the bot:_legacy_merge_configs(hiding it from consumers)merge_configsfromruntimeinto the import block and__all__Changes in This PR
src/cleveractors/runtime.py# Config mergingsection:merge_configs()and_deep_merge_two()are goneruffB007 lint violation: renamed unused loop variableagent_name→_agent_namein_build_factory_configmerge_configsentrysrc/cleveractors/__init__.pyfrom cleveractors.config_utils import merge_configs(no alias)merge_configsfrom thefrom cleveractors.runtime import (...)blockmerge_configsremains in__all__— now correctly backed by the canonicalconfig_utilsimplementationsrc/cleveractors/config_utils.pyPR Review: !21 (Ticket #11)
Verdict: ✅ Approve
This is a surgical, two-file cleanup PR. All four review agents returned zero findings. The PR correctly and completely undoes the bot's damage from commit
e7a7d39.Critical Issues
None
Major Issues
None
Minor Issues
None
Nits
None
Summary
All four review lenses — spec compliance, bug detection, test coverage, and performance/security — came back clean.
Spec compliance: All three requirements from the bot comment (#282188) are fully satisfied:
merge_configsand_deep_merge_twoare gone fromruntime.py,__init__.pynow importsmerge_configsdirectly fromconfig_utilswith no alias, andmerge_configsremains in__all__. No traces of the bot's duplicate code remain anywhere in the codebase.Bug detection: No dangling imports, no broken references. The bug agent also noted a latent correctness improvement: the removed
runtime.pyduplicate was actually worse than the canonical implementation — it raisedConfigurationErrorinstead ofTypeErroron invalid arguments, which would have silently diverged from the tested contract. Restoring the canonical implementation fixes this.Test coverage: The bot commit added no tests for its duplicate, so no test changes are needed. All 18 Behave scenarios, 5 Robot integration tests, and 4 ASV benchmarks continue to import from the public API and correctly target the canonical
config_utils.merge_configs.Performance/security: Removing the duplicate is a net positive — slightly faster import time, no new attack surface, and eliminates the maintenance drift risk of two implementations diverging over time.
The PR is ready to merge.