Skip to main content

max / makenotwork

pin the exact code on the sync account guard, restoring the hygiene seal fde8b6b9 landed `resp.status.is_client_error()`, which took `test_hygiene`'s loose-status count from 6 to 7 and left that seal red. The endpoint answers 401, so say 401. Worth noticing rather than just fixing: the seal was red in a commit that passed both hooks. The seals are tests; pre-commit runs gitleaks and rustfmt, and pre-push's build gate is skipped in this repo because MNW has no root Cargo.toml, so it gets the internal-deps gate alone. What would have caught it is the astra sweep's `test` check (nextest over the workspace), the next night, or Sando's cargo_test gate at deploy. So the exposure is a day, not forever.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session
https://claude.ai/code/session_01MptwXZ8k65v19rFmdGAyki
Author: Max Johnson <me@maxj.phd> · 2026-09-01 01:24 UTC
Signed with PGP, not checked
Commit: c17687dd7cd7dbe4d47302d3a63ee6e67ef90729
Parent: 770033c
1 file changed, +4 insertions, -3 deletions
@@ -303,9 +303,10 @@
303 303
304 304 let resp = h.client.get("/api/v1/sync/account").await;
305 305
306 - assert!(
307 - resp.status.is_client_error(),
308 - "an identity endpoint with no token is refused, got {}",
306 + assert_eq!(
307 + resp.status.as_u16(),
308 + 401,
309 + "an identity endpoint with no token is unauthorized, got {}",
309 310 resp.status
310 311 );
311 312 }