fix(builderlab-auth): default non-macOS session storage to a private file

.github/workflows/ci.yml

@@ -45,3 +45,22 @@ jobs:
 
       - name: Run isolated Docker acceptance tests
         run: just bl-cli-docker-acceptance
+
+  auth-windows:
+    name: Auth storage (Windows)
+    runs-on: windows-latest
+    timeout-minutes: 30
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6
+        with:
+          persist-credentials: false
+
+      - name: Restore Rust cache
+        uses: Swatinem/rust-cache@6323deb102c322ba6fcbdcafc7e3dddab59af2b6 # v2.9.2
+        with:
+          workspaces: . -> target
+
+      - name: Run builderlab-auth tests
+        run: cargo test --locked -p builderlab-auth

Cargo.toml

@@ -6,7 +6,7 @@ resolver = "2"
 name = "sq-kgoose"
 version = "0.0.1-beta.1"
 edition = "2021"
-rust-version = "1.88.0"
+rust-version = "1.89.0"
 license = "Apache-2.0"
 publish = false
 

README.md

@@ -263,9 +263,10 @@ KGOOSE_BASE_URL=http://localhost:8080 \
   ./target/debug/bl --local-dev skills list
 ```
 
-Authentication storage defaults to the operating-system keyring where
-supported. The local auth guide documents file-backed storage for tests and
-development without modifying keyring state.
+Authentication storage defaults to the operating-system keyring on macOS and
+to a private file, `<bl home>/auth-sessions.json`, on Linux and Windows. The
+local auth guide documents file-backed storage for tests and development
+without modifying the default store.
 
 ## Project layout
 
@@ -314,8 +315,9 @@ Do not use `--force` just to adopt an existing installation.
 The backend `X-BB-Session-Credential` header, `BBIdentity` authorization scheme,
 `builderbot` extension ID, and
 Playpen routing key are protocol identifiers and retain their existing names.
-On Linux and Windows, keyring login storage is not implemented; the explicit
-`BL_AUTH_STORAGE=file` option is available as described in the local auth guide.
+On Linux and Windows, keyring login storage is not implemented, so login
+sessions are stored in `<bl home>/auth-sessions.json` without any setup;
+`BL_AUTH_STORAGE=file:<path>` selects another file.
 
 On managed bb-public Blox workstations, `bl workspace list` uses the same
 operator-configured Kgoose endpoint and Roxy owner identity as `bl tools`.

crates/builderlab-auth/Cargo.toml

@@ -2,7 +2,7 @@
 name = "builderlab-auth"
 version = "0.1.0"
 edition = "2021"
-rust-version = "1.88.0"
+rust-version = "1.89.0"
 license = "Apache-2.0"
 publish = false