I would not be surprised at all if it's vibe coded. I have seen exactly the same thing myself.
I gave instruction to Claude to add a toggle button to a website where the value needs to be stored in local storage.
It is a very straightforward change. Just follow exactly how it is done for a different boolean setting and you are set. An intern can do that on the first day of their job.
Everything is done properly except that on page load, the stored setting is not read.
Which can be easily discovered if the author, with or without AI tools, has a test or manually goes through the entire workflow just once. I discovered the problem myself and fixed it.
Setting all of that aside -- even if this is not AI coded, at the least it shows the site owner doesn't have the basic care for its visitors to go through this important workflow to check if everything works properly.
And who cares if it's vibe-coded or not. Since when do we care more on the how than on the what? Are people looking at how a tool was coded before using it, as if it would accelerate confidence?
Depending on the company and their sector, people will nod in approval, or start laughing.
My company also accepted the risk of using Microsoft. We have a "data sharing agreement" together, with very powerful magical words. Compliance people are happy and sleep well.
At a recent AI workshop management made clear that they see AI as rendering sprints and scrums obsolete, that Kanban makes a lot more sense, and that estimating effort/story-points is also becoming meaningless. Which is a strong silver lining if you ask me.
I think it's to do with the bottleneck shifting away from code generation and towards specifying and reviewing and integrating code. The process of working with AI agents to produce specs, tech specs, code, and reviews lends itself more to a flow-based structure (like kanban).
Bear in mind this is a B2B enterprise company with a mix of legacy and greenfield. And management has invested heavily into designing a robust spec/context-based workflow for using agents. Might be different elsewhere.
Personally I don't think scrums, planning, retros etc were better than kanban even before AI, at least if you have switched-on, motivated and smart people on your team. They actually made things less agile, and story-points give a false sense of predictability. Imo the crucial factor may be that AI agents are smart and switched-on (with the right context).
Its a good excuse to move away from a shitty process, I'll take it! Fuck SCRUM, fuck Agile. No one was doing it anyway. I had to quit an Agile job because I was shipping shit without ever getting a lick of feedback, and this was not some webdev low stakes work, it was for planning expensive real world installations.
I know this is satire but we're in the process of rewriting the .NET Mediatr library because ... it's nothing but a simple design pattern packaged as a paid nuget package. We don't even need LLMs to reprogram it.
So the need is real, at least for enshittified libraries.