Remove leftover `console.trace` calls from production paths
`console.trace()` calls should not ship in production code outside an explicit dev-only branch.
#Metadata
#Why it matters
`console.trace` dumps a stack trace to stdout/stderr and is almost always leftover developer instrumentation. Stack traces in shipped output disclose internal call structure and inflate logs.
#Remediation
Remove the call or guard it behind an explicit dev-only check (`process.env.NODE_ENV !== 'production'`, `import.meta.env.DEV`, or `__DEV__`).
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.security.debug-statement-in-source.rule.yaml.