Explanation

Understanding-oriented documentation: concepts, architecture, and context.

Deployment

• Deployment baseline — seven requirements for production Terreno apps
• GCP deployment architecture — Cloud Run + GCS/CDN topology and tradeoffs
• GCP hosting architecture — static site hosting with GCS and Cloud CDN (legacy detail)

Contents

• Local-first data — Why the local store is the UI source of truth
• Loop engineering — Fresh-invocation lifecycle, state, evidence, and orchestration boundaries
• Install agent skills — npx skills add FlourishHealth/terreno
• AI-powered workflows — Autonomous documentation, testing, and maintenance workflows
• Authentication architecture — How JWT, OAuth, and token refresh work
• Configuration system — Runtime configuration with database persistence
• Dependency management — Dependabot, auto-merge, and security practices
• Modular API design — 🚧 Why TerrenoApp replaces setupServer
• modelRouter actions — Named collection and instance operations on modelRouter
• No barrel imports — Import concrete modules, not index re-export barrels
• Positioning — Canonical copy blocks and the honest Django/Rails comparison