Add boilerplate code for Loop Engineering implementation

[shortthirdman]

🚀 Pull Request

📌 Summary

Template code for implementing loop engineering with various coding agents (Claude and Codex)

---

📑 Description

• Not Completed
• Completed

---

🧩 Type of Change

• 🔬 Research / Experiment
• ✨ New feature
• 🐛 Bug fix
• ♻️ Refactor (no functional change)
• ⚡ Performance improvement
• 🛠️ Build / CI / Tooling change
• 🔐 Security fix
• 🧪 Test-only change
• 📚 Documentation update
• 🚢 Production release change

---

🧪 Research vs Production Readiness

• This PR is research / experimental only
• This PR is production-ready
• This PR transitions research code toward production

Notes (if applicable):

---

🧾 Conventional Commit Compliance

• PR title follows Conventional Commits
  • Examples:
    • feat(api): add rate limiting
    • fix(ci): resolve flaky pipeline
    • chore(deps): bump terraform provider
• Commit messages are clean, meaningful, and scoped
• No breaking changes OR breaking changes are documented below

⚠️ Breaking Changes (if any)

Describe the breaking change and required migration steps

Template code for implementing loop engineering with various coding agents (Anthropic Claude Code and OpenAI Codex)

---

🔄 CI/CD & GitOps Checklist

• CI pipeline passes locally and in GitHub Actions
• Linting, formatting, and static analysis pass
• Tests added or updated (unit / integration / e2e)
• No secrets, credentials, or tokens committed
• Versioning handled only via semantic-release (no manual bumps)
• GitOps manifests updated (if applicable)
• Rollback strategy considered

---

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

---

🏗️ Infrastructure / Deployment Impact

• No infrastructure changes
• Kubernetes / Helm / Argo / Flux changes
• Terraform / Cloud resource changes
• Environment variables or secrets updated

Details:

N/A

---

🧪 Testing Strategy

• Unit tests
• Integration tests
• End-to-end tests
• Manual testing performed

Test evidence / commands run:

# example
make test

N/A

---

📊 Observability & Ops Readiness

• Logging updated (if applicable)
• Metrics / alerts added or updated
• Dashboards validated
• Error handling reviewed

---

🔐 Security & Compliance

• Security impact reviewed
• Dependency scan passed
• No new high/critical vulnerabilities introduced
• Access control / RBAC reviewed (if applicable)

---

📚 Documentation

• Code comments added/updated
• README / docs updated
• Runbooks or ADRs updated (if applicable)

---

🔗 Related Issues / PRs

* Fixes #
* Related to #
* Closes # <!-- Issue # here -->

---

👀 Reviewer Notes

---

ℹ Additional Information

N/A