Module baseline files exist

How to fix

1. Create or refresh the module baseline.
2. Commit baseline artifacts if your workflow expects them.
3. Use baseline commands when drift comparison is part of CI.

What it means

ArchPilot expected baseline files used for module drift or history comparison but could not find them.

Why it matters

Baselines help distinguish accepted architecture from newly introduced drift.

Common causes

• Baseline generation has not been run.
• Baseline files were deleted or ignored.
• The baseline path changed.

Example bad pattern

CI expects baseline comparison but no baseline artifact exists.

Example good pattern

Accepted module baseline files are present and updated through the documented baseline workflow.

Related files/config

• .archpilot
• .archpilot/architecture.json

Related CLI commands

• archpilot baseline create
• archpilot baseline check
• archpilot validate
• archpilot validate --ci