video1.0<iframe src="https://www.loom.com/embed/50b74ac8385a495d9fd4ca27c5126954" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/50b74ac8385a495d9fd4ca27c5126954-ff8e6d30da665d51.gif215.489This Loom explains how the team plans to address a large set of codebase errors by categorizing and fixing them systematically. The author downloaded the ticket content as HTML, converted it to JSON, and classified the errors into four buckets: ESLint directive comments and error ranges, Lifecycle CSS issues, inline style problems, and DOM helper replacements. They also created a local script with specific test cases for each bucket to ensure nothing is missed during smoke testing. The root cause is that Obsidian guidelines are not enforced in the development process, and the author will follow up on adding the relevant Obsidian ESLint configuration and improving compliance in agent-generated code.