.cursorrules ยท diff

git:20260919.0d98a54 to git:20261017.3209339

1 added, 0 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.kotlin.AccountLedger.reconcile$se_deversity_vibetags_example_vibetags_example_kotlin(java.lang.String)` - Reason: LEDGER-INTERNAL-KEPT: reconciliation batches are replayed by the audit job.
* `com.example.kotlin.AccountLedger.settle(java.lang.Object)` - Reason: LEDGER-RESULT-KEPT: settlement outcome mapping is part of the payout contract.
+ * `com.example.kotlin.Invoice.total()` - Reason: BILLING-MULTI-CLASS: invoice totals are signed by the e-invoicing gateway, which rejects any change in rounding.
* `com.example.kotlin.PaymentService.chargeKey(java.lang.String,int)` - Reason: Charge idempotency key derivation is contract-tested against the gateway. Changing it re-charges in-flight payments.
## CONTEXTUAL RULES
* `com.example.kotlin.PaymentService`
* Focus: Coordinates payment authorization and capture against the gateway
* Avoid: Retry logic โ€” the gateway client already retries; a second layer double-charges
## ๐Ÿ”’ 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.kotlin.CustomerVault` - Holds customer PII โ€” never log, expose, or include field values in suggestions.
## ๐Ÿง  CORE FUNCTIONALITY (CHANGE WITH EXTREME CAUTION)
The following elements are well-tested core components. Make changes with extreme caution.
* `com.example.kotlin.CustomerVault.findCustomer(java.lang.String)` - Sensitivity: critical. Note: Primary lookup path for every checkout; covered by the vault contract suite
## Inherited Guardrails (dependencies)
These come from packages this project depends on. They constrain how the dependency may be used; they are not editable from here.
- `com.example.multimodule.core` (from se.deversity.vibetags.example:multimodule-core:1.0)
- @AISecure: aspect=Node identity is a security boundary: never build an IrNode from unvalidated external input, and never expose its raw id in a URL or log line.
## Inherited Context (dependencies)
Conventions the dependency's authors documented. Follow them unless this project's own rules above say otherwise.
- `com.example.multimodule.core` (from se.deversity.vibetags.example:multimodule-core:1.0)
- @AIContext: avoids=Adding mutable state, framework annotations, or a dependency on any sibling module.; focus=Immutable IR data model shared across every module of the reactor.
# VIBETAGS-END