API gate: downstream compile fixture and 100% coverage audit #12
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Objective
Prove that the complete mapped Rust API is present and callable before semantic test translation starts.
Deliverables
api/public-api.json, Rust mapping records, and exported Rust items.Validation
cargo check --workspace --all-targetsandcargo doc --workspace --no-depspass.Prerequisite
Stage 0 project setup is complete. Do not implement production behavior in this milestone.
Project constraints
Implemented in commit
c8a9539. Added a standalone downstream Rust workspace whose generated fixture names all 3,066 catalog types and calls or accesses all 30,789 mapped public members across all 13 assemblies. Added tools/check_api_coverage.py and API-COVERAGE.md to compare catalog IDs, type/member mapping rows, exported generated items, and fixture probes; the audit reports zero public exclusions, 142 explicitly cataloged external signature boundaries, two required support traits, all 80 deliberate delegate APM replacements compiled, and zero forbidden erased shim patterns. The fixture exposed and this commit fixed two real mapping defects: the static Logger.OnLogMessage event no longer has an instance receiver, and the catalog LSL Error type is exported as LslError instead of being hidden by the shared shim Error alias. Added Gitea CI gates for deterministic mapping/shim generation, coverage, formatting, workspace check, standalone fixture check, test compilation, Clippy, and docs. Verified with a fresh temporary Cargo target requiring no .NET or LibreMetaverse assemblies, cargo check --workspace --all-targets, cargo test --workspace --no-run, cargo clippy --workspace --all-targets --all-features -- -D warnings, cargo doc --workspace --no-deps, all generator/coverage checks, git diff --check, and 15 isolated compatibility regression tests. No production behavior was introduced; generated bodies still pass the standardized failure-only audit.