Integration Requirements
Official integrations should include:
- compatibility checks
- ChangePlan generation
- idempotent behavior
- verification
- tests
- documentation
Safety
Section titled “Safety”Integrations must not assume every project has the same layout. Check the detected context and inspect the target project before planning changes.
Idempotency
Section titled “Idempotency”Running the same integration again should not duplicate files, dependencies, providers, settings entries, or environment variables.
Verification
Section titled “Verification”Verification should distinguish dependency presence from complete setup. A dependency-only project should often be partial, not healthy.
Documentation
Section titled “Documentation”Each official integration should document:
- capability
- status
- trust
- setup maturity
- supported ecosystems and frameworks
- command
- what Avis does
- files Avis may create
- files Avis may modify
- dependencies added
- doctor checks
- idempotence behavior
- manual setup differences
- official links