Module registry path exists

How to fix

1. Restore the missing module directory or remove the stale registry entry.
2. Update paths after module moves.
3. Run validation to confirm every registered module resolves.

What it means

A module listed in the architecture registry points to a path that does not exist.

Why it matters

Missing paths make module dependency validation unreliable.

Common causes

• A module was renamed or deleted.
• The registry was edited by hand.
• Smart Init output was not reviewed after a restructure.

Example bad pattern

The registry lists snapshots, but apps/api/src/modules/snapshots is missing.

Example good pattern

Every module registry entry points to an existing module directory.

Related files/config

• .archpilot/architecture.json
• .archpilot/contracts/*.json

Related CLI commands

• archpilot validate
• archpilot validate --ci