# Inter-repo contracts. `publish:` is this project's engagement toward its counterparts —
# listing a leaf here IS the act of publishing it.
#
# This project is a CONSUMER of one interface: `polyfill-surface`, the API
# `@ng-eventually/polyfill` offers an application. The pair lives in an interface folder
# inside the concept whose territory it governs — the pulled engagement beside this
# project's own declaration of what it consumes.
#
# `pullFrom:` is a CANONICAL remote identity, because this file travels with the branch.
# Per-developer local access lives in `.project/contracts.local.yaml`, which is gitignored
# and must never be committed.

publish:
  # paths are relative to `.project/`
  refine-providers-eventually: concepts/refine-binding/polyfill-surface/usage_refine-providers-eventually.md

consume:
  - contract: polyfill-surface
    type: git
    pullFrom: git@gitea.reconnexion.apps.gueraud.net:Reconnexion/ng-eventually.git/.project/concepts/app-contract/polyfill-surface/contract_polyfill-surface.md
    # The Change policy names the pin regime: a tag carrying the package name, since that
    # repo publishes two engagements whose versions move independently.
    ref: polyfill/v1.0.0-dev.15
    into: concepts/refine-binding/polyfill-surface/