git:20260920.e596793 to git:20260925.0ba1d6a

7 added, 17 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.multimodule.core.IrNode">
<reason>Core IR node: structural changes break every downstream module</reason>
</file>
+ <file path="com.example.multimodule.core.IrGraphFixturesTest">
+ <reason>The golden graphs below are the layout engine&#39;s recorded output for the 1.0 release. Regenerating them makes the suite agree with the current engine instead of with the release it is meant to protect.</reason>
+ </file>
</locked_files>
<contextual_instructions>
<file path="com.example.multimodule.core">
<focus>Immutable IR data model shared across every module of the reactor.</focus>
<avoids>Adding mutable state, framework annotations, or a dependency on any sibling module.</avoids>
</file>
+ <file path="com.example.multimodule.core.IrGraphFixturesTest">
+ <focus>Build IrGraph fixtures through IrGraphFixtures.of(...), never by mutating a graph in place: the engine&#39;s layout cache keys on node identity</focus>
+ <avoids>Sharing one fixture graph between cases; the engine mutates what it lays out</avoids>
+ </file>
</contextual_instructions>
<thread_safe_elements>
<element path="com.example.multimodule.core">
<strategy>IMMUTABLE</strategy>
<note>Every type in this package is safe to publish across threads without synchronization.</note>
</element>
</thread_safe_elements>
<rule>Elements listed in <thread_safe_elements> are explicitly designed to be thread-safe via the named strategy. Any modification MUST preserve the synchronization invariant and document its reasoning in the change description.</rule>
<immutable_types>
<type path="com.example.multimodule.core.IrGraph">
</type>
</immutable_types>
<rule>Types listed in <immutable_types> are immutable by design. Never introduce non-final fields, setters, or methods that mutate instance state.</rule>
<security_elements>
<element path="com.example.multimodule.core">
<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.</aspect>
</element>
</security_elements>
<rule>Elements listed in <security_elements> are security-critical. Never weaken their security properties. Every proposed change must be explicitly reviewed for security impact.</rule>
<domain_model_elements>
<file path="com.example.multimodule.core.IrNode">
<domain_model_boundary>Pure Domain Model</domain_model_boundary>
</file>
</domain_model_elements>
<rule>Classes in <domain_model_elements> are pure domain models. Do not import or reference database or web framework dependencies (Spring, Hibernate, JPA, Jackson).</rule>
- </project_guardrails>
-
- <rule>Never propose edits to files listed in <locked_files>.</rule>
-
- <!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
- <project_guardrails>
- <locked_files>
- <file path="com.example.multimodule.core.IrGraphFixturesTest">
- <reason>The golden graphs below are the layout engine&#39;s recorded output for the 1.0 release. Regenerating them makes the suite agree with the current engine instead of with the release it is meant to protect.</reason>
- </file>
- </locked_files>
- <contextual_instructions>
- <file path="com.example.multimodule.core.IrGraphFixturesTest">
- <focus>Build IrGraph fixtures through IrGraphFixtures.of(...), never by mutating a graph in place: the engine&#39;s layout cache keys on node identity</focus>
- <avoids>Sharing one fixture graph between cases; the engine mutates what it lays out</avoids>
- </file>
- </contextual_instructions>
</project_guardrails>
<rule>Never propose edits to files listed in <locked_files>.</rule>
<!-- VIBETAGS-END -->