fix(agent): export waits for complete workflow state

[Sg312]

Summary

Export waits for complete workflow state (fixes premature/empty exports)

Type of Change

• Bug fix

Testing

Manual testing

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[greptile-apps]

Greptile Summary

This PR addresses a timing issue in YAML workflow exports by making the export process properly asynchronous. The main fix converts the getYaml() method in the YAML store from synchronous to asynchronous, ensuring it waits for complete YAML generation before returning content. This prevents premature exports that were occurring when users triggered exports before the workflow state was fully processed.

The core changes involve:

1. YAML Store (store.ts): The getYaml() method is now async and properly awaits generateYaml() when data is stale, ensuring fresh YAML content is available before export
2. Export Controls Component: The handleExportYaml function is converted to async/await pattern to properly wait for the YAML generation process
3. Environment Configuration: The isDev constant is hardcoded to false, disabling development-specific features across the application

The first two changes work together to fix the race condition where exports could happen before YAML generation completed via the /api/workflows/yaml/convert endpoint. The YAML store checks if cached content is stale (>1 second old) and refreshes it through an API call when needed. The export component was already designed to handle async operations, so the conversion to async/await integrates smoothly with existing error handling and loading states.

PR Description Notes:

• Several checklist items remain unchecked, including style guidelines, self-review, and testing requirements

Confidence score: 2/5

• This PR contains a critical unrelated change that will cause significant issues in development environments
• Score severely lowered due to the hardcoded isDev = false change that disables all development features regardless of NODE_ENV
• The environment change appears unrelated to the stated bug fix and could break development workflows, debugging, and logging

_{3 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	❌ Failed (Inspect)			Aug 6, 2025 6:24pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Aug 6, 2025 6:24pm