API testing reads knowledge files with web/api scope#43
Open
DavertMik wants to merge 3 commits into
Open
Conversation
Wire KnowledgeTracker into the api-tester so `explorbot api` planning (Chief) and execution (Curler) prompts include endpoint-matching knowledge. Add a `scope` frontmatter field (web | api | all) and a `knowledge/api/` convention so web and API testing isolate or share knowledge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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
explorbot api(API testing) did not read knowledge files — neither Chief (planner) nor Curler (executor) ever touchedKnowledgeTracker, soendpoint:-frontmatter files written byapi init/api knowwere never read back. This wires knowledge into both API agents and adds a scope model so web and API testing can isolate or share knowledge.Changes
KnowledgeTrackeris now reusable and scope-aware: constructor accepts{ knowledgeDir, sharedDir, scope }(skips the webConfigParsersingleton when a dir is passed), matches onurl || path || endpoint, and filters by effective scope (scopefrontmatter, else directory default).<knowledge>block into the planning prompt; Curler threadsknowledgeintotest()/buildTestPrompt()and appends a<knowledge>block to the execution prompt.knowledge/api/*.md(scopeapi) plus opt-in top-level files;api init/api knownow write toknowledge/api/withendpoint:+scope: api.Scope model
`scope: web | api | all` overrides the directory default. Use `scope: all` on a top-level file for shared knowledge such as credentials.
Verification
🤖 Generated with Claude Code