Review Angular architecture

Review an Angular codebase against two lenses that compose:

• Domain structure (DDD): is the system carved into bounded contexts with isolated domains, the right library categories, and enforced access restrictions? Vocabulary and checklist in references/ddd.md.
• Module depth: are the modules behind those seams deep (much behaviour behind a small interface) or shallow pass-throughs? Vocabulary in references/language.md.

The frame that unites them: bounded contexts name where the seams belong; depth measures the modules sitting behind them. A finding can be a misplaced seam (DDD), a shallow module (depth), or both. Use the terms in references/ddd.md and references/language.md exactly – consistent language is the point, so don't drift into "component", "service", "API", or "boundary".

This review is informed by the project's own domain model: a CONTEXT.md glossary names good seams, and ADRs record decisions the review must not re-litigate (check for a root ADR.md with ## ADR-NNN sections or a docs/adr/NNNN-title.md folder; when neither exists, create ADR.md lazily on the first decision worth recording).

1. Explore

Read first – these and AGENTS.md override any generic example here:

• The project domain glossary (CONTEXT.md) and any ADRs touching the area under review.
• style-guide/style-guide.md, then the specific guides for the code being judged (style-guide/style-guide.ts.md, style-guide/style-guide.html.md, style-guide/style-guide.scss.md).

Detect the project shape, because it sets how the DDD model maps: