Repository navigation
scanner: donkey publish registers the manifest with Exchange / Agent Registry #218
Description
Summary
donkey publish takes the manifest from donkey scan and registers it, so the
registry becomes a consequence of the code rather than a chore.
Why it matters — Scenario A
The support agent has six tools. Today the Registry knows about it only if
someone registers it by hand, and the tool list is stale within a week.
Acceptance criteria
- The Exchange publish API is verified against a real sandbox first —
currently_verify.blocked(...). Do not guess the endpoint. - Publishing is idempotent; an unchanged manifest is a no-op.
- A content digest allows
--if-changedso CI does not republish on every
merge. - A collision with an existing asset fails loudly rather than overwriting.
Cross-surface impact
- area:scanner: the change.
- Verification: blocked on the Exchange publish contract.
- docs/verified-apis.md: flip the publication rows when confirmed.
Out of scope
The GitHub Action.
Activity
[-]scanner: fabric publish registers the manifest with Exchange / Agent Registry[/-][+]scanner: donkey publish registers the manifest with Exchange / Agent Registry[/+]tbolis-at-mulesoft commentedon Oct 12, 2026
Related: #1102 — the Anypoint self-managed scanner becomes a second, parallel
donkey publishtarget (GA-gated); #1107 refuses to register one service through both targets.