Skip to content

Explore/chromadb 1x compat - #22

Closed
apajon wants to merge 17 commits into
mainfrom
explore/chromadb-1x-compat
Closed

Explore/chromadb 1x compat#22
apajon wants to merge 17 commits into
mainfrom
explore/chromadb-1x-compat

Conversation

@apajon

@apajon apajon commented Apr 16, 2026

Copy link
Copy Markdown
Owner
  • validation structurelle
  • validation retrieval
  • validation usage
  • validation MCP runtime
  • positionnement expérimental

point bloquant principal :

  • le runtime MCP sur cible reconstruite
    1.x n’est pas encore suffisamment validé/supportable

apajon and others added 17 commits April 15, 2026 14:45
Document the ChromaDB 1.x compatibility exploration and add an exploration-only MCP launcher that bypasses the stable branch guardrails for isolated testing.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add a conservative palace detector that classifies a palace as chroma_0_6, chroma_1_x, or unknown using manifest-first evidence and a narrow structural fallback, with unit tests.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Document the detector decision rules, ambiguity handling, and example outputs, and link the new documentation from the README.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add a stable-path palace safety gate that blocks unsafe read, write, create, and repair flows unless the detected palace format is chroma_0_6. Wire it into init, mine, health checks, MCP startup, and verify, with unit coverage.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Document the stable safety gate policy, guarded flows, and blocked-versus-allowed behavior, and surface the feature in the README.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Document the feasibility, risks, required building blocks, validation checklist, and recommendation for a source-preserving ChromaDB reconstruction migration flow, and link the assessment from the README.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Move the generated Copilot MCP config to .mcp.json, switch validation to the mcpServers schema, and add legacy .vscode/mcp.json migration handling in update.sh.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Update the README, MCP docs, troubleshooting notes, update workflow guide, and example config to reflect Copilot CLI's .mcp.json format and the jq-based migration path.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@apajon

apajon commented Apr 17, 2026

Copy link
Copy Markdown
Owner Author

This PR has been split into smaller, focused PRs for clarity and safer review:

Closing this PR to avoid confusion. The work continues in the split branches.

@apajon apajon closed this Apr 17, 2026
@apajon
apajon deleted the explore/chromadb-1x-compat branch April 17, 2026 16:21
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.

1 participant