Repository navigation
Implement top-level qw doctor as a toolchain/workspace health check #53
Description
Activity
🔗 Related PRs
#20 - Rewrite README around witnessed causal history [merged]
#27 - Feat: add qw warpspace locate [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
qw doctor(top-level) is referenced as planned product surface but is not implemented (onlyqw warpspace doctorexists). Now thatqw initresolves Wesley from acrateinstall source, there is a clear, useful first scope for it.Idea: implement
qw doctoras a toolchain/workspace health check that reports:cratesource) is onPATH, its path, andwesley --versionvs the manifest's declared version (with thecargo install wesley-clihint when missing),warpspace.lock.jsonis consistent withwarpspace.toml/ the manifest,It gives users a one-command answer to "is my stack toolchain set up correctly?" and is the natural home for the new crate-source resolution diagnostics. Pairs well with the manifest-validation idea.