{
  "title": "Sign-in request comparison",
  "checkedAt": "2026-10-31T13:07:11.329Z",
  "environment": "Isolated local sign-in scenario",
  "scope": "Constructed HTTP service on loopback with in-memory accounts and sessions. Not a production incident. Node fetch does not manage browser cookies; the second request deliberately omits Cookie and the third explicitly carries it.",
  "observations": [
    {
      "requestId": "signin-01",
      "method": "POST",
      "path": "/sign-in",
      "status": 200,
      "credentialsAccepted": true,
      "accountLookupMatched": true,
      "sessionCreated": true,
      "cookieIssued": true
    },
    {
      "requestId": "session-02",
      "method": "GET",
      "path": "/session",
      "status": 401,
      "cookiePresent": false,
      "sessionLookupAttempted": false
    },
    {
      "requestId": "session-03",
      "method": "GET",
      "path": "/session",
      "status": 200,
      "cookiePresent": true,
      "sessionLookupAttempted": true,
      "sessionLookupMatched": true
    }
  ],
  "responses": [
    {
      "requestId": "signin-01",
      "status": 200,
      "body": {
        "signedIn": true
      },
      "setCookie": "session=[redacted]; Path=/; HttpOnly; SameSite=Lax"
    },
    {
      "requestId": "session-02",
      "status": 401,
      "body": {
        "error": "missing_session"
      },
      "requestCookie": "absent"
    },
    {
      "requestId": "session-03",
      "status": 200,
      "body": {
        "authenticated": true,
        "accountId": "account-local"
      },
      "requestCookie": "session=[redacted]"
    }
  ],
  "conclusion": "The follow-up request is rejected when the session cookie is absent; carrying the issued cookie restores authenticated access. Browser cookie policy, CORS and proxy behavior were not exercised, so their role in a real incident remains unproven.",
  "sourceSha256": "139a938996263165361b8349b76a86fb520b49c508a7f907f419aed222931b8e"
}
