@rubytech/create-maxy 1.0.803 → 1.0.805

package/dist/index.js

@@ -1760,22 +1760,10 @@ function installTunnelScripts() {
     const setupSrc = join(INSTALL_DIR, "platform/plugins/cloudflare/scripts/setup-tunnel.sh");
     const resetSrc = join(INSTALL_DIR, "platform/plugins/cloudflare/scripts/reset-tunnel.sh");
     const listSrc = join(INSTALL_DIR, "platform/plugins/cloudflare/scripts/list-cf-domains.sh");
-    // _cdp-authorize.mjs is invoked by setup-tunnel.sh via `node <path>` and
-    // resolved via readlink -f → same dir as the script. It does NOT get a
-    // $HOME symlink — it's a helper, not a top-level operator command. We do
-    // chmod +x defensively so `ls -l` and any ad-hoc `~/setup-tunnel.sh` copy
-    // flow sees it as executable (Task 588).
-    //
-    // _cdp-authorize-matcher.mjs is imported by _cdp-authorize.mjs (Task 855)
-    // — the tri-state matcher's MATCH_EXPR + findMatch live in this side
-    // module so JSDOM tests run identical logic to the live page. chmod +x
-    // is defensive symmetry; the file is read by Node, not exec'd.
-    const cdpAuthorizeSrc = join(INSTALL_DIR, "platform/plugins/cloudflare/scripts/_cdp-authorize.mjs");
-    const cdpMatcherSrc = join(INSTALL_DIR, "platform/plugins/cloudflare/scripts/_cdp-authorize-matcher.mjs");
     const setupLink = resolve(process.env.HOME ?? "/root", "setup-tunnel.sh");
     const resetLink = resolve(process.env.HOME ?? "/root", "reset-tunnel.sh");
     const listLink = resolve(process.env.HOME ?? "/root", "list-cf-domains.sh");
-    for (const src of [setupSrc, resetSrc, listSrc, cdpAuthorizeSrc, cdpMatcherSrc]) {
+    for (const src of [setupSrc, resetSrc, listSrc]) {
         try {
             chmodSync(src, 0o755);
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.803",
+  "version": "1.0.805",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/platform/plugins/docs/references/troubleshooting.md

@@ -170,6 +170,30 @@ The setup script emits either the raw `https://dash.cloudflare.com/argotunnel?..
 
 The transient unit was auto-collected by systemd before the client subscribed. Race condition: action finished in <1 s. The per-action log file is retained for 7 days; look for it by name under `~/.maxy/logs/actions/`. If it isn't there, the unit failed before any output (check `journalctl --user -u maxy-action-<id>`).
 
+**Cloudflare-setup action card shows "Failed (exit null)" after the tunnel works.**
+
+> **Pre-Task-860 misdiagnosis.** Devices on platform versions before Task 860 misrender a successful `cloudflare-setup` run as red `Failed (exit null) · ~20s` because the script-armed brand-service restart kills the SSE generator before it can read the action's exit code. The Cloudflare side is fine in this case — the tunnel is created, DNS is routed, the brand service comes back up.
+>
+> **First-line check:** open the persisted action log directly. Two markers prove success:
+>
+> ```bash
+> grep -E 'step=service-restart-armed exit=0|step=done' \
+>   ~/.{configDir}/logs/actions/cloudflare-setup-*.log | tail -2
+> ```
+>
+> Both lines present in the log ⇒ the script succeeded; the UI banner is the bug, not the run. On post-Task-860 platforms the action card renders `Completed · Ns` on the same log shape; the card now distinguishes four states:
+>
+> - `Completed` (green) — `code === 0` (whether reported by systemd or recovered from the log).
+> - `Failed (exit N)` (red) — non-zero exit reported by systemd. Real failure, follow the existing remediation paths.
+> - `Restart in progress` (neutral sage) — arming line present in log but the post-arm `step=done` was not written before the unit was GC'd. Resolves automatically once `/api/admin/version` responds; if it stays >90 s, falls through to amber.
+> - `Failed (exit unobserved)` (amber) — neither systemd nor the log can confirm a terminal state. Check `journalctl --user -u maxy-action-<id>`; the unit failed early or the log was truncated.
+>
+> The server emits `[action-runner] reconcile actionId=<id> result=<succeeded|failed|restart-in-progress|unresolved> source=<systemd|persisted-log> ms=<n>` once per terminal-state resolution. Missing reconcile line on a finished run = stale platform; upgrade.
+
+**Cloudflare-setup auto-relays "completed" but the next chat turn 502s.**
+
+Pre-Task-860, `CloudflareSetupForm` dispatched the post-success chat message immediately on `exit{code:0}`. The relay POST hit the admin server inside the brand-restart bounce window (`~3 s` after `step=service-restart-armed`) and returned `Error: Request failed (502)`. Post-Task-860 the form holds the dispatch behind one successful `/api/admin/version` probe (cap 30 s); the relay only fires once admin handlers are reachable. Browser console emits `[cloudflare-setup-form] holdback=fired awaitedMs=<n>` per dispatch — non-zero `awaitedMs` is normal and expected.
+
 ---
 
 ## Software Update click shows an error instead of opening the terminal