[rennf93]

The registry that ecosystem, adapter_setup and wire_agent answer from still described the 4.2.0/3.1.0 train, pointed 12 repo= fields at rennf93/, and carried Go snippets that do not compile against the current module path. This re-syncs every version-bearing fact to what the registries and the release tags hold today.

Sources: PyPI, npm, crates.io, proxy.golang.org and Packagist latest versions, the newest semver tag of each of the 26 repos, and each repo's README, go.mod, composer.json, Cargo.toml or package.json at that tag.

1. Versions: engines 4.4.0 (Go 4.4.1), agents 3.2.4; Go adapters 1.5.0 and echo-guard 2.0.0; PHP adapters 1.6.0 (psr15-guard 1.6.1); Rust adapters 2.0.0; fastapi-guard 8.1.2, flaskapi-guard 4.4.0, djapi-guard 5.0.0, tornadoapi-guard 2.0.0. Install lines follow each README at its tag.
2. Repo URLs: every repo= now points at Guard-Core/. The Go module paths and Packagist names keep rennf93/, because that is what go.mod and composer.json still declare.
3. Snippets: the four Go snippets imported github.com/rennf93/guard-core-go/guardcore, missing the /v4 major path; the README at each tag has /v4/guardcore. echo-guard moved to the /v2 module on Echo v5 (echo/v5, *echolib.Context), and its notes say Echo v4 users stay on v1.5.0. The Python agent snippet is now the README quick-start block verbatim. Every other snippet already matched its README at the tag.
4. PHP install lines were composer require psr15-guard and similar, which is not a Packagist name; they are now composer require rennf93/<package>, as each README says.
5. Conformance: every port vendors the same corpus at conformance/guard-core-spec-4.1.0 (spec 4.1.0, 375 cases across 21 suites, generated from engine 4.3.2 at commit 37b6a132; read from each cases/index.json at the tags), so the block and each engine entry now say that. I dropped the "106/106" interop count and the per-port pass details I could not re-verify at these tags, and kept what the sources state: the redis_interop suite (14 cases), the interop harness described in guard-core's CHANGELOG, and the Rust "193 cases, zero xfail" line from its docs/configuration.md.
6. Status: the TypeScript engine, adapters and agent are published (npm has 4.4.0 and 3.2.4). Go and PHP stay tagged, since the pushed tag is the release there.
7. Notes that cited old facts: Go 1.26.0, guard-core-php ^4.4.0, slim-guard on psr15-guard ^1.6.0, guard-agent-php also requires ext-openssl and keeps its version in src/Version.php, axum-guard-rs depends on guard-core-engine directly as well as on tower-guard-rs, and the Rust engine gaps quoted from its docs/configuration.md at v4.4.0. The ecosystem tool docstring said spec-4.0.2; it now says spec-4.1.0.

Tests follow the new facts. They also assert the Go /v4/guardcore import and the PHP rennf93/ install line. Local run: uv run pytest 157 passed, ruff format --check, ruff check and mypy clean.

Not changed: the vendored _docs/ and the hand-written _knowledge/ corpus (a separate sync), the release version, and the CHANGELOG, since this is not a release.