fix: eliminate magic strings and fix aggregate boundary detection

- Extract DDD folder names and repository method suggestions to constants
- Fix regex pattern to support relative paths (domain/... without leading /)
- Add non-aggregate folder exclusions (constants, shared, factories, etc.)
- Remove findAll, exists, count from ORM_QUERY_METHODS (valid domain methods)
- Add exists, count, countBy patterns to domainMethodPatterns
- Add aggregate boundary test examples

packages/guardian/src/domain/constants/Messages.ts

@@ -49,6 +49,10 @@ export const REPOSITORY_PATTERN_MESSAGES = {
     SUGGESTION_QUERY: "find or search",
 }
 
+export const REPOSITORY_FALLBACK_SUGGESTIONS = {
+    DEFAULT: "findById() or findByEmail()",
+}
+
 export const AGGREGATE_VIOLATION_MESSAGES = {
     USE_ID_REFERENCE: "1. Reference other aggregates by ID (UserId, OrderId) instead of entity",
     USE_VALUE_OBJECT:

packages/guardian/src/domain/value-objects/RepositoryViolation.ts

@@ -1,6 +1,6 @@
 import { ValueObject } from "./ValueObject"
 import { REPOSITORY_VIOLATION_TYPES } from "../../shared/constants/rules"
-import { REPOSITORY_PATTERN_MESSAGES } from "../constants/Messages"
+import { REPOSITORY_FALLBACK_SUGGESTIONS, REPOSITORY_PATTERN_MESSAGES } from "../constants/Messages"
 
 interface RepositoryViolationProps {
     readonly violationType:
@@ -192,7 +192,7 @@ export class RepositoryViolation extends ValueObject<RepositoryViolationProps> {
         const fallbackSuggestion =
             technicalToDomain[this.props.methodName as keyof typeof technicalToDomain]
         const finalSuggestion =
-            smartSuggestion || fallbackSuggestion || "findById() or findByEmail()"
+            smartSuggestion || fallbackSuggestion || REPOSITORY_FALLBACK_SUGGESTIONS.DEFAULT
 
         return [
             REPOSITORY_PATTERN_MESSAGES.STEP_RENAME_METHOD,