working-directory-conventions

You can enforce a consistent working directory by applying a container-root convention that requires all component agents to operate from the container directory. This prevents path resolution inconsistencies across multi-component architectures.

Import and test path errors occur when component operations run from incorrect working directories. They happen because component paths are not resolved relative to the container root, causing imports referencing components like {component}/src/... to fail.

The best way to resolve component paths is to set the container as the working directory and run all scripts and tools from there. This ensures imports reference components as {component}/src/... and prevents path resolution errors.

No external tooling is required to enforce container root workspace conventions. The approach relies entirely on documented workspace conventions that mandate performing tasks from the container root directory.

You need a container-root working directory when testing multi-component architectures to ensure import paths resolve correctly. It prevents test path errors by standardizing how component paths are resolved relative to the container root.