Dependencies template

What a repository relies on: other Ediky repositories, external services, and the packages that shape its design. The organization-wide view lives in Repository dependencies. This page covers one repository. Lives at docs/repos/<repo>/dependencies.md.

Generated by npm run new:repo.

Template

---
title: "Dependencies"
description: "Repositories, services and packages {{repoName}} depends on."
status: draft
---

# {{repoName}} dependencies

TODO: One paragraph summarizing what this repository can't run without.

```mermaid
flowchart LR
  repo["{{repoName}}"] --> r1[TODO: Ediky repository]
  repo --> s1[TODO: External service]
  repo --> p1[TODO: Key package]
  up[TODO: Repository that depends on this one] --> repo
```

## Ediky repositories

| Repository | Direction | How they connect | Contract |
| --- | --- | --- | --- |
| TODO | uses / used by | TODO: API, files, package, fetch at runtime | TODO: link |

## External services

| Service | Used for | Failure impact | Docs |
| --- | --- | --- | --- |
| TODO | TODO | TODO | TODO |

## Key packages

TODO: Only the packages that shape the design. Everything else lives in the
lockfile.

| Package | Version | Why |
| --- | --- | --- |
| TODO | TODO | TODO |

## Dev and build tooling

| Tool | Purpose |
| --- | --- |
| TODO | TODO |

## Upgrade notes

TODO: Pinned versions and why, known upgrade hazards, and the last upgrade
checked.

Placeholders

{{repoName}}  Display name of the repository