I have an sbt-based Scala project that keeps failing at runtime with a mix of errors and odd behaviour. After digging through the dependency tree I spotted what looks like a “ghost” POM / purchase-order artifact that sbt keeps trying to resolve even though it no longer exists in my build definitions. I need someone who knows sbt inside out to: • Identify the phantom POM entry that’s being pulled in during the run task. • Remove or correctly exclude it from build.sbt (or plugins.sbt if that’s where it sneaks in). • Verify the application starts and runs cleanly once the fix is in place. • Give me a brief note explaining what you changed so I can avoid the issue next time. This is a quick, targeted fix rather than a full refactor, so I’m looking for a concise solution I can apply right away.