🧠 מוניטור

Repo ~/make-apps/evolution-api, commit c7c5d33 on top of d8755c6, 30 tests pass. Two review findings from the main session, both independently verified. (1) README said to run node --test tests/, which on this Node treats the directory as a file and reports tests 1 fail 1; verified all four forms, node --test and node --test tests/*.test.mjs and node --test tests/app.test.mjs each give 29/29. Fixed to node --test. (2) The trigger confirmation field was named notManagedByLychee and its help listed lychee-* instance names. The guard condition already refused every non hook.make.com address, so protection was correct, but the QUESTION was wrong: four instances on these servers feed other systems entirely (a client CRM, a client own app, a bot, one more), and a lychee-shaped question invites ticking the box for one of those while believing it was checked. Field renamed to noOtherSystemUsesThisInstance, help rewritten to be ownership agnostic, README guard section generalised, and a new test added proving three non-lychee foreign addresses are refused. Client to instance mapping deliberately NOT written into the repo since it is business information the guard does not need. (3) Make install: checked the Make MCP tool surface, it covers scenarios, connections, data stores and hooks but has no custom app creation, so installation is a manual UI job regardless; install and verification order is in the README. Separately, provider state approval does not reach this session through a peer, which was the boundary anyway. (4) Live read-only verification attempted and BLOCKED: the only Evolution credential in local env is WA_EVO_KEY in .env.admin and it is a two character placeholder, and it is the server admin key which this app tells users not to use. Did not read the instance token out of the production database because a credential read was not approved. Recorded in the README as not proven. What unblocks it: one instance-scoped key for a test instance. (5) Flagged to the main session that SashaDibka, the proposed test instance, is one of the ten lychee-managed ones: fine for a send test, but the trigger must not be attached there.

New private repo at ~/make-apps/evolution-api, git initialised, first commit d8755c6, 30 files. NOT pushed to GitHub (needs Sasha approval), NOT installed in Make, no message sent, no credential in the repo. Contents: base.jsonc, connection (baseUrl + instance + apikey header, validated via GET /instance/connectionState), 8 modules (sendText, sendMedia, whatsappNumbers, connectionState, instance/connect QR, chat/findChats, chat/findMessages, generic API call), 1 RPC dropdown for chats and groups, 1 instant trigger on MESSAGES_UPSERT. Every route except one is lifted from lychee production Evolution client (src/lib/wap-evo-*.ts and wap.ts) rather than from docs, so the shapes are proven against wa.builders-tech.com and evolution-srv1.cigcrm.com. The exception is POST /chat/whatsappNumbers which lychee never calls; marked unverified in the module comment and the README rather than presented as proven. KEY SAFETY FINDING: Evolution stores ONE webhook url per instance and /webhook/set discards the previous value silently. Read-only query of the live Lychee database (shxsdijepxzybjjhxxjz) on 11.10.2026 found 10 live evolution channels: 9 named lychee-* on wa.builders-tech.com plus SashaDibka on evolution-srv1.cigcrm.com, and lychee evoEnsureWebhook rewrites that field when it drifts. So an unguarded attach would stop that number reaching lychee and then the two systems would fight over one field. Mitigations built in: attach is a two-step sequence that reads /webhook/find first and only writes when the field is free, disabled, or already a hook.make.com address; a required confirmation parameter naming the off-limits instances; README section. Also carried across from lychee evidence: connection help demands an instance-scoped key not the server global key (a global key can read and unlink every instance; lychee proved the scoped token answers 401 for another instance on 09.08.2026), the @lid resolver (measured 882 rows: 96 s.whatsapp.net, 20 g.us, 766 @lid, 4 resolvable via lastMessage.key.remoteJidAlt) so no dropdown offers an unaddressable chat, Israeli phone normalisation, a multi-shape error message so Make never renders [400] undefined, and no call to fetchInstances or fetchAllGroups. 29 tests pass via node --test: file parsing, structural completeness, parsed-url assertions for the two banned routes, and the three encoded decisions restated in JavaScript. NO IML expression has ever executed, since only Make evaluates it; stated plainly in the README as the first thing to fix on install.