Skip to content

Reconcile managed room-learner stack with current RuView main - #2513

Open
proffesor-for-testing wants to merge 159 commits into
mainfrom
integration/ruv-main-reconcile-20261110
Open

proffesor-for-testing wants to merge 159 commits into
mainfrom
integration/ruv-main-reconcile-20261110

Conversation

@proffesor-for-testing

@proffesor-for-testing proffesor-for-testing commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Reconcile the managed pairing, companion, room-learner, recovery and temporal stack with current RuView main while retaining the original PR ancestry. Current head: 38a10584d33ccb18be98d62bd0e3567ad54d9766, incorporating main 13b47883a73d5070f35a3f04aec2ffa778b47e29 (#2574). No main merge or release is performed.

Resulting behavior

  • Preserve managed ruview-unified, companion/room publication, configured-topology provenance, selected-model withholding, recovery and prepared training alongside upstream FANN, RSSI, witness and forecasting work.
  • Preserve upstream's actual registry ZIP 9.0.5 implementation through the private Candle API adapter and libz-sys 1.1.33. Remove the old ZIP 7 patch selector from the live dependency graph. The security workflow now tests the active adapter, while retained historical ZIP 7 source remains excluded from workspace membership. Wasmtime/zstd and SQLx SQLite repairs and audit policy remain unchanged.
  • Repair CI bootstrap with digest-pinned non-root Mosquitto and SDK QEMU/runtime, hosted Clang 18 and scoped signed Canonical HTTPS APT sources. Preserve broker integration, fuzz budgets, workspace, temporal, socket/security, CIR, FANN, auth and bench gates.
  • Reduce AETHER attention/GNN temporary allocations without changing scalar accumulation order, APIs, parameter layout, architecture, gradients, epochs or production evaluation budgets. Frozen scalar oracles and perturbation/golden tests protect equivalence. Correct synthetic test preparation/input ordering rather than relaxing production guards.

Current reconciliation validation — local, 2026-11-18

macOS arm64, Rust 1.97.1, exact committed dependency sources; no sensors or installed app/helper changes:

  • Locked metadata and locked server binary build pass.
  • All 608 server-bin tests pass, including the five configured-topology tests and upstream RSSI tests.
  • Real companion socket contract: 26 checks pass, including auth, pinned TLS, restart refresh, revocation and already-open WebSocket closure, using isolated temporary state and ephemeral loopback ports.
  • Real Candle archive round-trip/error handling: two tests pass. Active ZIP adapter security guards: four tests pass.
  • Upstream source-label/live-data UI regressions: 10 tests pass; temporal CI classification: 45 tests pass. Diff and secret checks pass.
  • CI-pinned cargo-audit 0.22.2: zero unresolved registry advisories under the unchanged policy, against RustSec database 233155b4025b854c68a4b199c0e32d7fd53291a2. Older local 0.22.1 reports six path-package ZIP matches. The newer tool excludes local path packages from registry matching: this does not prove those sources clean; the actual registry ZIP 9 backend, provenance and executed adapter guards are separate evidence.

Current-head hosted qualification is complete: all 14 workflows SUCCESS; 66 checks SUCCESS and nine conditional SKIPPED. Full CI44265854972, security44265854909, MQTT44265854655, QEMU/fuzz44265854985, bench44265854887 all pass. The total includes duplicate firmware/QEMU/Python event runs, not 14 unique test suites.

The actual full-CI checkout is GitHub merge candidate ed41919348cb5f5395966a1cbe740e91bb293e64 with parents main13b4788/PR38a10584. Its source tree c96656ad32006a73542bc0e4a91b9d1769bffb9b exactly matches pushed38a10584. The downloaded temporal artifact records clean Linux/Rust1.89, 37 selected Release cases passed, zero selected failures/ignores, and Release binary SHA256 04325ffd10db7b2271bab8b2e03547e13a50719ee07ee79c59c5311a5a1febe9. Full workspace, socket/archive guards, FANN, CIR/calibration proofs and all-feature authentication also pass in the terminal full-CI job.

Maintainer review and separate exact-head merge authorization remain open. Prior4f70 receipts remain historical; skipped jobs do not become executed proof.

Review, dependencies and limits

Complete the prepared local integration of upstream a1ca023 into the companion candidate. Runtime helper provenance remains pinned to the previously verified clean source.
Move the companion pairing design to ADR-419 so upstream ADR-383 remains the HTTP request-target validation decision.
Recheck approved-device capacity under the approval lock before persistence, retaining pending requests when full. Build the exact Host allowlist entry from the prepared identity authority used by the QR, including generated and reloaded identities.

Regressions reproduced the old failures and now pass. Verified actual workspace binary check, nine companion tests and the real binary authority test, plus 28 isolated module tests and independent fix-delta review. No Host wildcard or validation bypass.
Resolve Tokio 1.51.6 with its compatible Mio, socket2 and macro dependencies. Preserve the scoped companion stack and existing audit policy; no upstream vendor or framework adoption. Existing LRU unsoundness and yanked-package warnings remain separately recorded.
Preserve main archive/cache compatibility and companion socket gates. Retain the audited main dependency graph while restoring companion/MAT privacy changes.
@proffesor-for-testing
proffesor-for-testing marked this pull request as ready for review November 10, 2026 14:48
Retain unified and FANN dependencies, reviewed ZIP backports and current SQLite runtime guard. Use byte-verified Wasmtime cache metadata from main without its unconsumed original manifest.
@proffesor-for-testing proffesor-for-testing changed the title Reconcile managed app stack with rUv sensor-fusion main for local baseline Reconcile managed room-learner stack with current RuView main Nov 11, 2026
@proffesor-for-testing

Copy link
Copy Markdown
Collaborator Author

Conditional authored-PR cleanup analysis refreshed against published head b8f731b854cf1760262082992c75b4e9e51d23c9. Authenticated author proffesor-for-testing; all five REST pages checked:48 authored open PRs including2513, eight drafts. Of the47 other PRs:

35 exact heads included: #2501, #2500, #2495, #2487, #2481, #2479, #2475, #2474, #2471, #2470, #2467, #2465, #2461, #2459, #2452, #2450, #2449, #2447, #2446, #2444, #2439, #2438, #2434, #2427, #2424, #2423, #2417, #2407, #2402, #2401, #2386, #2379, #2374, #2350, #2249.

Two superseded, not ancestor/patch-equivalent claims: #1760 is covered by stronger provisioning already present (the same provisioning source exercised by62 mocked controls is retained); #2342's TLS dependency intent is matched/exceeded by the preserved current-main Python lock (quinn-proto0.11.19, rustls0.23.46, rustls-webpki0.103.16, webpki-roots1.0.11). This is source-intent equivalence, not a fresh published-wheel security qualification.

Keep these10: #2499 identity-failure authority repair; #2445 dual native/UART firmware transport; #2498 guarded paired node labels; #2497/#2453/#2458 reference/comparison alternatives; #2496 offline pose-training split repair; #2395/#2400 firmware signing/release; #1145 Docker runtime work. Each still has unique scoped changes; do not wholesale merge them or close as delivered by2513.

Closure conditions: approval alone is not closure. Wait for the approved2513 candidate to land, then re-read every original head/state. A normal merge permits ancestry proof; a squash requires candidate-tree/content parity or explicit reconciliation of intervening changes. The candidate tree here is 866c8605d8b7112d1726b75c480ed2ee75f7ed02. GitHub may not close stacked PRs automatically. Any changed original head must be reclassified. No PR closures/main merge performed by this analysis.

Executed by Codex with a separate read-only inventory reviewer. Repository/API base SHA snapshots lagged live target refs in14 rows; live target refs were verified separately rather than treating those snapshots as today's branches.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator Author

CI follow-up at candidate dc0661f47b9ff5b537e9d13da7cec9e91dbb0aad:

  • The prior MQTT cancellation was the 20-minute job limit: unrelated long learner library tests prevented the real broker step from starting. The workflow now runs its MQTT namespace (99 passing tests and one existing ignore locally) before the unchanged real Mosquitto integration step. Full workspace/temporal CI remains unchanged. YAML parsing and broker-step preservation pass.
  • The first new MQTT run failed earlier, during apt installation, with Temporary failure resolving 'azure.archive.ubuntu.com'; no unit/broker test result was produced. Retried failed run 43039199137 once.
  • Fuzz job 130586129291 failed on the same apt/DNS error before fuzz compilation. Retried failed jobs in run 43039199315 after its other jobs completed.
  • Rust Workspace Tests is still running. This is not a green/no-block CI verdict, and the hosted broker result is pending. No main merge, release or original-PR closure has occurred; review/merge authorization must name this current head.

@proffesor-for-testing proffesor-for-testing left a comment •

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

REMAND for final merge disposition: the qualified current-main candidate is green, while rUv review and the known standalone timing risk still need a decision. This COMMENT is not formal human approval.

Frozen tuple, refreshed November 12 at 16:00 UTC:

  • PR head: 68cd04927ac503ae68313edc249c6ea8627319c2.
  • Main: 094e1400719ded1283c67d23b9c737f6738a3244.
  • GitHub merge ref: 9b8f70754d036a77900d936b93795616d2242dd5; tree 2b732f00e133526b310d634a792a219aaba4d86d.
  • The PR remains CLEAN/MERGEABLE, with rUv requested and no submitted owner review.

EXECUTED receipts close all five original CI areas:

  • MQTT on head68: 43183390004 passed feature units and actual pinned Mosquitto integration; the owned broker stopped successfully.
  • QEMU and fuzz on the merge candidate: 43188188492, all 11 jobs passed, including actual fuzz testing.
  • Rust workspace and downstream checks: 43188188760, SUCCESS. All 37 mandatory Release cases passed, zero selected failures or ignores. Default-48 C4C completed 48 epochs, 395 parameters and 38,373 objective evaluations under the unchanged 60,000 ms / 100,000 caps. Full lifecycle 487.68 s is not fit time.
  • Bench: 43188188802, SUCCESS. Head68 also separately passed 43183609967.
  • Firmware, security, forecast Rust and Python workflows also remain SUCCESS on the merge candidate.

Retained counterevidence: standalone head68 43183605678 hit the unchanged 240-second operator guard at 76/80 windows before C4C. Child938 repeated it. These failures are not erased or claimed causally fixed.

Further probes did not reproduce the failure: child diagnostic full CI8370 43232492184 passed Debug plus all 38 Release cases and downstream sockets/FANN/CIR/witness checks; direct Release0e490242 passed all 38; failure-only comparison31b15c55 passed all nine C4 cases with normal-path logging removed. Controlled segment76 and partial-row77 storage holds both resumed to 80 durable windows and completed fit/cold/evaluate. These are additional probes, not substitutes for the parent's separate 37-case receipt or hardware qualification.

Child #2527 now has test/CI-only live evidence and lazy watchdog state at56d43b5a, with current-head gates still running. Parent head68 is unchanged. No speculative capture repair or timeout/budget relaxation was introduced. Keep the intermittent standalone timing risk visible for rUv's decision; refresh qualification if either parent/main ref changes. No main merge, release or helper installation was performed by this lane.

@proffesor-for-testing
proffesor-for-testing marked this pull request as draft November 12, 2026 18:25

@proffesor-for-testing proffesor-for-testing left a comment •

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NO BLOCK for the reviewed code and CI at head 4f70c5eafe28a17395f1588cc15f5e64ba932d7d against main 094e1400719ded1283c67d23b9c737f6738a3244. This COMMENT is not formal human approval or merge authorization.

The current GitHub merge candidate 994e5896053579ae8e35b36f2bc8818160a37aad, tree af593d44129b957c917c14d2c1a6ad397c1dadc5, matches those exact parents. All 11 current-head workflows are terminal SUCCESS, including full CI43279683707, MQTT43279683661, QEMU/fuzz43279683678, security43279683676 and bench43279683922. Rust workspace, sockets, patched archive/cache compatibility, FANN, CIR and both witness guards passed.

The retained Release receipt is clean, has 1096 registered tests and 37 required passes with zero selected failures/ignores. C4: nine cases PASS526.41s. C4C: PASS629.70s for its full lifecycle; this is not fit duration. Test binary SHA256 fb559047d32f72eb4e1b4d859d22177954ab74ab63c3b39efd69a75407d9849b.

Root cause and repair: diagnostic211 exposed 22 final-Check preparation/restart gaps, no deferred ACK and no clock lead. The synthetic driver generated input before segment preparation completed; host latency repeatedly consumed its first-window buffer. The fixture now waits for verified preparation before generating synthetic packets, asserts no preparation credited as observation, and includes an actual five-second publication hold. Local full-journey regression also passed205.18s. All80 windows/phases/fit/cold/evaluation assertions, original240s phase wall guard, production clock/backpressure rules and default-48 training/evaluation caps are retained. Real-paced/backpressure tests are unchanged.

Opposite-assumption checks: no rows/flags are manually promoted, the wait shares the original phase-start Instant, bad/missing ACKs cannot produce success, and PR verification cannot invoke the legacy publisher/notifier. Publication/version jobs were skipped for verification, not qualified. No production capture repair, physical sensing/throughput qualification or repair of the separate historical Empty Check is claimed.

Current source/CI follow-up is complete. Ready for rUv's owner review and separate exact-head merge decision. Refresh qualification if head/main changes. No main merge, release or helper198 replacement was performed by this lane.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator Author

Dependency-security follow-up for the held stack: fresh November14 audit on descendant #2555 at783e69d4 found RUSTSEC-2026-0523/0524 (quinn-proto0.11.18) and RUSTSEC-2026-0538 (quinn-udp0.5.14), inherited from this parent lockfile. Prior green checks at4f70c5e do not include the new advisory result.

Separate draft #2556 at ef9dd1b patches only the two lock entries and required UDP dependency edges. Local locked compile checks and the unchanged repository-policy audit pass. #2555 now stacks on that repair and its current combined-head Rust Dependency Audit passes; fresh standalone security run43602259821 also passed its Rust audit. Other hosted checks remain in progress.

This parent and installed helper are unchanged. The merge hold remains; account for #2556 in the stack review before treating dependency security as current. No new audit ignores or approval/merge claim.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator Author

November17 reconciliation of the held security/review state (no branch edits or merge):

Reproduce from each exact revision with working-directory v2: cargo audit --json. The merge-candidate result does not make the old head's advisory scan green and does not prove the whole new merge tree compiles. Remaining gate: maintainer review/landing decision and appropriate exact-merge qualification against the then-current main; refresh if that candidate changes. Original parent and installed helper remain untouched. No approval or merge authorization claimed.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator Author

Fresh-database correction to today's lockfile audit snapshot: advisory DB commit 233155b4025b854c68a4b199c0e32d7fd53291a2 now reports7 unignored package/advisory findings in the checked lockfile. The earlier zero-unignored result was a snapshot before these entries and must not be treated as current audit cleanliness.

New findings: libz-sys1.1.31 / RUSTSEC-2026-0544; zip0.6.6 /0545 and0548; zip7.2.0 /0545,0546,0547,0548. These are version-based workspace findings; applicability of the existing vendored backports and actual caller paths still needs assessment. No new ignore is proposed. The checked .cargo/audit.toml remains byte-identical (31 existing ignores, SHA256 1c9ac5c8bfcead9f35ca1b53c840a3e9c3da1ba7036acc15f6977ecc0edb1b70).

For #2513 this refresh checked merge candidate e3a029f4acf0e96b089e581363323b30c63deaf8 (base dea1cc23e1efb3d409fb00a99bf68fed9955a24b); for #2555 it checked head cd8139cc5dd0ec5469c4a6c478f83180750cba2b. Quinn0.11.19/UDP0.5.16 in those revisions resolves the earlier Quinn entries, but not the newly reported zip/libz entries. Repeat from v2 with cargo audit --json, preserving the current policy and advisory DB identity.

No source edits, advisory suppressions, runtime exploitability conclusion, merge or release performed. Keep review/landing qualification separate from historical green CI.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator Author

NO BLOCK in the reviewed current-main reconciliation delta at 38a10584d33ccb18be98d62bd0e3567ad54d9766. Maintainer stack review and a separate exact-head merge decision remain required. No main merge/release or installed helper update occurred.

Fresh qualification is terminal: 14 workflows SUCCESS, 66 checks SUCCESS, nine conditional SKIPPED. Includes full CI44265854972, security44265854909, MQTT44265854655, QEMU/fuzz44265854985, bench44265854887. Duplicate firmware/QEMU/Python event runs are counted as separate workflows, not independent test coverage.

EXECUTED source binding: full CI's merge candidate ed41919348cb5f5395966a1cbe740e91bb293e64 has parents current main13b4788 and PR38a10584; its tree c96656ad32006a73542bc0e4a91b9d1769bffb9b equals pushed38a10584. Downloaded temporal artifact14413449119 records clean Linux/Rust1.89,1096 registered tests and 37 selected Release cases passed, zero selected failures/ignores. The three globally ignored registrations are recorded separately. Release binary SHA256 04325ffd10db7b2271bab8b2e03547e13a50719ee07ee79c59c5311a5a1febe9.

Review scope: the three conflict resolutions preserve managed room/companion plus upstream RSSI modules, registry ZIP9 through its Candle adapter and libz1.1.33. The old active ZIP7 selector is removed, the security job executes the active adapter guards, and audit policy is unchanged. Local608 bin tests/26 real socket checks and hosted workspace/Release/FANN/CIR/calibration/auth, audit, QEMU/fuzz/MQTT and bench checks all pass. No timing budget, coverage floor, security gate or production fit guard was relaxed.

Limits remain explicit: local path packages require independent provenance/caller/guard evidence despite cargo-audit0.22.2's zero unresolved registry findings. Conditional skips are not executed results. This is not container publication, physical sensing, installed-helper198, dependent-PR or customer acceptance qualification. Reverify if main/head changes; do not close original PRs before actual landing and ancestry/content reconciliation.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants