Skip to content

test(sync): preserve current encrypted client envelope - #10

Merged
appergb merged 1 commit into
mainfrom
appergb/client-sync-compat
Oct 25, 2026
Merged

appergb merged 1 commit into
mainfrom
appergb/client-sync-compat

Conversation

@appergb

@appergb appergb commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

Summary

The client follow-up in f71ffd54 adds portable preference fields inside the existing encrypted preferences document. The server does not decrypt that document, so the SnapshotUpload envelope, protocol metadata, OpenAPI contract, and ciphertext limits remain unchanged.

This PR:

  • documents the opaque encrypted boundary in the client-integration, encryption-protocol, and HTTP API contracts;
  • adds a regression test using the shared current client envelope fixture and verifies exact store/download round-trip without filtering ciphertext;
  • records the beta-to-task, PR-only, CI-gate, scope, and English-comment contribution policy in AGENTS.md;
  • refreshes only Cargo.lock security versions so the required audit passes.

Validation

  • cargo fmt --check
  • cargo clippy --all-targets --locked -- -D warnings
  • cargo test --locked
  • cargo audit --deny warnings
  • .venv/bin/python scripts/interop_vectors.py
  • .venv/bin/python scripts/check_contract.py
  • .venv/bin/python -m unittest discover -s tests -p 'test_*.py'
  • cargo build --release --locked
  • .venv/bin/python scripts/smoke_local.py

The optional nginx check was not run successfully because nginx is not installed on this macOS host.

@appergb
appergb merged commit c40dadd into main Oct 25, 2026
4 checks passed
@appergb
appergb deleted the appergb/client-sync-compat branch October 25, 2026 16:15
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.

1 participant