harshitsinghbhandari fcdbe24d6c fix: prevent one project's bad config from breaking shared plugin ... When multiple projects share the same external plugin, a misconfiguration in one project (wrong expectedPluginName) would prevent the plugin from being registered at all, silently breaking it for all projects. Fix by: 1. Register the plugin FIRST, before validating individual project configs 2. Validate each project's config in its own try-catch 3. Log validation errors but continue processing other projects This ensures: - Plugin is always registered if it loads successfully - Projects with correct config get updated - Projects with bad config get a warning but don't break others - Misconfigured projects fail at point of use with clearer errors Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2026-04-02 21:28:53 +05:30
..
ao	chore: version packages	2026-03-29 09:21:26 +00:00
cli	fix: handle optional plugin field in CLI and web packages	2026-04-02 19:19:44 +05:30
core	fix: prevent one project's bad config from breaking shared plugin	2026-04-02 21:28:53 +05:30
integration-tests	extend opencode discovery timeout, include integration tests in pnpm test	2026-03-29 16:44:53 +05:30
plugins	feat: standardize agent plugins — shared hooks, activity JSONL, backfill aider/opencode (#755)	2026-04-01 21:50:07 +05:30
web	fix: handle optional plugin field in CLI and web packages	2026-04-02 19:19:44 +05:30