Renames root library module to altk_evolve#138
Merged
Merged
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 6 minutes and 0 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (11)
📝 WalkthroughWalkthroughThis pull request performs a comprehensive package namespace rename from Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (10)
tests/unit/test_milvus_backend.py (3)
80-81:⚠️ Potential issue | 🔴 CriticalPatch target uses stale
evolvenamespace.Update to
altk_evolve.backend.milvus.SQLiteManager.🐛 Proposed fix
- with patch("evolve.backend.milvus.SQLiteManager", return_value=db_manager): + with patch("altk_evolve.backend.milvus.SQLiteManager", return_value=db_manager): result = milvus_backend.create_namespace(namespace_id=namespace_id)Apply the same fix to all other occurrences at lines 87, 108, 127, and 145.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_milvus_backend.py` around lines 80 - 81, The test patch is targeting the old module path "evolve.backend.milvus.SQLiteManager"; update the patch target string to "altk_evolve.backend.milvus.SQLiteManager" wherever SQLiteManager is patched in tests/unit/test_milvus_backend.py (the with patch(...) calls around the milvus_backend.create_namespace and related tests), and apply the same replacement for the other occurrences mentioned (the other patch calls in this file).
19-21:⚠️ Potential issue | 🔴 CriticalPatch targets use stale
evolvenamespace — fixture will not mock correctly.The patches reference
evolve.backend.milvus.MilvusClientandevolve.backend.milvus.SentenceTransformer, but the module is nowaltk_evolve.backend.milvus. The real classes will be instantiated instead of mocks.🐛 Proposed fix
`@pytest.fixture`(scope="module") def milvus_backend() -> MilvusEntityBackend: """Create a MilvusEntityBackend instance for testing.""" - with patch("evolve.backend.milvus.MilvusClient"), patch("evolve.backend.milvus.SentenceTransformer"): + with patch("altk_evolve.backend.milvus.MilvusClient"), patch("altk_evolve.backend.milvus.SentenceTransformer"): backend = MilvusEntityBackend() return backend🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_milvus_backend.py` around lines 19 - 21, The test patch targets are using the old module path; update the mock targets so the fixtures actually patch the classes used by MilvusEntityBackend: change the patch calls that reference "evolve.backend.milvus.MilvusClient" and "evolve.backend.milvus.SentenceTransformer" to the current module path "altk_evolve.backend.milvus.MilvusClient" and "altk_evolve.backend.milvus.SentenceTransformer" so that creating MilvusEntityBackend() within the test uses the mocked MilvusClient and SentenceTransformer.
172-174:⚠️ Potential issue | 🔴 CriticalPatch target uses stale
evolvenamespace.Update to
altk_evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts.🐛 Proposed fix
- with patch("evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts", resolve_conflicts): + with patch("altk_evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts", resolve_conflicts): entities = [Entity(type=entity_update.type, content=entity_update.content, metadata={"key": "value"})]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_milvus_backend.py` around lines 172 - 174, The test patches the wrong import path for resolve_conflicts—update the patch target string in the with patch(...) call from "evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts" to "altk_evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts" so the mocked function actually overrides resolve_conflicts used by milvus_backend.update_entities (refer to the resolve_conflicts symbol and the with patch(...) block surrounding the call to milvus_backend.update_entities).tests/unit/test_conflict_resolution.py (1)
250-250:⚠️ Potential issue | 🔴 CriticalPatch target uses stale
evolvenamespace — tests will fail.The
@patchdecorator still referencesevolve.llm.conflict_resolution.conflict_resolution.completion, but the module has been renamed toaltk_evolve. This will cause the patch to target a non-existent module, and the actualcompletionfunction will not be mocked.This same issue occurs at lines 311, 354, and 401.
🐛 Proposed fix
-@patch("evolve.llm.conflict_resolution.conflict_resolution.completion") +@patch("altk_evolve.llm.conflict_resolution.conflict_resolution.completion") def test_resolve_conflicts_event_types(Apply the same fix to:
- Line 311:
test_resolve_conflicts_response_parsing- Line 354:
test_resolve_conflicts_retry_logic- Line 401:
test_resolve_conflicts_edge_cases🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_conflict_resolution.py` at line 250, Update the `@patch` target strings to use the new module namespace: replace "evolve.llm.conflict_resolution.conflict_resolution.completion" with "altk_evolve.llm.conflict_resolution.conflict_resolution.completion" in the decorator on the test function where it appears, and apply the same replacement for the other occurrences used by test_resolve_conflicts_response_parsing, test_resolve_conflicts_retry_logic, and test_resolve_conflicts_edge_cases so the completion function is mocked from the correct module.tests/unit/test_tracing.py (2)
106-107:⚠️ Potential issue | 🟡 MinorModule cache reset uses old namespace key.
This block should clear
altk_evolve.auto; currently it clearsevolve.auto, which can leave stale state between tests.🔧 Suggested fix
- if "evolve.auto" in sys.modules: - del sys.modules["evolve.auto"] + if "altk_evolve.auto" in sys.modules: + del sys.modules["altk_evolve.auto"]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_tracing.py` around lines 106 - 107, The module cache reset in tests/unit/test_tracing.py currently removes "evolve.auto" from sys.modules but should remove the actual package key "altk_evolve.auto"; update the cleanup block that checks sys.modules (the if/ del logic) to test for and delete "altk_evolve.auto" (and optionally both keys if you want backward compatibility) so tests clear the correct module namespace and avoid stale state between tests.
214-218:⚠️ Potential issue | 🟠 Major
enable_tracingcall uses an unsupportedframeworksargument.Based on the current
altk_evolve.auto.enable_tracingsignature, this kwarg is invalid and can raiseTypeError.🔧 Suggested fix
tracer = enable_tracing( project="integration-test", endpoint="http://test:8080/traces", - frameworks=[], # Empty list to skip framework instrumentation )🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_tracing.py` around lines 214 - 218, The test calls enable_tracing with an unsupported kwarg "frameworks", which will raise a TypeError; update the test to remove the frameworks=... argument and call enable_tracing(project="integration-test", endpoint="http://test:8080/traces") (i.e., use the supported signature of enable_tracing) so the call matches the altk_evolve.auto.enable_tracing function and no invalid keyword is passed.tests/unit/test_postgres_backend.py (2)
21-23:⚠️ Potential issue | 🟠 MajorPatch targets still reference deprecated
evolve.*modules.After migrating imports to
altk_evolve.*, these patches are now mis-targeted and can make tests fail or become ineffective.🔧 Suggested patch target updates
- patch("evolve.backend.postgres.psycopg") as mock_psycopg, - patch("evolve.backend.postgres.register_vector"), - patch("evolve.backend.postgres.SentenceTransformer") as mock_transformer, + patch("altk_evolve.backend.postgres.psycopg") as mock_psycopg, + patch("altk_evolve.backend.postgres.register_vector"), + patch("altk_evolve.backend.postgres.SentenceTransformer") as mock_transformer, - patch("evolve.backend.postgres.SQLiteManager", return_value=db_manager), - patch("evolve.backend.postgres.sql.Literal", side_effect=lambda value: original_literal(value)) as mock_literal, + patch("altk_evolve.backend.postgres.SQLiteManager", return_value=db_manager), + patch("altk_evolve.backend.postgres.sql.Literal", side_effect=lambda value: original_literal(value)) as mock_literal, - patch("evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts", resolve_conflicts), + patch("altk_evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts", resolve_conflicts),Also applies to: 92-94, 128-130, 155-157, 185-187, 223-223, 251-251, 275-275, 305-305
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_postgres_backend.py` around lines 21 - 23, Update all test patch targets that still reference the old "evolve.*" import path to the new "altk_evolve.*" path so the mocks actually target the migrated modules; specifically replace occurrences like patch("evolve.backend.postgres.psycopg"), patch("evolve.backend.postgres.register_vector"), and patch("evolve.backend.postgres.SentenceTransformer") (and the other listed occurrences at ~lines 92-94, 128-130, 155-157, 185-187, 223, 251, 275, 305) with patch("altk_evolve.backend.postgres.psycopg"), patch("altk_evolve.backend.postgres.register_vector"), and patch("altk_evolve.backend.postgres.SentenceTransformer") respectively so the tests mock the correct modules.
1-401:⚠️ Potential issue | 🟠 MajorRuff formatting check is currently failing for this test file.
Please run
ruff format tests/unit/test_postgres_backend.py(orruff format .) to satisfy CI.As per coding guidelines,
**/*.py: Use Ruff for linting and formatting (configured in pyproject.toml).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_postgres_backend.py` around lines 1 - 401, The test file fails Ruff formatting; run ruff format on the test file (or the repo) to auto-format it, save the resulting edits, and commit the changes so CI passes; locate the file by looking for the test functions such as test_ready, test_postgres_backend_initialization_ensures_extension_before_registering_vector, test_create_namespace, and test_update_entities to confirm formatting was applied and that only whitespace/style changes were made before pushing.tests/e2e/test_mcp.py (1)
187-187:⚠️ Potential issue | 🔴 CriticalPatch target still uses the old
evolve.*module path.The
@patchdecorator targets"evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts", but the module has been renamed toaltk_evolve. This patch will not intercept the actual function call, causing the test to invoke the real LLM-based conflict resolution instead of the mock.🐛 Proposed fix
- patch_target = "evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts" + patch_target = "altk_evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/e2e/test_mcp.py` at line 187, The patch target string is using the old module path "evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts" so the `@patch` in tests/e2e/test_mcp.py doesn't intercept calls; update patch_target to the new module path (replace the leading "evolve" with "altk_evolve") so it points to "altk_evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts" (i.e., ensure the string used in the `@patch` decorator matches the current module where resolve_conflicts is defined).tests/unit/test_client.py (1)
187-187:⚠️ Potential issue | 🔴 Critical
monkeypatch.setattrtargets still use the oldevolve.*module path.The monkeypatch targets
"evolve.frontend.client.evolve_client.extract_facts_from_messages", but the module has been renamed toaltk_evolve.frontend.client.evolve_client. These patches will fail to intercept the actual function call, causing tests to:
- Invoke the real
extract_facts_from_messages(LLM call) intest_store_user_facts_uses_trimmed_message- Fail the assertion in
test_store_user_facts_skips_none_empty_or_whitespacebecause the function won't be patched🐛 Proposed fix
- monkeypatch.setattr("evolve.frontend.client.evolve_client.extract_facts_from_messages", fail_extract) + monkeypatch.setattr("altk_evolve.frontend.client.evolve_client.extract_facts_from_messages", fail_extract)- monkeypatch.setattr("evolve.frontend.client.evolve_client.extract_facts_from_messages", extract) + monkeypatch.setattr("altk_evolve.frontend.client.evolve_client.extract_facts_from_messages", extract)Also applies to: 212-212
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/unit/test_client.py` at line 187, Update the monkeypatch targets to use the renamed module path so the patch actually replaces extract_facts_from_messages: change any monkeypatch.setattr calls that reference "evolve.frontend.client.evolve_client.extract_facts_from_messages" to "altk_evolve.frontend.client.evolve_client.extract_facts_from_messages" (both occurrences around the test functions test_store_user_facts_uses_trimmed_message and test_store_user_facts_skips_none_empty_or_whitespace) so the fail_extract stub is applied instead of calling the real function.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/examples/hello_world/claude.md`:
- Around line 35-37: Several fenced code blocks in the Claude example are
unlabeled (e.g., the blocks containing "where was the photo `@sample.jpg` taken?
use exif metadata.", "summarize what steps you took, including tool calls,
failed attempts, and reasoning guidelines.", "/evolve-lite:learn", "/clear", and
"what focal length was used to take the photo `@sample.jpg`? use exif metadata")
which triggers MD040; fix by adding a language identifier (e.g., change each
opening ``` to ```text) for those exact fenced blocks so they become labeled
code fences (use "text" unless another language is appropriate).
In `@docs/guides/low-code-tracing.md`:
- Line 10: Update the remaining prose and diagram labels that still mention the
old module name "evolve.auto" so they match the code snippets' new name
"altk_evolve.auto"; specifically replace occurrences in diagram labels (e.g.,
A1["import altk_evolve.auto"]) and any troubleshooting/table rows or inline
prose that reference "evolve.auto" so they read "altk_evolve.auto", ensuring all
mentions across the guide are consistent with the updated import.
In `@README.md`:
- Around line 56-60: Update the remaining outdated module paths in README.md so
startup commands are consistent: replace occurrences of the old module path
fragment like "evolve.frontend.mcp..." with the new "altk_evolve/frontend/ui"
style used in the diff, ensuring the npm commands and cd targets in the startup
sections (around the blocks spanning 63-74 and 80-84) all point to
altk_evolve/frontend/ui; search for any other references to
"evolve.frontend.mcp" or similar and standardize them to the new path string
used in the snippet.
In `@tests/e2e/test_e2e_pipeline.py`:
- Line 9: Remove the unused import phoenix_settings from the top-level import
list in the test (the import statement "from altk_evolve.config.phoenix import
phoenix_settings"); delete that name or the entire import line so the symbol is
not referenced, then run the linter/formatter (Ruff) to verify the F401 warning
is resolved.
In `@tests/unit/test_cli.py`:
- Around line 9-12: The tests import CLI and schema from altk_evolve but the
mock targets still reference the old evolve.* module path; update every
unittest.mock.patch string in tests/unit/test_cli.py (all patch(...) and
`@patch`(...) usages) to use the new altk_evolve.* import path so the patch
targets match symbols like app, Namespace, RecordedEntity, EntityUpdate and the
exception classes now imported from altk_evolve.
In `@tests/unit/test_mcp_server.py`:
- Around line 6-7: The test's mock.patch targets were left pointing at the old
evolve namespace and therefore don't intercept the imported save_trajectory and
create_entity symbols; update the mock.patch targets to the new altk_evolve
namespace (e.g., patch "altk_evolve.frontend.mcp.mcp_server.save_trajectory" and
"altk_evolve.frontend.mcp.mcp_server.create_entity" for the patches at the two
locations mentioned) so the test mocks the actual imported functions (also
update any other patch targets in the same test that refer to the old evolve.*
path to altk_evolve.*).
In `@tests/unit/test_tracing.py`:
- Line 65: The tests are patching the wrong module path; replace all patch
targets that use "evolve.auto.is_already_instrumented" with
"altk_evolve.auto.is_already_instrumented" so the code under test is actually
affected—update every occurrence in tests/unit/test_tracing.py (e.g., the patch
call at the lines referencing is_already_instrumented around the blocks at the
original 65, 74, 88, and 210) to point to
altk_evolve.auto.is_already_instrumented.
---
Outside diff comments:
In `@tests/e2e/test_mcp.py`:
- Line 187: The patch target string is using the old module path
"evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts" so the
`@patch` in tests/e2e/test_mcp.py doesn't intercept calls; update patch_target to
the new module path (replace the leading "evolve" with "altk_evolve") so it
points to
"altk_evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts"
(i.e., ensure the string used in the `@patch` decorator matches the current module
where resolve_conflicts is defined).
In `@tests/unit/test_client.py`:
- Line 187: Update the monkeypatch targets to use the renamed module path so the
patch actually replaces extract_facts_from_messages: change any
monkeypatch.setattr calls that reference
"evolve.frontend.client.evolve_client.extract_facts_from_messages" to
"altk_evolve.frontend.client.evolve_client.extract_facts_from_messages" (both
occurrences around the test functions test_store_user_facts_uses_trimmed_message
and test_store_user_facts_skips_none_empty_or_whitespace) so the fail_extract
stub is applied instead of calling the real function.
In `@tests/unit/test_conflict_resolution.py`:
- Line 250: Update the `@patch` target strings to use the new module namespace:
replace "evolve.llm.conflict_resolution.conflict_resolution.completion" with
"altk_evolve.llm.conflict_resolution.conflict_resolution.completion" in the
decorator on the test function where it appears, and apply the same replacement
for the other occurrences used by test_resolve_conflicts_response_parsing,
test_resolve_conflicts_retry_logic, and test_resolve_conflicts_edge_cases so the
completion function is mocked from the correct module.
In `@tests/unit/test_milvus_backend.py`:
- Around line 80-81: The test patch is targeting the old module path
"evolve.backend.milvus.SQLiteManager"; update the patch target string to
"altk_evolve.backend.milvus.SQLiteManager" wherever SQLiteManager is patched in
tests/unit/test_milvus_backend.py (the with patch(...) calls around the
milvus_backend.create_namespace and related tests), and apply the same
replacement for the other occurrences mentioned (the other patch calls in this
file).
- Around line 19-21: The test patch targets are using the old module path;
update the mock targets so the fixtures actually patch the classes used by
MilvusEntityBackend: change the patch calls that reference
"evolve.backend.milvus.MilvusClient" and
"evolve.backend.milvus.SentenceTransformer" to the current module path
"altk_evolve.backend.milvus.MilvusClient" and
"altk_evolve.backend.milvus.SentenceTransformer" so that creating
MilvusEntityBackend() within the test uses the mocked MilvusClient and
SentenceTransformer.
- Around line 172-174: The test patches the wrong import path for
resolve_conflicts—update the patch target string in the with patch(...) call
from "evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts" to
"altk_evolve.llm.conflict_resolution.conflict_resolution.resolve_conflicts" so
the mocked function actually overrides resolve_conflicts used by
milvus_backend.update_entities (refer to the resolve_conflicts symbol and the
with patch(...) block surrounding the call to milvus_backend.update_entities).
In `@tests/unit/test_postgres_backend.py`:
- Around line 21-23: Update all test patch targets that still reference the old
"evolve.*" import path to the new "altk_evolve.*" path so the mocks actually
target the migrated modules; specifically replace occurrences like
patch("evolve.backend.postgres.psycopg"),
patch("evolve.backend.postgres.register_vector"), and
patch("evolve.backend.postgres.SentenceTransformer") (and the other listed
occurrences at ~lines 92-94, 128-130, 155-157, 185-187, 223, 251, 275, 305) with
patch("altk_evolve.backend.postgres.psycopg"),
patch("altk_evolve.backend.postgres.register_vector"), and
patch("altk_evolve.backend.postgres.SentenceTransformer") respectively so the
tests mock the correct modules.
- Around line 1-401: The test file fails Ruff formatting; run ruff format on the
test file (or the repo) to auto-format it, save the resulting edits, and commit
the changes so CI passes; locate the file by looking for the test functions such
as test_ready,
test_postgres_backend_initialization_ensures_extension_before_registering_vector,
test_create_namespace, and test_update_entities to confirm formatting was
applied and that only whitespace/style changes were made before pushing.
In `@tests/unit/test_tracing.py`:
- Around line 106-107: The module cache reset in tests/unit/test_tracing.py
currently removes "evolve.auto" from sys.modules but should remove the actual
package key "altk_evolve.auto"; update the cleanup block that checks sys.modules
(the if/ del logic) to test for and delete "altk_evolve.auto" (and optionally
both keys if you want backward compatibility) so tests clear the correct module
namespace and avoid stale state between tests.
- Around line 214-218: The test calls enable_tracing with an unsupported kwarg
"frameworks", which will raise a TypeError; update the test to remove the
frameworks=... argument and call enable_tracing(project="integration-test",
endpoint="http://test:8080/traces") (i.e., use the supported signature of
enable_tracing) so the call matches the altk_evolve.auto.enable_tracing function
and no invalid keyword is passed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: b9ca9247-a276-425d-b0d9-31601a3727b2
⛔ Files ignored due to path filters (3)
altk_evolve/frontend/ui/package-lock.jsonis excluded by!**/package-lock.jsondocs/assets/sample.jpgis excluded by!**/*.jpguv.lockis excluded by!**/*.lock
📒 Files selected for processing (112)
.github/workflows/check-code.yaml.secrets.baselineAGENTS.mdMANIFEST.inREADME.mdaltk_evolve/__init__.pyaltk_evolve/auto/__init__.pyaltk_evolve/backend/__init__.pyaltk_evolve/backend/base.pyaltk_evolve/backend/filesystem.pyaltk_evolve/backend/milvus.pyaltk_evolve/backend/postgres.pyaltk_evolve/cli/__init__.pyaltk_evolve/cli/cli.pyaltk_evolve/config/__init__.pyaltk_evolve/config/evolve.pyaltk_evolve/config/filesystem.pyaltk_evolve/config/llm.pyaltk_evolve/config/milvus.pyaltk_evolve/config/phoenix.pyaltk_evolve/config/postgres.pyaltk_evolve/db/__init__.pyaltk_evolve/db/sqlite_manager.pyaltk_evolve/frontend/__init__.pyaltk_evolve/frontend/api/__init__.pyaltk_evolve/frontend/api/routes.pyaltk_evolve/frontend/client/__init__.pyaltk_evolve/frontend/client/evolve_client.pyaltk_evolve/frontend/mcp/__init__.pyaltk_evolve/frontend/mcp/__main__.pyaltk_evolve/frontend/mcp/mcp_server.pyaltk_evolve/frontend/ui/.gitignorealtk_evolve/frontend/ui/README.mdaltk_evolve/frontend/ui/eslint.config.jsaltk_evolve/frontend/ui/index.htmlaltk_evolve/frontend/ui/package.jsonaltk_evolve/frontend/ui/setupTests.tsaltk_evolve/frontend/ui/src/App.tsxaltk_evolve/frontend/ui/src/components/ConfirmDialog.tsxaltk_evolve/frontend/ui/src/components/CreateEntityModal.tsxaltk_evolve/frontend/ui/src/components/Dashboard.tsxaltk_evolve/frontend/ui/src/components/EntityDetailModal.tsxaltk_evolve/frontend/ui/src/components/EntityExplorer.test.tsxaltk_evolve/frontend/ui/src/components/EntityExplorer.tsxaltk_evolve/frontend/ui/src/components/EntityTable.tsxaltk_evolve/frontend/ui/src/components/Namespaces.test.tsxaltk_evolve/frontend/ui/src/components/Namespaces.tsxaltk_evolve/frontend/ui/src/hooks/useApi.tsaltk_evolve/frontend/ui/src/hooks/useDebounce.tsaltk_evolve/frontend/ui/src/index.cssaltk_evolve/frontend/ui/src/main.tsxaltk_evolve/frontend/ui/tsconfig.app.jsonaltk_evolve/frontend/ui/tsconfig.jsonaltk_evolve/frontend/ui/tsconfig.node.jsonaltk_evolve/frontend/ui/vite.config.tsaltk_evolve/llm/__init__.pyaltk_evolve/llm/conflict_resolution/__init__.pyaltk_evolve/llm/conflict_resolution/conflict_resolution.pyaltk_evolve/llm/conflict_resolution/prompts/conflict_resolution.jinja2altk_evolve/llm/conflict_resolution/prompts/default_conflict_resolution.jinja2altk_evolve/llm/fact_extraction/__init__.pyaltk_evolve/llm/fact_extraction/categorization.pyaltk_evolve/llm/fact_extraction/fact_extraction.pyaltk_evolve/llm/fact_extraction/prompts/fact_extraction.jinja2altk_evolve/llm/fact_extraction/prompts/fact_extraction_predefined.jinja2altk_evolve/llm/tips/__init__.pyaltk_evolve/llm/tips/clustering.pyaltk_evolve/llm/tips/prompts/combine_tips.jinja2altk_evolve/llm/tips/prompts/generate_tips.jinja2altk_evolve/llm/tips/tips.pyaltk_evolve/schema/__init__.pyaltk_evolve/schema/conflict_resolution.pyaltk_evolve/schema/core.pyaltk_evolve/schema/exceptions.pyaltk_evolve/schema/policy.pyaltk_evolve/schema/tips.pyaltk_evolve/sync/__init__.pyaltk_evolve/sync/phoenix_sync.pyaltk_evolve/utils/__init__.pyaltk_evolve/utils/utils.pydemo/workspace/.evolve/entities/guideline/on-macos-use-mdls-as-the-primary-tool-for-extracting-image.mddemo/workspace/.evolve/entities/guideline/when-running-exif-extraction-commands-use-a-fallback-chain.mddocs/examples/hello_world/bob.mddocs/examples/hello_world/claude.mddocs/guides/configuration.mddocs/guides/low-code-tracing.mddocs/guides/phoenix-sync.mddocs/installation/index.mddocs/reference/policies.mdevolve/llm/__init__.pyevolve/sync/__init__.pyexamples/low_code/litellm_demo.pyexamples/low_code/openai_agents_demo.pyexamples/low_code/simple_openai.pyexamples/low_code/smolagents_demo.pymkdocs.yamlpyproject.tomltests/e2e/test_e2e_pipeline.pytests/e2e/test_mcp.pytests/llm/test_long_conflict_resolution.pytests/unit/test_cli.pytests/unit/test_client.pytests/unit/test_clustering.pytests/unit/test_combine_tips.pytests/unit/test_conflict_resolution.pytests/unit/test_mcp_server.pytests/unit/test_milvus_backend.pytests/unit/test_phoenix_sync.pytests/unit/test_policy_schema.pytests/unit/test_postgres_backend.pytests/unit/test_tips.pytests/unit/test_tracing.py
💤 Files with no reviewable changes (2)
- evolve/sync/init.py
- evolve/llm/init.py
Comment on lines
+35
to
+37
| ``` | ||
| where was the photo @sample.jpg taken? use exif metadata. | ||
| ``` |
There was a problem hiding this comment.
Add language identifiers to fenced code blocks (MD040).
These fences are currently unlabeled and trigger markdownlint warnings.
🔧 Suggested markdown fix
-```
+```text
where was the photo `@sample.jpg` taken? use exif metadata.- +text
summarize what steps you took, including tool calls, failed attempts, and reasoning guidelines.
-```
+```text
/evolve-lite:learn
- +text
/clear
-```
+```text
what focal length was used to take the photo `@sample.jpg`? use exif metadata
</details>
Also applies to: 41-43, 48-50, 55-57, 60-62
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.22.0)</summary>
[warning] 35-35: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
Verify each finding against the current code and only fix it if needed.
In @docs/examples/hello_world/claude.md around lines 35 - 37, Several fenced
code blocks in the Claude example are unlabeled (e.g., the blocks containing
"where was the photo @sample.jpg taken? use exif metadata.", "summarize what
steps you took, including tool calls, failed attempts, and reasoning
guidelines.", "/evolve-lite:learn", "/clear", and "what focal length was used to
take the photo @sample.jpg? use exif metadata") which triggers MD040; fix by
adding a language identifier (e.g., change each opening totext) for
those exact fenced blocks so they become labeled code fences (use "text" unless
another language is appropriate).
</details>
<!-- fingerprinting:phantom:poseidon:hawk:cc388200-6596-4b0b-aec2-6279934273e3 -->
<!-- This is an auto-generated comment by CodeRabbit -->
| flowchart TB | ||
| subgraph Agent["Your Agent"] | ||
| A1["import evolve.auto"] | ||
| A1["import altk_evolve.auto"] |
There was a problem hiding this comment.
Complete the module-name rename in surrounding prose/diagram.
The code snippets are updated, but the guide still references evolve.auto in non-snippet text (e.g., diagram label and troubleshooting row). Please align those to altk_evolve.auto as well.
Suggested fix
- subgraph Evolve["evolve.auto Module"]
+ subgraph Evolve["altk_evolve.auto Module"]
-| `ModuleNotFoundError: evolve.auto` | Install: `pip install -e path/to/evolve_repo` or add to PYTHONPATH |
+| `ModuleNotFoundError: altk_evolve.auto` | Install: `pip install -e path/to/evolve_repo` or add to PYTHONPATH |Also applies to: 52-53, 80-81, 102-103, 131-132, 153-154
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/guides/low-code-tracing.md` at line 10, Update the remaining prose and
diagram labels that still mention the old module name "evolve.auto" so they
match the code snippets' new name "altk_evolve.auto"; specifically replace
occurrences in diagram labels (e.g., A1["import altk_evolve.auto"]) and any
troubleshooting/table rows or inline prose that reference "evolve.auto" so they
read "altk_evolve.auto", ensuring all mentions across the guide are consistent
with the updated import.
Comment on lines
+56
to
+60
| > cd altk_evolve/frontend/ui | ||
| > npm ci && npm run build | ||
| > cd ../../../ | ||
| > ``` | ||
| > See `evolve/frontend/ui/README.md` for more frontend development details. | ||
| > See `altk_evolve/frontend/ui/README.md` for more frontend development details. |
There was a problem hiding this comment.
Fix remaining old module paths in startup commands.
The section now references altk_evolve paths, but Line 65 and Line 73 still use evolve.frontend.mcp.... This leaves README instructions inconsistent.
Suggested fix
-uv run python -m evolve.frontend.mcp
+uv run python -m altk_evolve.frontend.mcp
-uv run uvicorn evolve.frontend.mcp.mcp_server:app --host 127.0.0.1 --port 8000
+uv run uvicorn altk_evolve.frontend.mcp.mcp_server:app --host 127.0.0.1 --port 8000Also applies to: 63-74, 80-84
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README.md` around lines 56 - 60, Update the remaining outdated module paths
in README.md so startup commands are consistent: replace occurrences of the old
module path fragment like "evolve.frontend.mcp..." with the new
"altk_evolve/frontend/ui" style used in the diff, ensuring the npm commands and
cd targets in the startup sections (around the blocks spanning 63-74 and 80-84)
all point to altk_evolve/frontend/ui; search for any other references to
"evolve.frontend.mcp" or similar and standardize them to the new path string
used in the snippet.
vinodmut
added a commit
to vinodmut/kaizen
that referenced
this pull request
Apr 3, 2026
Dir was accidentally committed in a26429d (AgentToolkit#138). Expand .gitignore pattern from /.evolve to .evolve so it is ignored in subdirs too.
This was referenced Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
New Features
Refactor
evolvetoaltk-evolveacross all modules and documentation.Chores