docs: Update AI Testing Rules in CLAUDE.md#1
Conversation
Updated CLAUDE.md to specify that AI agents should only be responsible for running unit tests locally during development. Integration tests and any tests dependent on external services (like Docker, Testcontainers, PostgreSQL, Redis) will be deferred to CI/CD workflows for verification. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Updated CLAUDE.md to expand the Docker endpoint rule to cover all environment-specific configurations (like connection strings and secrets), emphasizing that these should never be hardcoded. Also removed the outdated specific instructions for Testcontainers on WSL2. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Refined the Excalidraw wireframe templates and generation script to adhere to user's 'UX as #1' guidelines, promoting a cleaner, typography-first approach, and reducing visual clutter across authentication, setting, and state screens. Fixed PRNG deterministic seed shifting issue. Regenerated SVGs to reflect these modern UX patterns. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
…x casing Addresses the CodeRabbit review on the verify-email endpoint and a latent FE/BE casing bug: - Response DTO (CodeRabbit #1): replace `.Produces<object>()` + `new { sessionEstablished = true }` with VerifyEmailSessionEstablishedDto in the Application layer (repo rule: response DTOs live in Application). - Single application result (CodeRabbit #2): VerifyEmailHandler now gathers the sign-in permissions (before commit) and returns them on VerifyEmailSuccessDto, so the endpoint is one mediator.Send → sign in → return. Removes the second GetUserTokenClaims round-trip that could fail after the one-time link was already consumed. - Casing: regenerate openapi.json + api-types.ts (session_established), point VerifyEmailResponse at the generated schema, and read data?.session_established in useVerifyEmail — the post-verify PKCE branch was dead before (FE read camelCase off a snake_case wire). Verified: full dotnet test Axis.sln green (0 failed), frontend ci + tests, OpenApiDocumentTests green/idempotent. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Added rule in CLAUDE.md to bypass Testcontainers/Docker integration testing locally. CI/CD will handle full test suite verification.
Generalize rule against hardcoding config values and remove outdated WSL2 config rule.
PR created automatically by Jules for task 1137306013417195195 started by @phuongnse