Repository navigation
docs(knowledge): re-sync the hand-written corpus to the shipped 4.4 engines and 3.2.4 agents - #106
Merged
Merged
Conversation
…ngines and 3.2.4 agents
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
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.
Follow-up to #105. The hand-written
_knowledge/corpus and theversionsexample indocs/tools.mdstill described the 4.2.0/3.1.0 train, and several of the corpus facts no longer matched the repos. I checked each one against a shallow clone of every repo at its release tag (guard-core-go v4.4.1, guard-core-php v4.4.0, guard-core-rs v4.4.0, the four agents at v3.2.4, guard-core-app master at tag 2026.10.21).manifest.json: versions now match the tags (theversionstool reports them asknowledge_bundled_for), and the 7rennf93/site URLs point atGuard-Core/.guard-agent-php/3.2.4(src/Version.php:17), notguard-agent/3.1.0.go 1.26.0and the full direct-dependency list. The README now carries usage, and a SKILL.md ships underguardcore/.agents/. The runners and Go xfail files are listed by name.go.modrequires guard-core-go/v4 forexamples/basic_usageand the build-info version lookup inversion.go.bin/conformance_cost.phpexists, but no Makefile target, composer script or workflow runs it.agentHandler(GuardEngine::setAgentHandler()).xfail_baseline.tomlis no longer empty: it holds 6safety_gatescases.docs/configuration.md, where the corpus previously cited old behavior-rule and route-order gaps that it no longer lists.docs/exists, and CLAUDE.md is no longer a copy of AGENTS.md.guard-corefeature (bridge::GuardAgentTelemetry).backend/guard-core-api/guard_core_api/.agents/, andTelemetryResponsehas eight fields (telemetry_models.py:48-58).ecosystem.py: the Go, PHP and Rust agentintegrationtext follows the same facts. fix(registry): re-sync the ecosystem registry to the shipped 4.4 engines and 3.2.4 agents #105 wrongly listedbin/conformance_cost.phpamong the runners, and the PHP conformance line now names the runnersmake testactually runs.docs/tools.md: the example is the realversions()output from this branch.Local run:
uv run pytest157 passed; pre-commit on the changed files, ruff, mypy andpymarkdownlntondocs/tools.mdall pass.Not changed: the vendored
_docs/(docs-drift passes on master), the release version, and the CHANGELOG.