Skip to content

refactor(core): centralize boundary normalization - #43931

Closed
kitlangton wants to merge 1 commit into
v2from
centralize-boundary-normalization
Closed

refactor(core): centralize boundary normalization#43931
kitlangton wants to merge 1 commit into
v2from
centralize-boundary-normalization

Conversation

@kitlangton

Copy link
Copy Markdown
Contributor

What

Centralize repeated normalization at ripgrep, MCP, and provider boundaries. Each helper exactly preserves the previous path, error, and record semantics while removing local duplication and assertions.

How

  • Reuse one path normalizer across ripgrep glob, find, and grep results.
  • Reuse one unknown-to-Error conversion across seven MCP promise boundaries.
  • Use the canonical AI package isRecord guard when merging provider overlays.

Scope

Behavior-preserving Core cleanup only; no path policy, MCP recovery, provider merge, or public API changes.

Testing

  • bun run test test/ripgrep.test.ts test/mcp.test.ts test/provider.test.ts (38 passed)
  • bun typecheck from packages/core
  • Push hook: bun turbo typecheck --concurrency=3 (40-package workspace)

@kitlangton

Copy link
Copy Markdown
Contributor Author

Consolidated into #43929 so the cleanup ships as one coherent persistence and boundary-normalization review.

@kitlangton kitlangton closed this Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant