Dependency policy

​

Principles

• Keep shared runtime dependencies exact-pinned across shell and feature packages.
• Keep stralos-ui and stralos-domain as explicit shared contract surfaces.
• Avoid feature packages importing shell internals.
• Prefer per-feature API clients unless a shared contract is deliberately introduced.
• Do not reintroduce stralos-mock-api consumers.

​

Frontend package expectations

• type-check, lint, test, and build should stay available for frontend packages.
• Route contracts should remain small and stable.
• Shared UI primitives belong in stralos-ui only when multiple packages need them.

​

API package expectations

• API packages should keep service-local dependencies explicit.
• Build and Lambda packaging should remain per repo.
• Database migrations should stay with the service that owns the schema.