chore(agents): improv AI files

Author: RomuDeuxfois

.github/agents/api-reviewer.agent.md

@@ -122,8 +122,8 @@ If the PR changes Output DTO fields, flag for frontend type regeneration:
 
 ## What NOT to Flag
 
-- `@JsonIgnore` on `tenant` relation → correct, prevents circular reference and data exposure
-- `skipRBAC = true` with an explanatory comment → intentional bypass, not missing `@AccessControl`
+In addition to **Shared Exceptions** in `AGENTS.md`:
+
 - Legacy controllers in `io.openaev.rest` that are NOT modified in this PR → migration is incremental
 - Output DTOs including `id` field → standard, required for client-side referencing
 - `@Transactional` on controller methods that coordinate multiple service calls → acceptable pattern

.github/agents/frontend-reviewer.agent.md

@@ -50,6 +50,8 @@ These thresholds trigger automatic severity levels regardless of subjective asse
 
 ## What NOT to Flag
 
+In addition to **Shared Exceptions** in `AGENTS.md`:
+
 - Legacy `.jsx` files that are NOT being touched in this PR — migration is incremental
 - `makeStyles` in files not modified by this PR — only flag when the file is being changed
 - Redux store usage in existing features — only flag for new features

.github/agents/multi-tenancy-reviewer.agent.md

@@ -93,15 +93,11 @@ For tenant-scoped tables:
 
 ## What NOT to Flag
 
-- Platform-level entities (`Tenant`) without `@Filter` → correct by design
-- Dual-scope entities (Settings, User, Role, Group) without `@Filter` → correct by design, scope enforced by services
-- `TenantContext.getCurrentTenant()` used in **legacy `io.openaev.rest` controllers** to pass tenant as argument to services → acceptable (legacy), but new code must use `TENANT_PREFIX` + `@PathVariable`
+In addition to **Shared Exceptions** in `AGENTS.md`:
+
 - `@PathVariable String tenantId` in new `io.openaev.api` controllers → this is the correct pattern
 - Service receiving `tenantId` as a method parameter (not calling `TenantContext` directly) → correct
-- Migration using default tenant UUID `2cffad3a-0001-4078-b0e2-ef74274022c3` → standard seed data
-- Test fixtures setting tenant context explicitly → test-only setup
-- `@JsonIgnore` already present on tenant relation → already handled
-- `FetchType.EAGER` on `capabilities` / `permissions` collections → intentional for RBAC performance, not a tenant issue
+- Test fixtures setting tenant context explicitly → test-only setup (distinct from hardcoded credentials)
 
 ## Output Format
 

.github/agents/performance-reviewer.agent.md

@@ -45,7 +45,8 @@ Escalate to **Opus 4.6** for reviews involving complex query optimization or arc
 
 ## What NOT to Flag
 
-- `FetchType.EAGER` on `capabilities` / `permissions` collections → small, always-needed for RBAC (intentional exception, documented in `security.instructions.md`)
+In addition to **Shared Exceptions** in `AGENTS.md`:
+
 - `findAll()` on reference data tables (enum-like, <50 rows) — e.g. `ResourceType`, `Capability`
 - In-memory filtering on collections already fetched for other reasons
 - Test code performance — only flag production code