Implement recursive import processing with BFS traversal for shared agentic workflows

[Copilot]

The compiler only processed direct imports from workflow frontmatter, ignoring nested imports in shared files. This meant workflows importing shared files that themselves had imports would miss transitive dependencies.

Changes

Queue-based BFS traversal

• Replaced linear iteration with queue-based BFS in ProcessImportsFromFrontmatterWithManifest
• Added importQueueItem struct to track import path, resolved path, section, and base directory
• Processes imports level-by-level for deterministic ordering

Recursive import discovery

• Extracts frontmatter from each imported file to discover nested imports: field
• Enqueues discovered imports for processing
• Maintains visited set for cycle detection

Import path resolution

• Nested imports now resolve relative to base workflows directory, not parent file location
• Fixes issue where shared/trends.md importing shared/python-dataviz.md looked in wrong path

Validation relaxation

• Updated isUnderWorkflowsDirectory to only flag top-level workflow files
• Shared workflow files in subdirectories can now use imports:, mcp-servers: fields
• Prevents validation errors on legitimate shared file patterns

Example

Before (only direct imports processed):

# main.md
imports:
  - shared/trends.md  # ✓ processed

# shared/trends.md  
imports:
  - shared/python-dataviz.md  # ✗ ignored

After (recursive processing):

# main.md
imports:
  - shared/trends.md  # ✓ processed (level 1)

# shared/trends.md
imports:
  - shared/python-dataviz.md  # ✓ now processed (level 2)

All three files are now correctly merged in BFS order: trends → python-dataviz.

Original prompt

Update compiler to support imports from imported share agentic workflows.

The compiler should recursively import all imported workflows and their imports.

• must handle cycles (cross referenced workflows)
• must have deterministic ordering
• must use queues to maintain node sets and todos instead of functional recursion.
• extensive testing
• use BFS traversal to generate ordering

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull Request Overview

This PR implements recursive import support for workflow files with BFS (Breadth-First Search) traversal, cycle detection, and improved validation. The changes enable workflow files to import other files that themselves contain imports, creating a hierarchical import structure.

Key Changes

• Added BFS-based recursive import processing with cycle detection in frontmatter parser
• Updated isUnderWorkflowsDirectory to correctly identify top-level workflow files vs. shared files in subdirectories
• Added comprehensive test suite covering recursive imports, cyclic imports, diamond patterns, and import ordering

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
pkg/workflow/imports_recursive_test.go	New comprehensive test suite for recursive imports, cyclic dependencies, diamond patterns, and BFS ordering
pkg/parser/frontmatter_test.go	Updated test expectation for subdirectory file detection
pkg/parser/frontmatter.go	Implemented BFS-based recursive import processing with queue-based traversal and cycle detection; enhanced validation for imported files
.github/workflows/daily-news.lock.yml	Regenerated lock file reflecting new imports, Python data visualization support, and firewall configuration changes

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

[nitpick] The comment on line 542 states nested imports are resolved relative to the workflows directory, but this design decision may be problematic. In typical import systems, relative paths in nested files should be resolved relative to the importing file's directory, not the root. This inconsistency could confuse users and make it difficult to create reusable shared file hierarchies. Consider documenting this behavior prominently in user-facing documentation, or reconsider the design to support relative-to-file resolution.