t3-code-android-nightly/.repos/effect-smol/.agents/skills/dependency-maintenance/manifest-roles.md
Julius Marminge e3c85ead63
chore(refs): sync Effect and Alchemy references to rc.115 and beta.78 (#12327)
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-09-17 23:21:25 -07:00

15 lines
2.1 KiB
Markdown

# Manifest Roles
Inspect the nearest package with the same integration shape, then justify each
added or moved entry:
| Role | Use when | Completion check |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| `dependencies` | Published runtime code requires its own installed copy. | A packed consumer receives it without adding an undeclared package. |
| `peerDependencies` | Consumers provide a compatible shared package or the public contract integrates with their copy. | The range states supported consumer versions; add a development entry when local build or tests need an installed copy. |
| `devDependencies` | Only repository build, test, type, benchmark, or code-generation work needs it. | Published runtime code and declarations do not require consumers to install it. |
| `optionalDependencies` | A runtime feature handles absence and installation failure must not block the base package. | Focused tests cover present and absent behavior. |
| Optional peer via `peerDependenciesMeta` | A consumer-provided integration is genuinely optional. | The peer remains in `peerDependencies`, and code requires it only when selected. |
Role selection is complete when every changed entry has one justified role and
peer compatibility remains independent from repository validation versions.