Implement native RLV state and permissions (#79)
Some checks failed
Native code generation / deterministic (push) Failing after 2m1s
Imaging and meshing gate / native (push) Successful in 5m22s
JPEG 2000 feature / linux (push) Successful in 2m45s
Native Rust workspace compile / compile (push) Failing after 6m12s
Skia feature / linux (push) Successful in 30m44s

This commit is contained in:
2026-08-10 23:55:11 +00:00
parent 468a0f0619
commit 362fa62059
12 changed files with 3429 additions and 347 deletions

View File

@@ -463,14 +463,17 @@ reports decode allocations and timing without replacing correctness gates. The
format, ownership, error, and tangent-output contracts are documented in the
[`MeshFoundry` guide](crates/libremetaverse-rendering-mesh-foundry/README.md).
The native RLV protocol layer parses bounded chat messages into typed clear,
action, restriction, and query directives without changing client state. It
The native RLV layer parses bounded chat messages into typed clear, action,
restriction, and query directives, then provides independent thread-safe
restriction, inventory-map, folder-lock, camera, blacklist, and permission
providers without network I/O. It
preserves source casing, folder paths, separators, numeric channels, UUIDs, and
attachment/wearable aliases while exposing canonical behavior names and
source-located typed errors. All 119 restriction names from the pinned
LibreMetaverse snapshot are covered, and deterministic malformed-input
mutations exercise the parser without an external fuzzing runtime. State,
camera, inventory, callback, and transport effects remain explicit consumers
of this pure layer. The grammar, normalization rules, limits, and ownership
boundary are documented in the
mutations exercise the parser without an external fuzzing runtime. Immutable
snapshots and post-lock update events make concurrent policy reads
deterministic; callback execution and transport effects remain explicit
consumers of the layer. The grammar, state precedence, normalization rules,
limits, and ownership boundary are documented in the
[`RLV protocol guide`](crates/libremetaverse-rlv/README.md).