microsoft/data-formulator ships both files, and they share 2 of the 20 section tags.
The first runs 473 words and the second runs 546. Every list below is set membership over what the nightly stored for each file, never a re-reading of the text.
Everything indexed in microsoft/data-formulatorCounted 13 September 2026
Headings
0 in both, 9 only in the first, 14 only in the second
.cursor/rules/backend-test-conventions.mdc
Backend Test Conventions
File Location & Naming
File Structure
Conventions
Running Tests
Error Handling Test Requirements
Example
❌ BAD – vague name, no parametrize, no marker
✅ GOOD
.cursor/rules/log-sanitization.mdc
Log Sanitization
Architecture: Defense in Depth
When to Use Each Utility
Rules
Common Mistakes
BAD — dict may contain password
GOOD
BAD — URL may embed credentials
BAD — exception may leak connection string or upstream body
GOOD — log type name at warning level, full traceback at error level
BAD — full token in logs
Disabling for Local Debug
Adding New Sensitive Keys
New Module Checklist
Commands
0 in both, 4 only in the first, 1 only in the second
.cursor/rules/backend-test-conventions.mdc
pytest.mark.parametrize
pytest.fixture()
python -m pytest tests/backend/ -q
python -m pytest tests/backend/ -v 2>&1
.cursor/rules/log-sanitization.mdc
python -m pytest tests/backend/security/test_log_sanitizer.py
Section tags
2 in both, 2 only in the first, 3 only in the second
.cursor/rules/backend-test-conventions.mdc
architecture
testing-strategy
.cursor/rules/log-sanitization.mdc
types
security
do-not
In both files
test
code-style