docs(soter): initSigh resultCode is load-bearing

The probe's signSessionOk requires resultCode==0 (SoterCapabilityProbe .kt:107), so writeInt(SOTER_OK) for initSigh is not optional. Cite the probe line in the comment so a future cleanup does not drop it on the false "detector ignores resultCode" belief, true only for the export path.
2026-06-26 16:57:12 +01:00
parent 5ddd8137df
commit 4429f0ed60
1 changed files with 1 additions and 1 deletions
@@ -168,7 +168,7 @@ object SoterServiceInterceptor : BinderInterceptor() {
                forgedReply(callingUid, txId, method) {
                    writeInt(1)
                    writeLong(1L) // session — any non-zero satisfies the probe
-                    writeInt(SOTER_OK) // resultCode
+                    writeInt(SOTER_OK) // resultCode — probe requires == 0 (SoterCapabilityProbe.kt:107)
                }
            TX_FINISH_SIGN ->
                forgedReply(callingUid, txId, method) {