git:20260820.1cddfe2 to git:20260911.a884ca8
1 added, 1 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 -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
<locked_files>
<file path="com.example.alltiers.billing.InvoiceController.invoiceNumber(long)">
<reason>The invoice number format is on partner contracts; changing it breaks reconciliation</reason>
</file>
</locked_files>
<audit_requirements>
<file path="com.example.alltiers.billing.InvoiceController">
<vulnerability_check>SQL Injection</vulnerability_check>
<vulnerability_check>Broken Access Control</vulnerability_check>
</file>
</audit_requirements>
<rule>
If you are asked to modify any file listed in <audit_requirements>, you must first silently analyze your proposed code for the listed <vulnerability_check> items. If your code introduces these vulnerabilities, you must rewrite it before displaying it to the user.
</rule>
<pii_guardrails>
<element path="com.example.alltiers.billing.InvoiceController.billingEmail">
<reason>Billing email identifies a natural person; never log it or echo it back</reason>
</element>
</pii_guardrails>
<rule>
Never include runtime values of elements listed in <pii_guardrails> in logs, console output, external API calls, test fixtures, mock data, or code suggestions. Treat their values as strictly confidential.
</rule>
<core_elements>
<element path="com.example.alltiers.billing.LedgerEntry">
<sensitivity>critical</sensitivity>
<note>Every monetary total in the system is derived from these rows</note>
</element>
</core_elements>
<rule>Elements listed in <core_elements> are well-tested core components. Make changes with extreme caution and verify comprehensive test coverage before proposing modifications.</rule>
<scoped_rules>
- <note>Detailed per-element guardrails for the elements below live in scoped rule files that load automatically when the matching source file is opened. Consult the referenced file before modifying an element.</note>
+ <note>Detailed per-element guardrails for the elements below live in scoped rule files that load automatically when the matching source file is opened. Unless an entry carries an explicit path, its file is .claude/rules/{path, every non-alphanumeric character replaced by '-'}.md. Consult the file before modifying an element.</note>
<element path="com.example.alltiers.billing.InvoiceController" rules=".claude/rules/api-endpoints.md"/>
<element path="com.example.alltiers.billing.LedgerEntry" rules=".claude/rules/domain-model.md"/>
<element path="com.example.alltiers.billing.PaymentGateway" rules=".claude/rules/payments.md"/>
<element path="com.example.alltiers.billing.TaxRules" rules=".claude/rules/domain-model.md"/>
</scoped_rules>
<rule>When you work on any element listed in <scoped_rules>, open its referenced rule file and apply the guardrails there. The rule files are the authoritative source for those elements.</rule>
</project_guardrails>
<rule>Never propose edits to files listed in <locked_files>.</rule>
<!-- VIBETAGS-END -->