1. The "Fragile Regex" Problem (Agentic Repair) Building the "Self-Healing" agent was the hardest part. Initially, our regex patterns for detecting and fixing Solidity vulnerabilities (like Reentrancy) were too brittle. If a developer formatted their code with different spacing or comments, the Agent would break the file while trying to inject the nonReentrant modifier.

How we solved it: We moved from simple string replacement to a more robust AST-like parsing strategy. We created a rigorous test suite of "badly formatted" contracts to ensure the Agent could identify the correct injection point 100% of the time without corrupting the syntax.

2. Verifying Attestations On-Chain (Foundry + EAS) Integrating the Ethereum Attestation Service (EAS) into a Foundry deployment script was tricky. We needed the deployment transaction to revert if an attestation didn't exist, but checking dynamic bytes and schema UIDs inside a Solidity constructor is complex and prone to gas errors.

How we solved it: We built a custom "Gatekeeper" contract that acts as a proxy. It uses a specialized Resolver to pre-validate the schema structure before allowing the final CREATE2 deployment call. This ensured that our "Code is Law" promise was mathematically enforced on Base Sepolia.

3. Async Race Conditions (Local vs. Cloud) We faced a race condition where the CLI would try to upload the build artifact to AWS S3 before the file zipping process had fully closed the stream, resulting in corrupted 0-byte uploads.

How we solved it: We refactored the CLI's control flow to use strict await promises. We implemented a "lockfile" system that prevents the S3 upload from initializing until the local archiver library emits a distinct finalize event, ensuring data integrity.