[helpcodeai]

Block 16 adds two connectors and extends the existing Mirakl one.

ManyChat (manychat, 22 tools)

• Contacts by name, email/phone or custom field, plus contact details. Tag and untag contacts, set custom and bot fields, create and update contacts. Also tags, fields, flows and growth tools, and sending a text, rich content or a flow.
• Auth is the account API key as Authorization: Bearer (Settings > API). API access needs the Pro plan; the setup text says so. {"status": "error"} answers are turned into failed calls.
• manychat_delete_tag deletes the tag account-wide, so it installs switched off. Every send and write asks for confirmation.

Zenkit (zenkit, 16 tools)

• Current user, workspaces with their collections, workspace and list users, fields, entries (filter with counts, global search, read, create, update), entry and list activity, and comments.
• Auth is the Zenkit-API-Key header. Entry values use Zenkit's <field uuid>_<key> convention, and the instructions explain it.
• zenkit_archive_entries is Zenkit's soft delete and installs switched off. There is no permanent delete.

Mirakl Seller (mirakl, now 35 tools)

• There was already a generic Mirakl adapter from block 6, so I extended it instead of adding a duplicate.
• 6 new reads: DR11 document requests, OR72 order documents, CH11 channels, SH11 shipping zones, SH12 shipping methods and SH31 logistic classes.
• 3 new writes: OR64 resolve incident, RT21 accept/refuse return and RT25 receive return.
• New aliases so the store and chat search find it as Leroy Merlin, ADEO, Conforama, BUT, home24, Maisons du Monde, Vente-unique and ePrice. The setup text now lists the base URL of each of those marketplaces.
• I also documented two gotchas seen in real traffic: entity_id needs entity_type, and an inactive locale answers 400.
• The variable stays MIRAKL_URL (without /api) so existing installs keep working.

Verification

• ManyChat was verified against the official API reference (Page API OpenAPI document at api.manychat.com/swagger).
• Zenkit was verified against the official API reference (base.zenkit.com/docs/api). The filter, create, update, comment and archive bodies also pass Zenkit's live request validation, which runs before auth.
• Mirakl was verified against the official seller OpenAPI and against a working production configuration (six marketplaces, 1,700+ successful calls), with matching paths, raw-key Authorization and multipart message bodies.
• No live calls were made with real credentials on any of the three. The *.live.spec.ts live blocks are read-only and gated behind env vars.

Left out on purpose

• Nothing that moves money (Mirakl refunds and cancellations, ManyChat payments).
• ManyChat: OTN and user_ref tools (Messenger-only, legacy).
• Zenkit: restore (the docs say POST, the server only accepts PUT), webhooks (response shape not documented) and permanent delete.

Checks run

• node scripts/validate-adapters.mjs (no new warnings)
• validate-adapters and adapter-new node tests
• satellites tests
• node scripts/adapter-count.mjs --check (477 adapters, 7213 tools)
• regenerate-catalog.mjs (output byte-identical)
• check-runtime-deps
• backend tsc --noEmit
• eslint on the specs
• Full backend jest: everything passes except database.engine.hana.spec.ts, which can't resolve hdb in my local node_modules. That is an environment issue, not caused by this change.