| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 3 | 1 | 0% |
| Commands | 0 | 3 | 0 | 0% |
| Section tags | 1 | 3 | 0 | 25% |
What each file covers
Sections
0 shared · 3 only in A · 1 only in B- − AI Service Test Instructions
- − Commands
- − Rules
- + Supabase Rules
Commands
0 shared · 3 only in A · 0 only in B- − python -m pytest
- − python -m pytest tests/test_health.py
- − python -m pytest tests/test_consents.py
Section tags
1 shared · 3 only in A · 0 only in B- − test
- − code-style
- − agent-behaviour
- do-not
Line diff
Aledon8/OpenLeukemia · ai-service/tests/CLAUDE.md
@@ −1 @@
1# AI Service Test Instructions
2
3## Commands
4
5Run from `ai-service/`:
6
7```sh
8python -m pytest
9python -m pytest tests/test_health.py
10python -m pytest tests/test_consents.py
11```
12
13## Rules
14
15- Keep tests focused on externally visible behavior and domain contracts.
16- Cover consent and privacy-sensitive behavior conservatively.
17- Prefer clear test names that describe the expected behavior.
18- Add regression tests when fixing bugs in API routes, schemas, or domain services.
19- If a test fails, fix the root cause and rerun the smallest failing test before broader checks.
20
Aledon8/OpenLeukemia · .cursor/rules/supabase.mdc
@@ +1 @@
1---
2description: Supabase data, storage, and RLS rules
3globs:
4 - "supabase/**/*"
5alwaysApply: false
6---
7
8# Supabase Rules
9
10- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
11- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
12- Treat RLS as a primary protection layer.
13- Pair sensitive tables with narrow, auditable policies.
14- Plan affected data flows and access paths before schema or policy changes.
15
@@ −1 +1 @@
1−# AI Service Test Instructions
1+---
2+description: Supabase data, storage, and RLS rules
3+globs:
4+ - "supabase/**/*"
5+alwaysApply: false
6+---
27
3−## Commands
8+# Supabase Rules
49
5−Run from `ai-service/`:
6−
7−```sh
8−python -m pytest
9−python -m pytest tests/test_health.py
10−python -m pytest tests/test_consents.py
11−```
12−
13−## Rules
14−
15−- Keep tests focused on externally visible behavior and domain contracts.
16−- Cover consent and privacy-sensitive behavior conservatively.
17−- Prefer clear test names that describe the expected behavior.
18−- Add regression tests when fixing bugs in API routes, schemas, or domain services.
19−- If a test fails, fix the root cause and rerun the smallest failing test before broader checks.
10+- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
11+- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
12+- Treat RLS as a primary protection layer.
13+- Pair sensitive tables with narrow, auditable policies.
14+- Plan affected data flows and access paths before schema or policy changes.
2015
