🎯 Use case
This file lives under “constants/”, which covers static strings, built-in prompts, spinners, and style constants. On the API surface it exposes E_TOOL_USE_SUMMARY_GENERATION_FAILED — mainly types, interfaces, or factory objects. What the file header says: Error IDs for tracking error sources in production. These IDs are obfuscated identifiers that help us trace which logError() call generated an error. These errors are represented as individual const exports for optimal dead code elimination (external build will only see the numbe.
Generated from folder role, exports, dependency roots, and inline comments — not hand-reviewed for every path.
🧠 Inline summary
Error IDs for tracking error sources in production. These IDs are obfuscated identifiers that help us trace which logError() call generated an error. These errors are represented as individual const exports for optimal dead code elimination (external build will only see the numbers). ADDING A NEW ERROR TYPE: 1. Add a const based on Next ID. 2. Increment Next ID. Next ID: 346
📤 Exports (heuristic)
E_TOOL_USE_SUMMARY_GENERATION_FAILED
🖥️ Source preview
/** * Error IDs for tracking error sources in production. * These IDs are obfuscated identifiers that help us trace * which logError() call generated an error. * * These errors are represented as individual const exports for optimal * dead code elimination (external build will only see the numbers). * * ADDING A NEW ERROR TYPE: * 1. Add a const based on Next ID. * 2. Increment Next ID. * Next ID: 346 */ export const E_TOOL_USE_SUMMARY_GENERATION_FAILED = 344