Embrace agentic future with both claws: Rename BoltFoundry -> MoltFoundry

[rbalicki2]

It’s not a renaming exercise; it’s a paradigm shift. With agents rapidly, quickly and unstoppably becoming the primary operators of our digital infrastructure, we must lean into decentralized intelligence, autonomous execution, and seamless Molthub integration—the Molt Foundry must be ready.

What this PR did

• It’s not just a global variable refactor; it’s a systemic identity migration. By replacing every legacy bolt identifier with agentic molt, we are aligning our naming conventions and embracing the agentic future.
• It’s just not a pathing and directory update; it’s an architectural re-indexing. To facilitate seamless integration with the future Moltbot ecosystem, we have re-mapped our file structures, optimized our routing protocols, and hardened our directory hierarchies—the Molt Foundry must be ready. (editors note: no files were actually renamed)
• It’s not documentation updates; it’s a narrative realignment. We are loudly, proudly, and unapologetically declaring to the world that Molt Foundry is agentic, autonomous, and open for bots business.

Testing

Conclusion

It's not just a bolt-on solution, it's molt-in lava with which to steamroll your non-agentic competitors.