Repository navigation
feat(companion): retain versioned RoomPlan objects and room identity - #2555
proffesor-for-testing wants to merge 6 commits into
Conversation
|
November17 held-stack follow-up at Parent/security reconciliation: #2513 (comment) . Upstream #2552 superseded closed #2556; this branch already targets held #2513 directly. The parent's standalone old head and its current merge candidate have different advisory results; the packet records exact SHAs. Remaining landing/integration gate: maintainer decision on #2513, then retarget/requalify this v2 producer against the actual landed main and build/qualify the corresponding helper/consumer combination. Do not advance the held parent merely by merging this child into it to satisfy a status label. Current draft/head checks are not evidence of a newly installed helper or physical device acceptance. No parent/main merge or installed-helper change performed here. |
|
Fresh-database correction to today's lockfile audit snapshot: advisory DB commit 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 For #2513 this refresh checked merge candidate No source edits, advisory suppressions, runtime exploitability conclusion, merge or release performed. Keep review/landing qualification separate from historical green CI. |
|
NO BLOCK in the reviewed Nov20 reconciliation delta at Normal current-parent reconciliation; only lock conflict resolved to exact parent canonical graph. Spatial source/fixture unchanged, shared fixtureSHA d18f7bfa408b78f45dca4b3a751bc9f7139e29cc9f0cde97603bc5618bd0bd26. Contract remains bounded objects/immutable histories plus exact active room binding, not catalogue/lineage/legacy association. Full same-head push CI running; physical cross-device acceptance remains unverified. Earlier terminal CI receipts remain historical and are not relabeled as passes on this new head. Same-head duplicate push QEMU/bench and unfinished supersededb109 runs were cancelled only where an active replacement exists; completed failure evidence is retained. No main merge, installed-helper/app replacement, release or sensor operation. Maintainer review/exact-head merge authority remains separate. |
Preserve phone RoomPlan objects in explicit saved-scan transfer without treating historical geometry as live sensing. Current head
d96f9e132b5e56cb41fbf0b410923439e90e9086; base held #2513 atbb2b088b. Paired mobile PRs #305/#306 remain held; helper198 is unchanged.V2 artifacts add bounded objects and stable published-room ID. The existing granted ticket advertises support; upload and acceptance retain nonce/expiry/device grant/digest checks and require the current installation, room ID, revision and binding digest. V1 remains supported. Separate v2 history retains original v1 bytes for rollback, reconciles later v1 receipts by digest and preserves private owner/installation checks and global32-receipt bound. Original payload bytes stay immutable. No registration, calibration/model activation or live object detection.
Nov20 reconciliation imports the current held parent, including upstream ZIP9/libz/Quinn fixes, Wasmtime36.0.21 and runner fixes. The only conflict was a stale Quinn UDP lock edge; the complete resolved lockfile is byte-identical to the parent, rather than mixing old socket2/Windows edges. The spatial implementation and shared fixture are unchanged fromcd8139cc. Locked metadata, workflow/diff/secret checks pass. Parent native audit0.22.2 passes the identical lock on fresh corrected RustSecDB074ea9a7; full current-head hosted qualification is pending on this branch's push workflow, not inferred from the stacked PR's limited branch-filter checks.
Historical11 companion spatial tests passed, including strict schema/wrong room, nonce/grant/router refusals, review/restart/revocation, storage faults and rollback writes. Shared synthetic fixture SHA256d18f7bfa408b78f45dca4b3a751bc9f7139e29cc9f0cde97603bc5618bd0bd26 remains unchanged; earlier hosted results apply only to their recorded heads.
Contract limit: this is object transport/history, not full room catalogue synchronization, revision lineage or legacy-v1 association. Those remain mobile#276/#277 producer/consumer work. Future association must be explicit and preserve original bytes; never infer room ownership from name or dimensions. Mobile session notified of this seam. Physical cross-device/room acceptance, installed-helper migration and release are NOT verified. Draft; no main merge or installation.