v1.0.16-dev.1

Respire CLI 1.0.16-dev.1

Development release for testing. The npm latest channel remains on the stable version.

Changes since v1.0.15.

Features

No separately classified changes.

Fixes

No separately classified changes.

Other changes

• Fix same-identity release guard fixtures and Python diagnostics [manual-release] — The new server/account isolation correctly keeps an anonymous local library separate from a cloud identity. The release sweep used keygen --force to create a mismatched key, but keygen also removes user/server identity, so that fixture no longer exercised the same-account overwrite guard. Bind only the disposable fixture metadata back to its exact cloud user/server, retain its separate local data key in the process environment for readback, and restore the inherited environment in finally. Keep the login-refusal, unchanged-session and readable-source assertions. (c0e8dc30)
• Fix same-identity key mismatch release fixtures and unsafe timed stack dumps — Bind the disposable keygen library to the intended cloud identity before verifying overwrite refusal, and keep its generated local credential only in a restored process environment for readback. Verify the same-identity guard in the existing real CLI scenario. Retain all acceptance deadlines and fault diagnostics while removing the asynchronous Python stack-dump timer that raced active frames. (44e9b89d)
• Fix full logout recovery and native upgrade model fixture [manual-release] — The first gated DEV publication exposed two failures. Stable 1.0.15 now requires a real CPU ORT model that the historical upgrade fixture did not copy. Separately, full logout removes the session, so server-aware directory selection could choose a fresh library instead of reconnecting the retained encrypted records. (f606b642)
• Recover retained sessionless libraries using the verified cloud data key — Full logout removes account identity while preserving encrypted records. Probe only sessionless candidate libraries with the authorized key, then use the prepared destination when deciding whether a transfer is needed. Extend the existing runtime smoke to verify original-directory recovery and immediate readback. (dd0d82e1)
• Include the prepared CPU model in published upgrade fixtures — The newly published 1.0.15 upgrade source loads model_quantized.cpu-v1.ort, but the historical cache only copied ONNX files. Copy the already installed and probed real CPU container alongside ONNX/FP16 so every published stable remains in the mandatory upgrade sweep. (1e9baa85)
• Fix server account migration and idempotent imports [manual-release] — Changing from a self-hosted server to the public service could reuse an account directory belonging to another server or differently cased username. Login now selects profiles by server and exact account identity, and `login --migrate-local` synchronizes the target before copying the selected snapshot in memory. This lets cloud-only records participate in deduplication. Failed target preflight restores the source selection; the source library is retained. The result includes import counts and the attempted final sync outcome; TUI login offers the same transfer. (7a9c6163)
• Synchronize cloud records before deduplicating a local server transfer — Refresh and verify the target library before copying so records present only in the cloud participate in exact-body deduplication. Abort and restore the source selection when target preflight fails, then preserve copied records with an explicit warning if the later sync fails. (eab7dc63)
• Preserve read-only and disabled memory modes during local transfer — Apply the existing write gate before snapshot migration and inside the shared import entry so host login cannot bypass account/device memory policy. Extend the existing workspace-mode assertions; all 29 service tests pass. (2f420206)
• Cover duplicate IDs and interrupted sync outcomes in migration checks — Skip repeated IDs only when their bodies match, collapse mapped association duplicates, and strengthen case-folded profile checks. Make existing migration fixtures keep their server alive during the intentional sync outage and assert the documented warning exit code. (416e3ef0)
• Exercise server transfer through the shipped CLI and bound ownership probes — Extend the existing runtime fixture to verify re-encryption into a different URK, source-session retention and idempotent retry. Bound the existing alternate-port socket probe so Windows refusal latency cannot exhaust the unchanged startup deadline. (371adf11)
• Use the original synthetic factor in server transfer regression — Keep the fixture source unlock independent of the target RSRS_SUPER so the regression proves transfer between different data keys. (057e4d5d)
• Fix server account migration and idempotent memory imports — Scope remote profiles by server and exact account identity, copy local snapshots through verified login, and report import and sync outcomes. Deduplicate JSON imports by exact body while remapping relationships atomically. Correct public npm upgrade hints and current-vault migration discovery. (1141413a)

Commits

Commit	Change
c0e8dc30	Fix same-identity release guard fixtures and Python diagnostics [manual-release]
44e9b89d	Fix same-identity key mismatch release fixtures and unsafe timed stack dumps
f606b642	Fix full logout recovery and native upgrade model fixture [manual-release]
dd0d82e1	Recover retained sessionless libraries using the verified cloud data key
1e9baa85	Include the prepared CPU model in published upgrade fixtures
7a9c6163	Fix server account migration and idempotent imports [manual-release]
eab7dc63	Synchronize cloud records before deduplicating a local server transfer
2f420206	Preserve read-only and disabled memory modes during local transfer
416e3ef0	Cover duplicate IDs and interrupted sync outcomes in migration checks
371adf11	Exercise server transfer through the shipped CLI and bound ownership probes
057e4d5d	Use the original synthetic factor in server transfer regression
1141413a	Fix server account migration and idempotent memory imports

Full comparison

Install

npm install -g rsrs-cli@1.0.16-dev.1 --registry=https://registry.npmjs.org
rsrs --version

Source and validation

• Source: c0e8dc303aabdbf9e4ecd0e959ab12e7a367ac9f.
• Publication requires the existing platform, CLI and development API acceptance gates.
• Release workflow.