# fix\(desktop\): log the keychain read only for Chromium, and narrow the Windows lock probe · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/a22067681b5211f8f1796103904bb72fa8571373)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: a22067681b5211f8f1796103904bb72fa8571373

Requested commit: a22067681b5211f8f1796103904bb72fa8571373

Commit: a22067681b5211f8f1796103904bb72fa8571373

Tree: d02d99bc1cd2727750592e159af6fee649641ab8

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(desktop): log the keychain read only for Chromium, and narrow the Windows lock probe

A Firefox import logged "Reading browser cookie key from the keychain" with the executable path even though it never touches a keychain, putting a false security-sensitive event in the audit trail; the log now sits behind the Chromium engine check. Also narrows isLockHeld to the Windows probe its doc describes (its only caller already guards on win32) and deletes entryExists, which that dead branch was the last use of.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

```

## Parents

- [c44e9590f68d17478f581e09585052513672701b](https://git.cafe/pingdotgg/t3code/commit/c44e9590f68d17478f581e09585052513672701b?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/a22067681b5211f8f1796103904bb72fa8571373?format=markdown)