fix(plugins): warn on invalid install default choice#71011
Conversation
Greptile SummaryThis PR adds two new diagnostic warnings — Confidence Score: 5/5Safe to merge — changes are additive warnings only with no behavioral regressions. All new logic is guarded by mutually exclusive conditions (invalid-default-choice and default-choice-missing-source cannot both fire), tests cover all three new warning paths, and the two existing warning types are unaffected. No P0 or P1 findings. No files require special attention. Reviews (1): Last reviewed commit: "Merge branch 'main' into feat/plugin-ins..." | Re-trigger Greptile |
Summary
openclaw.install.defaultChoicevaluesdefaultChoicepoints at an unavailable source, including invalid npm specsWhy
Phase 1 source-plane diagnostics should explain malformed install metadata without breaking existing plugins. These warnings keep catalog facts explicit while preserving compatibility: invalid or impossible defaults warn in
installSource.warnings; install behavior does not reject them.Validation
pnpm test src/plugins/install-source-info.test.ts src/plugins/provider-install-catalog.test.ts src/channels/plugins/contracts/channel-catalog.contract.test.tspnpm format:check src/plugins/install-source-info.ts src/plugins/install-source-info.test.ts docs/plugins/architecture-internals.md docs/plugins/manifest.md CHANGELOG.mdNotes
pnpm check:changedcurrently fails insrc/plugin-sdk/provider-tools.tswithTS2322because a compat config is missingsupportsLongCacheRetention; this branch does not touch that file.