Make consumer agent discover-vs-isolate split explicit - #10
Merged
Conversation
Keep a diagnostic mvn test as the first step when the failing scenarios are still unknown, and require headless Workbench MCP (mcp .) to isolate a known failure instead of skipping it when workbench_* tools are missing. Co-authored-by: ds-code-t <ds-code-t@users.noreply.github.com>
ds-code-t
marked this pull request as ready for review
August 26, 2026 21:17
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
2 participants
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
Make the consumer AI discover-vs-isolate split explicit so IntelliJ Copilot and other consumer agents stop skipping Workbench when
workbench_*MCP tools are missing, without forcing Workbench when a diagnosticmvn testis the right first step.Docs and exported consumer pointers only. No Workbench sync/compile behavior change, and no version bump.
Chooser order is now:
mvn testwithpkb_runvarswhen the failing scenarios are still unknown (parallel OK).mcp .). Ifworkbench_*tools are missing, start that stdio server; do not keep usingmvn testfor isolation because MCP is disconnected.mvn test.Missing
workbench_*tools is a reason to start Workbench MCP, not a reason to skip it. A multi-scenario diagnostic test is a reason to runmvn testfirst, not a reason to skip Workbench afterward.This PR targets
2.1.10, notmaster.Functionality-change coverage
AGENTS.mdand the relevant feature-map entry.PickleballGuidanceChecksplusverify_agent_contract.pyconsumer-bridge rules)AGENTS.md/ Copilot pointer; no Gherkin change)docs/agent/feature-map.mdremains accurate.docs/agent/repository-index.mdis current.Validation
python3 scripts/verify_agent_contract.pypython3 scripts/refresh_agent_index.py --checkpython3 scripts/sync_consumer_guidance.py --check./gradlew publishToMavenLocal./maven-consumer-project/mvnw -f maven-consumer-project/pom.xml -U test -Dpkb_runvars.pkb_browser=CHROME_HEADLESS -Dpkb_runvars.pkb_tags=@diagnostic-reporting(PickleballGuidanceChecks all PASS)./gradlew test— not run; docs/export-guidance change, not framework runtime@all— not run; smallest relevant tag is@diagnostic-reporting