RuView Cognitum Spaces release checkpoint

This release checkpoints RuView's production Cognitum Spaces activation, read projection, tenant-scoped spatial memory, and governed-action boundaries.

Included

• Authorization Code + S256 PKCE activation through wifi-densepose login --spaces using sensing:read spaces:read.
• Strict reads for sites, buildings, floors, spaces, zones, anonymous entities, semantic events, and alerts.
• OAuth-only contributor CLI/MCP integration through @ruvnet/ruview; MCP requires an explicit credential-use grant and accepts no token, API key, arbitrary origin, or credential path as tool input.
• Tenant/workspace-scoped spatial memory with provenance and freshness preservation.
• Typed governed-action intents, policy decisions, and witness receipts; observing or recommending cannot become consequential execution without separate approval.
• ADR-325, ADR-326, and ADR-327 plus packaged Cognitum guidance.

Published artifact

@ruvnet/ruview@0.5.1 is published on npm with provenance. Its release workflow reinstalled, tested, packed, claim-checked, and smoke-tested the exact tarball before publication:

https://github.com/ruvnet/RuView/actions/runs/32289873933

Validation

• Release integration: #1650
• Packaged guidance: #1651
• Final OAuth/release evidence: #1653
• Main CI and automatic release authority: https://github.com/ruvnet/RuView/actions/runs/32289794565
• Live RuView S256 PKCE access successfully read the production Cognitum sites collection.
• Published-package doctor and source-cited Cognitum guidance passed.

Boundaries

Raw RF/CSI, CIR, tensors, recordings, pose frames, vital waveforms, and identity observations remain local. spaces:read grants no write, pairing, command, policy approval, spending, or actuator authority. Shared remote RuVector memory, MQTT federation, real-hardware accuracy, and long-duration operational claims remain separate rollouts/evidence gates.

Architecture: ADR-325, ADR-326, and ADR-327.