Repository navigation
feat: vendored PyYAML config, single version source, launcher fixes - #10
Merged
9thLevelSoftware merged 1 commit intoOct 1, 2026
Merged
Conversation
- CLODEX.md front matter is parsed with yaml.safe_load (real PyYAML when installed, vendored pure-Python 6.0.3 under clodex/_vendor for npm installs, which run on a bare system Python). Nested keys now work, bad YAML raises ConfigError, empty sections keep their defaults. Output is identical to the old parser for the shipped CLODEX.md. - clodex.__version__ is the single source: pyproject reads it dynamically, the MCP server reports it, and a test keeps package.json, both plugin manifests and install/uninstall scripts in sync. - pyproject: readme, pyyaml dependency, clodex-mcp-server script, package discovery (wheel excludes the vendored copy). - package.json files: ship every clodex/**/*.py plus the vendored license; a test checks `npm pack --dry-run` lists every module. - Launchers operate on the caller's repo: clodex.ps1 and mcp-bridge/bin/clodex-mcp-server no longer cd into the Clodex checkout; clodex.ps1 survives the Microsoft Store python3 stub and tries `py -3`; npm launcher tries `py -3`, 3.14, 3.13, 3.12. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (11 files)
(Vendored Reviewed by minimax-m3 · Input: 0 · Output: 0 · Cached: 0 |
3 of 4 tasks
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
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
Stacked on #9 (PR 3 of the modernization plan).
CLODEX.mdfront matter now usesyaml.safe_load— real PyYAML when installed, a vendored pure-Python PyYAML 6.0.3 (clodex/_vendor, MIT, sha256 recorded inVENDORED.md) for npm installs on a bare system Python. Nested keys work, bad YAML raisesConfigError, empty sections keep defaults. Parsed output is identical to the old parser for the shippedCLODEX.md(verified).clodex.__version__is the single source (pyproject dynamic, MCPserverInfo); a test keeps package.json, both plugin manifests and install/uninstall scripts in sync.pyyaml>=6dependency,clodex-mcp-serverscript, package discovery (wheel excludes the vendored copy).files: ships allclodex/**/*.py+ vendored license; test checksnpm pack --dry-runlists every module.clodex.ps1andmcp-bridge/bin/clodex-mcp-serverno longercdinto the Clodex checkout;clodex.ps1survives the Microsoft Storepython3stub and triespy -3; the npm launcher triespy -3, 3.14, 3.13, 3.12.Test plan
pip install .→ real PyYAML used,clodexandclodex-mcp-serverrunclodex doctorworks against the caller's repoclodex.ps1(Windows PowerShell 5.1 and pwsh 7) and the MCP bridge report the caller's repo🤖 Generated with Claude Code