Skip to content

docs(knowledge): re-sync the hand-written corpus to the shipped 4.4 engines and 3.2.4 agents - #106

Merged
rennf93 merged 1 commit into
masterfrom
docs/knowledge-resync-4.4
Oct 21, 2026
Merged

rennf93 merged 1 commit into
masterfrom
docs/knowledge-resync-4.4

Conversation

@rennf93

@rennf93 rennf93 commented Oct 21, 2026

Copy link
Copy Markdown
Member

Follow-up to #105. The hand-written _knowledge/ corpus and the versions example in docs/tools.md still 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).

  1. manifest.json: versions now match the tags (the versions tool reports them as knowledge_bundled_for), and the 7 rennf93/ site URLs point at Guard-Core/.
  2. Versions, tags and install lines in every index.md. guard-agent-php's User-Agent is guard-agent-php/3.2.4 (src/Version.php:17), not guard-agent/3.1.0.
  3. Facts that had drifted:
    • Go: go 1.26.0 and the full direct-dependency list. The README now carries usage, and a SKILL.md ships under guardcore/.agents/. The runners and Go xfail files are listed by name.
    • guard-agent-go: its packages still import only go-redis, but go.mod requires guard-core-go/v4 for examples/basic_usage and the build-info version lookup in version.go.
    • PHP:
      • AGENTS.md exists, and the README has 364 lines.
      • The PCRE2 note now follows the README's "Detection limits" section: the affected pattern families are skipped above 15360 bytes, where the note said the engine fails with a 500.
      • Adapters resolve the engine from Packagist with no path repository.
      • bin/conformance_cost.php exists, but no Makefile target, composer script or workflow runs it.
      • guard-agent-php also requires ext-openssl, and the adapters forward an optional agentHandler (GuardEngine::setAgentHandler()).
    • Rust:
      • xfail_baseline.toml is no longer empty: it holds 6 safety_gates cases.
      • The gaps now quote 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-agent-rs has an optional guard-core feature (bridge::GuardAgentTelemetry).
    • guard-core-app: a SKILL.md ships under backend/guard-core-api/guard_core_api/.agents/, and TelemetryResponse has eight fields (telemetry_models.py:48-58).
  4. ecosystem.py: the Go, PHP and Rust agent integration text follows the same facts. fix(registry): re-sync the ecosystem registry to the shipped 4.4 engines and 3.2.4 agents #105 wrongly listed bin/conformance_cost.php among the runners, and the PHP conformance line now names the runners make test actually runs.
  5. docs/tools.md: the example is the real versions() output from this branch.

Local run: uv run pytest 157 passed; pre-commit on the changed files, ruff, mypy and pymarkdownlnt on docs/tools.md all pass.

Not changed: the vendored _docs/ (docs-drift passes on master), the release version, and the CHANGELOG.

@rennf93 rennf93 added documentation Docs, README, CHANGELOG, governance files no-issue Chore or dependency PR that does not need an issue labels Oct 21, 2026
@rennf93
rennf93 merged commit a9e5211 into master Oct 21, 2026
16 checks passed
@rennf93
rennf93 deleted the docs/knowledge-resync-4.4 branch October 22, 2026 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Docs, README, CHANGELOG, governance files no-issue Chore or dependency PR that does not need an issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant