1.6 KiB
1.6 KiB
Change: Device Fingerprint Consolidation and Hardening
What Changes
- Unify backend scope:
- Fingerprint read/write with synchronized updates to
storage.jsonandstate.vscdb - Account-level binding, revision history, and baseline restore
- Fingerprint apply orchestration during switch flows (local/cloud)
- Fingerprint read/write with synchronized updates to
- Unify management scope:
- Device fingerprint management dialog
- Generate-and-bind, capture-and-bind, restore revision, delete revision, restore baseline, and open storage folder
- Unify robustness scope:
- Two-phase apply (
prepare -> verify -> commit) - Deterministic rollback before commit on failure
- Failure reason classification, safe mode, degradation strategy, and diagnostics snapshots
- Versioned payload with boundary validation (lenient compatibility + strict failure for critical structure)
- Two-phase apply (
- Path scope: this stage focuses on the default runtime configuration path.
Non-Goals
- Do not promise any anti-detection, anti-ban, or risk-control bypass outcome.
- Do not introduce token/protobuf semantic changes unrelated to device fingerprinting.
- Do not perform ORM or large database refactors in this change.
Impact
- Affected specs:
device-fingerprint-hardening - Affected code:
src/ipc/device/handler.tssrc/ipc/account/handler.tssrc/ipc/cloud/handler.tssrc/ipc/switchFlow.tssrc/ipc/switchMetrics.tssrc/ipc/database/cloudHandler.tssrc/components/DeviceFingerprintDialog.tsxsrc/actions/account.tssrc/actions/cloud.tssrc/tests/unit/account.test.tssrc/tests/unit/cloudHandler-sync.test.ts