Potential memory leak from unbounded growth
Shared collections that only grow should be reviewed for eviction or lifecycle boundaries.
#Metadata
#Why it matters
Appending to long-lived state without a cap can leak memory across requests or over process lifetime.
#Remediation
Add eviction, scoping, or cleanup so the collection cannot grow forever across calls.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.performance.unbounded-growth-memory-leak.rule.yaml.