Skip to content

refactor: remove legacy Code Map ahead of replacement - #414

Merged
sudomaggie merged 1 commit into
developfrom
harry/deprecate-legacy-code-map
Jul 18, 2026
Merged

refactor: remove legacy Code Map ahead of replacement#414
sudomaggie merged 1 commit into
developfrom
harry/deprecate-legacy-code-map

Conversation

@Harry19081

Copy link
Copy Markdown
Member

Summary

  • remove the legacy Rust Code Map crate, Tauri commands, persistence/index lifecycle, and storage reporting
  • remove frontend status/explore UI, hooks, APIs, auto-indexing, translations, and E2E coverage
  • retire use_code_map / manage_code_map agent tools, prompt guidance, policies, schemas, and wire metadata
  • add separate architecture and frontend UI audit reports

Why

The existing Code Map is being retired before the replacement implementation lands. Removing it now avoids shipping two indexing lifecycles, command surfaces, agent tool contracts, and storage formats in parallel.

Scope note

Independent code_search, semantic-search, and UI-indexing systems are unchanged.

Testing

  • cargo check
  • cargo clippy --all-targets
  • cargo test -p agent_core --lib core::tools (563 passed)
  • cargo test -p core_types --lib tool_name_constants_are_stable_wire_strings
  • cargo test -p org2 --lib new_storage_roots_are_reported
  • pnpm typecheck
  • targeted ESLint and Prettier checks
  • focused FallbackAdapter Vitest suite (14 passed)
  • exact source/test identifier and filename sweep

Remove the legacy Rust crate, Tauri commands, storage path, and indexing lifecycle.

Retire the frontend UI, hooks, APIs, auto-indexing, agent tools, prompts, translations, and obsolete E2E coverage ahead of the replacement Code Map.

Preserve the independent code search, semantic search, and UI-indexing systems.

Pre-commit hook ran. Total eslint: 0, total circular: 0
@sudomaggie
sudomaggie merged commit 1fcef44 into develop Jul 18, 2026
1 of 2 checks passed
Neonforge98 pushed a commit that referenced this pull request Jul 30, 2026
refactor: remove legacy Code Map ahead of replacement
@Harry19081
Harry19081 requested a review from sudomaggie July 30, 2026 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants