Skip to content

P3.8: Fixtures — OAuth flow + client storage scenarios #84

Description

@bjcorder

Parent tracker: #62
Spec: docs/superpowers/specs/2026-05-21-edge-case-hardening-design.md
Milestone: P3
Depends on: P3.1 through P3.7

Goal

Add representative fixtures for every new P3 check across all supported OAuth libraries and client-storage APIs.

Acceptance criteria

  • Fixtures under:
    • fixtures/generic-ts/oauth-flow-{pkce,state,nonce,redirect-uri}/
    • fixtures/nextjs/authjs-{pkce,state,nonce}-evidence/
    • fixtures/express/passport-oauth2-{pkce,state}/
    • fixtures/generic-python/authlib-{pkce,state,nonce}/
    • fixtures/generic-{js,ts}/client-storage-{localstorage,sessionstorage,url-fragment}/
  • Positive, negative, and false-positive variants where each applies.
  • Each fixture ships expected.json.
  • All placeholder values only. No real credentials, tokens, or customer code.

Files touched

  • Per the directory list above.

Doc-update checklist

  • None for this issue. Doc updates land in P3.10.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions