@fidacy/mcp 0.5.2 → 0.6.0

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.6.0
+
+### Minor Changes
+
+- Ask for the operator's email in the terminal, at install time. `npm i @fidacy/mcp` now prompts for it right after install, and `npx @fidacy/mcp setup` runs the same prompt on demand. The address registers immediately, so the install is identified from the first moment rather than anonymous until someone stumbles onto a claim link.
+
+  The prompt only appears when a human is actually there. Under `npx -y` (how MCP hosts launch the server), inside Docker builds, in CI, or with piped input, it exits instantly and silently — an install script that waits for input does not fail, it hangs forever, taking the host or the pipeline with it. `FIDACY_NONINTERACTIVE=1` forces that behaviour for anyone scripting installs. It also never fails an install: any error leaves exit code 0, because a firewall that refuses to install over a prompt is worse than one that never asked. If the network is down when you answer, the address is kept on disk and registers on the next start.
+
 ## 0.5.2
 
 ### Patch Changes

package/dist/core.js

@@ -488,7 +488,7 @@ function resolveMandateRules(cfg) {
 }
 
 // src/telemetry.ts
-var CLIENT_VERSION = true ? "0.5.2" : "dev";
+var CLIENT_VERSION = true ? "0.6.0" : "dev";
 function bandOf(amount) {
   if (typeof amount !== "number" || !Number.isFinite(amount) || amount <= 0) return void 0;
   if (amount < 10) return "lt10";