Files
ruvnet--RuView/.github/workflows/ruview-swarm-ci.yml
T
rUv df617145d6 feat(ADR-262 P3): live /api/field + /ws/field — RuView sensing speaks RuField (fail-closed egress) (#1071)
* feat(ADR-262 P3): live RuField surface — RuView sensing speaks RuField on /api/field + /ws/field

Wire the P1 `wifi-densepose-rufield` bridge into the live
`wifi-densepose-sensing-server` so the governed sensing cycle emits real
signed RuField `FieldEvent`s on two additive endpoints.

- Cargo: add the `wifi-densepose-rufield` path dep (the single coupling
  point, ADR-262 §5.4 — no new RuView-internal coupling).
- New `src/rufield_surface.rs` (kept out of the 8k-line main.rs):
  `FieldSurface` holds a dedicated ed25519 `Signer` + a bounded ring of
  recent events + the `/ws/field` broadcast topic; `GET /api/field` and
  `GET /ws/field` handlers; a standalone `router()` for isolated testing.
- Signer (defers the P2 key decision, ADR-262 §8 Q1): a STANDALONE
  dev/sensing key from `WDP_RUFIELD_SIGNING_SEED`, else a deterministic
  dev default with a logged WARN. Reusing the `cog-ha-matter` Ed25519
  key is the deferred P2 call — P3 does not pre-empt it.
- Tap: at the ESP32 governed-trust cycle (`main.rs` ~5886 observe_cycle
  / ~5938 SensingUpdate build), `emit_rufield_event` joins the cycle's
  features/classification/signal_field with the engine's
  effective_class/demoted trust state into a `SensingSnapshot` and
  surfaces it via the bridge. Existing endpoints (`/ws/sensing` etc.)
  are unchanged — purely additive.
- Privacy egress: `network_egress_allowed` is fail-closed for an
  unattended live surface — only P1/P2 leave the box; P0 raw and
  P3/P4/P5 (identity/biometric/aggregate) are held edge-local. A
  `Derived` cycle maps to P4/P5 and never surfaces.
- No-phantom: `emit` drops no-presence cycles (no fabricated events).

Gates (tests/rufield_surface_test.rs, tower::oneshot, 4/0): well-formed
signed event (WifiCsi, P2 not P1, is_fusable, real timestamp); empty
cycle → no phantom; Derived trust never surfaces; mixed stream surfaces
only egress-safe events.

Honesty (ADR-262 §0/§6): real plumbing on a live endpoint, NOT accuracy.
Single-link CSI with its existing caveats (no validated room-coordinate
accuracy); dedicated dev signing key pending the P2 ownership decision;
no accuracy claim.

Co-Authored-By: claude-flow <ruv@ruv.net>

* docs(ADR-262 P3): mark P1+P3 implemented; document /api/field + /ws/field; CHANGELOG

- ADR-262 Status → "P1 + P3 implemented"; add a P3 implementation-status
  block (tap site, endpoints, dedicated dev signer deferring the §8 Q1
  key decision, fail-closed egress, gates). Keep the honesty framing:
  real plumbing on a live endpoint, not accuracy.
- CHANGELOG [Unreleased]: add the ADR-262 P3 entry.
- user-guide: add `/api/field` to the REST table + a "RuField surface
  (ADR-262 P3)" section covering `/api/field` + `/ws/field`, the
  fail-closed P1/P2-only egress, the WDP_RUFIELD_SIGNING_SEED dev key,
  and the no-accuracy honesty note.

Co-Authored-By: claude-flow <ruv@ruv.net>

* ci: checkout submodules everywhere + Dockerfile copies vendor/rufield

Making wifi-densepose-rufield (ADR-262 bridge) a v2 workspace member means
EVERY cargo-on-workspace context must have the vendor/rufield submodule
present (cargo loads all member manifests). P1 only fixed the rust-tests
job; this adds `submodules: recursive` to all workflow checkouts that run
cargo (mqtt-integration was failing on the missing submodule manifest), and
makes Dockerfile.rust COPY vendor/rufield/ to /vendor/rufield (matches the
bridge's ../../../vendor/rufield path-dep under the collapsed Docker layout).
update-submodules.yml left alone (it manages submodules itself).

Co-Authored-By: claude-flow <ruv@ruv.net>

---------

Co-authored-by: ruv <ruvnet@gmail.com>
2026-06-14 13:55:41 -04:00

158 lines
6.6 KiB
YAML

name: ruview-swarm CI guard
# Dedicated guard for the ADR-148 drone swarm crate (`v2/crates/ruview-swarm`).
# The main ci.yml runs `cargo test --workspace --no-default-features`, which
# only exercises ruview-swarm's DEFAULT feature set. This guard additionally:
# - tests every feature combination (train / ruflo+itar / full)
# - fails on ANY clippy warning in the crate's own code (--no-deps)
# - asserts the ITAR + publish guards stay in place (USML Cat VIII(h)(12))
# - builds the GPU training binary under the `train` feature
#
# Path-scoped so it only runs when the crate or this workflow changes.
on:
push:
branches: [ main, 'feat/*' ]
paths:
- 'v2/crates/ruview-swarm/**'
- '.github/workflows/ruview-swarm-ci.yml'
pull_request:
paths:
- 'v2/crates/ruview-swarm/**'
- '.github/workflows/ruview-swarm-ci.yml'
workflow_dispatch:
env:
CARGO_TERM_COLOR: always
jobs:
# ── Feature-matrix tests ─────────────────────────────────────────────────
tests:
name: tests (${{ matrix.features.label }})
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
features:
- { label: 'default', flags: '--no-default-features' }
- { label: 'train', flags: '--features train' }
- { label: 'ruflo+itar', flags: '--features ruflo,itar-unrestricted' }
- { label: 'full+train', flags: '--features full,train' }
steps:
- uses: actions/checkout@v4
with:
submodules: recursive
- uses: dtolnay/rust-toolchain@stable
- name: Cache cargo
uses: actions/cache@v4
with:
path: |
~/.cargo/registry
~/.cargo/git
v2/target
key: ${{ runner.os }}-ruview-swarm-${{ hashFiles('v2/Cargo.lock') }}
restore-keys: ${{ runner.os }}-ruview-swarm-
- name: cargo test -p ruview-swarm ${{ matrix.features.flags }}
working-directory: v2
run: cargo test -p ruview-swarm ${{ matrix.features.flags }} --lib
# ── Clippy: zero warnings in the crate's own code ────────────────────────
clippy:
name: clippy (-D warnings, --no-deps)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
submodules: recursive
# v2/rust-toolchain.toml pins channel "1.89" with profile "minimal" (no
# clippy). dtolnay@stable installs clippy on the floating "stable"
# toolchain, but the override makes cargo use the separate "1.89"
# toolchain — so `cargo clippy` errors "cargo-clippy is not installed for
# 1.89". Install clippy on the pinned toolchain that cargo actually uses.
- uses: dtolnay/rust-toolchain@stable
with:
toolchain: "1.89"
components: clippy
- name: Cache cargo
uses: actions/cache@v4
with:
path: |
~/.cargo/registry
~/.cargo/git
v2/target
key: ${{ runner.os }}-ruview-swarm-clippy-${{ hashFiles('v2/Cargo.lock') }}
restore-keys: ${{ runner.os }}-ruview-swarm-clippy-
# --no-deps confines linting to ruview-swarm's own source, so pre-existing
# warnings in dependency crates don't gate this PR.
- name: clippy (default)
working-directory: v2
run: cargo clippy -p ruview-swarm --no-default-features --no-deps -- -D warnings
- name: clippy (full,train)
working-directory: v2
run: cargo clippy -p ruview-swarm --features full,train --no-deps -- -D warnings
# ── Build the GPU training binary (train feature) ────────────────────────
train-bin:
name: build train_marl bin
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
submodules: recursive
- uses: dtolnay/rust-toolchain@stable
- name: Cache cargo
uses: actions/cache@v4
with:
path: |
~/.cargo/registry
~/.cargo/git
v2/target
key: ${{ runner.os }}-ruview-swarm-bin-${{ hashFiles('v2/Cargo.lock') }}
restore-keys: ${{ runner.os }}-ruview-swarm-bin-
- name: cargo build --bin train_marl --features train
working-directory: v2
run: cargo build -p ruview-swarm --features train --bin train_marl
- name: train_marl is excluded from the default build
working-directory: v2
run: |
# The training binary requires the `train` feature; a default `--bins`
# build must NOT produce it (keeps default/CI builds light + Candle-free).
# Remove any prior artifact first so this checks what the DEFAULT build
# produces, not a leftover from the train-feature build above.
rm -f target/debug/train_marl
cargo build -p ruview-swarm --no-default-features --bins
if [ -f target/debug/train_marl ]; then
echo "ERROR: train_marl built without the 'train' feature" >&2
exit 1
fi
echo "OK: train_marl correctly gated behind the 'train' feature"
# ── ITAR + publish guards ────────────────────────────────────────────────
export-control-guard:
name: ITAR / publish guard
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
submodules: recursive
- name: publish = false is present (no accidental crates.io publish)
run: |
CARGO=v2/crates/ruview-swarm/Cargo.toml
if ! grep -qE '^\s*publish\s*=\s*false' "$CARGO"; then
echo "ERROR: ruview-swarm Cargo.toml must keep 'publish = false' until" >&2
echo " PR merge + dependency publish + ITAR export sign-off." >&2
exit 1
fi
echo "OK: publish = false present"
- name: default feature set does NOT enable itar-unrestricted
run: |
CARGO=v2/crates/ruview-swarm/Cargo.toml
# USML Cat VIII(h)(12): swarming coordination must be opt-in, never default.
DEFAULT_LINE=$(grep -E '^\s*default\s*=' "$CARGO" || true)
echo "default = $DEFAULT_LINE"
if echo "$DEFAULT_LINE" | grep -q 'itar-unrestricted'; then
echo "ERROR: 'itar-unrestricted' must NOT be in the default feature set" >&2
exit 1
fi
echo "OK: ITAR-gated coordination features are opt-in, not default"