Jev MCP 0.1.5

Full Changelog: v0.1.4...v0.1.5

Jev MCP 0.1.4

Signed and notarized — the first release that is.

The macOS app carries the team's Developer ID Application certificate (Q4KD7AC52U) and Apple's
notarization ticket, stapled into the bundle: spctl -a -vvv -t exec "Jev MCP.app" answers
accepted, source=Notarized Developer ID. The old «"Jev MCP.app" is damaged and cannot be
opened» is gone, and no xattr line is needed.

• macOS — Jev.MCP_0.1.4_aarch64.dmg (Apple silicon), signed and notarized
• Windows — Jev.MCP_0.1.4_x64-setup.exe and Jev.MCP_0.1.4_x64_en-US.msi
• Linux — Jev.MCP_0.1.4_amd64.AppImage and Jev.MCP_0.1.4_amd64.deb
• Server only (no tray app, for hosts that want just the server) — jev-mcp-server-0.1.4.tar.gz

Two things macOS may still do, both harmless to the app: it may ask you to confirm the first
launch of a downloaded copy (the standard quarantine question — click Open once), and while
that quarantine flag is present it may run the app from a randomized read-only copy instead of
/Applications. The second one matters only for Launch at startup, whose login item would
record that temporary path — launch the app once from /Applications before enabling it, or run
xattr -dr com.apple.quarantine "/Applications/Jev MCP.app".

The tray app carries the MCP server inside it (Node included, nothing else to install); the
server-only bundle is for a host that runs it as a plain process. Both read their configuration
from a single .env: one endpoint (JEV_URL), one key (JEV_API_KEY), one model
(JEV_MODEL), one answer spelling (JEV_QUESTION_TYPE) — the same twelve tools either way.