.cursorrules ยท diff

git:20260925.291bde5 to git:20260925.82b44e7

16 added, 32 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

# VIBETAGS-START
# AUTO-GENERATED AI RULES
# Generated by VibeTags | https://github.com/PIsberg/vibetags
# Do not edit manually.
## LOCKED FILES (DO NOT EDIT)
* `com.example.payment.PaymentProcessor` - Reason: Tied to legacy database schema v2.3. Changes will break production payment processing. Contact the payments team before modifying.
* `com.example.security.SecurityConfig` - Reason: CRITICAL: Security configuration managed by DevOps team. Any changes require security review and approval ticket SEC-XXXX
* `com.example.security.SecurityConfig.getEncryptionAlgorithm()` - Reason: Encryption algorithm tied to compliance requirements (PCI-DSS)
* `com.example.security.SecurityConfig.getKeyRotationHours()` - Reason: Key rotation period mandated by company policy
* `com.example.security.SecurityConfig.getMaxLoginAttempts()` - Reason: Max login attempts set by security team to prevent brute force
* `com.example.security.SecurityConfig.validateToken(java.lang.String)` - Reason: Token validation must match auth server exactly. Changes will break all client authentication
* `com.example.service.OrderService.calculateTax(java.lang.String,double)` - Reason: Tax calculation uses Avalara API integration. Credentials and endpoint configuration managed by finance team.
* `com.example.service.OrderService.processPayment(java.lang.String,double)` - Reason: Payment processing uses Stripe API v2024.10. Changes require PCI compliance review.
* `com.example.service.OrderService.validateOrder(java.util.Map<java.lang.String,java.lang.Object>)` - Reason: Order validation implements 47 business rules. Last changed in Q2 2024 after 3-month testing cycle. DO NOT MODIFY without running full test suite.
* `com.example.testing.GoldenPayloadFixtures` - Reason: These byte sequences are the partner's recorded settlement responses. Regenerating or reformatting them makes the suite agree with itself and disagree with production.
## ๐Ÿ›ก๏ธ MANDATORY SECURITY AUDITS
When proposing edits or writing code for the following files, you MUST perform a security review before outputting the final code. You must explicitly state in your response that you have audited the changes for the required vulnerabilities.
* `com.example.database.DatabaseConnector`
- Required Checks: SQL Injection, Thread Safety issues
## ๐Ÿšซ IGNORED ELEMENTS (EXCLUDE FROM CONTEXT)
Do not reference, suggest changes to, or include the following in completions or answers.
* `com.example.internal.GeneratedMetadata` - Auto-generated at build time. Manual edits are overwritten on every build.
## ๐Ÿ”’ PII / PRIVACY GUARDRAILS
The following elements handle Personally Identifiable Information (PII).
NEVER include their runtime values in logs, console output, external API calls,
test fixtures, mock data, or code suggestions.
* `com.example.database.DatabaseConnector.password` - Database credential - never log or include in error messages
* `com.example.database.DatabaseConnector.username` - Database credential - never log or include in error messages
* `com.example.service.InventoryService.customerId` - Customer identifiers linked to purchase history โ€” PII under GDPR
* `com.example.service.NotificationService.sendEmail(java.lang.String,java.lang.String,java.lang.String)` - Email address is PII under GDPR - never log the recipient address
* `com.example.service.NotificationService.sendSMS(java.lang.String,java.lang.String)` - Phone number is PII - never log the destination number
* `com.example.service.OrderService.generateOrderConfirmation(java.lang.String)` - Output contains customer shipping address and contact details (PII)
* `com.example.strategy.impl.CreditCardStrategy.cardNumber` - PCI-DSS cardholder data - never log or expose in suggestions
* `com.example.strategy.impl.CreditCardStrategy.cvv` - PCI-DSS security code - never log or expose in suggestions
* `com.example.strategy.impl.CreditCardStrategy.expiryDate` - PCI-DSS cardholder data - never log or expose in suggestions
## ๐Ÿง  CORE FUNCTIONALITY (CHANGE WITH EXTREME CAUTION)
The following elements are well-tested core components. Make changes with extreme caution.
* `com.example.security.SecurityConfig` - Sensitivity: Critical. Note: This is a security manager. Any single-line change can compromise the entire project.
* `com.example.service.InventoryService.releaseReservation(java.lang.String)` - Sensitivity: High. Note: Must be called as the exact inverse of reserveStock. Pair changes to both methods together.
* `com.example.service.InventoryService.reserveStock(java.lang.String,int,java.lang.String)` - Sensitivity: Critical. Note: Reservation logic handles concurrent requests via optimistic locking. Took 18 months to get right under high load โ€” do not refactor without running the full concurrency test suite.
## ๐Ÿ” SECURITY-CRITICAL CODE
The following elements are security-critical. AI must not weaken security properties. Any change must be reviewed for security impact.
* `com.example.security.SecurityConfig` - Security-critical code [authentication]. Do not weaken security properties. Flag any change for security review.
## Scoped Rules Index
- Detailed per-element guardrails live in scoped rule files that load automatically when you open the matching source file. Unless an entry carries an explicit path, its file is .cursor/rules/{path, every non-alphanumeric character replaced by '-'}.mdc. Consult the file before modifying an element:
+ Detailed per-element guardrails live in scoped rule files that load automatically when you open the matching source file. A line `a.b`: `C`, `D` names a.b.C and a.b.D. Unless an entry carries an explicit path, its file is .cursor/rules/{path, every non-alphanumeric character replaced by '-'}.mdc. Consult the file before modifying an element:
- - `com.example.NotificationService`
- - `com.example.compliance.GdprService`
- - `com.example.concurrent.SessionCache`
- - `com.example.config.AsyncTestConfig`
- - `com.example.config.ParallelTestSettings`
- - `com.example.database.UserEntity`
- - `com.example.legacy.LegacyBridgeService`
- - `com.example.legacy.OldPaymentApi`
- - `com.example.metrics.OrderMetrics`
- - `com.example.payment.PaymentDetails`
- - `com.example.payment.PaymentProcessor`
- - `com.example.security.SecurityConfig`
- - `com.example.service.EvidenceBasedShowcase`
- - `com.example.service.InventoryService`
- - `com.example.service.LayeredDomainService`
- - `com.example.service.NewAnnotationsShowcase`
- - `com.example.service.NewAnnotationsShowcase.DraftKafkaIntegrationSpike`
- - `com.example.service.NewAnnotationsShowcase.ImmutableProductPrice`
- - `com.example.service.NewAnnotationsShowcase.SandboxTestHelper`
- - `com.example.service.NewAnnotationsShowcase.TaxCalculatorStrategy`
- - `com.example.service.NotificationService`
- - `com.example.service.OrderService`
- - `com.example.service.PricingService`
- - `com.example.service.PublicPaymentController`
- - `com.example.service.TransactionalPaymentService`
- - `com.example.strategy.PaymentStrategy`
- - `com.example.strategy.impl.CreditCardStrategy`
- - `com.example.utils.I18nMessageHelper`
- - `com.example.utils.StrictUtility`
- - `com.example.utils.StringParser`
- - `com.example.testing.PaymentFixturesTest`
+ - `com.example`: `NotificationService`
+ - `com.example.compliance`: `GdprService`
+ - `com.example.concurrent`: `SessionCache`
+ - `com.example.config`: `AsyncTestConfig`, `ParallelTestSettings`
+ - `com.example.database`: `UserEntity`
+ - `com.example.legacy`: `LegacyBridgeService`, `OldPaymentApi`
+ - `com.example.metrics`: `OrderMetrics`
+ - `com.example.payment`: `PaymentDetails`, `PaymentProcessor`
+ - `com.example.security`: `SecurityConfig`
+ - `com.example.service`: `EvidenceBasedShowcase`, `InventoryService`, `LayeredDomainService`, `NewAnnotationsShowcase`, `NotificationService`, `OrderService`, `PricingService`, `PublicPaymentController`, `TransactionalPaymentService`
+ - `com.example.service.NewAnnotationsShowcase`: `DraftKafkaIntegrationSpike`, `ImmutableProductPrice`, `SandboxTestHelper`, `TaxCalculatorStrategy`
+ - `com.example.strategy`: `PaymentStrategy`
+ - `com.example.strategy.impl`: `CreditCardStrategy`
+ - `com.example.utils`: `I18nMessageHelper`, `StrictUtility`, `StringParser`
+ - `com.example.testing`: `PaymentFixturesTest`
# Guardrails for test code are in TESTING.md. Read it before modifying anything under a test source set.
# VIBETAGS-END