Why: BiometricApiImpl.checkLiveness has no endpoint to call — server-side passive liveness is folded into /biometric/verify (uniface, passive), so the client returns a safe non-blocking 'live' verdict to avoid ever gating login. This is intentional today but is a known stub to revisit if a dedicated standalone liveness endpoint ever ships.
Done when: either a dedicated identity liveness endpoint is wired here, or the stub is documented as permanent and the dead probe path removed.
source: shared/src/commonMain/kotlin/com/fivucsas/shared/data/remote/api/BiometricApiImpl.kt:78
Migrated from shared/src/commonMain/kotlin/com/fivucsas/shared/data/remote/api/BiometricApiImpl.kt:78.
Why: BiometricApiImpl.checkLiveness has no endpoint to call — server-side passive liveness is folded into /biometric/verify (uniface, passive), so the client returns a safe non-blocking 'live' verdict to avoid ever gating login. This is intentional today but is a known stub to revisit if a dedicated standalone liveness endpoint ever ships.
Done when: either a dedicated identity liveness endpoint is wired here, or the stub is documented as permanent and the dead probe path removed.
source: shared/src/commonMain/kotlin/com/fivucsas/shared/data/remote/api/BiometricApiImpl.kt:78
Migrated from
shared/src/commonMain/kotlin/com/fivucsas/shared/data/remote/api/BiometricApiImpl.kt:78.