@adhdev/daemon-core 0.9.82-rc.494 → 0.9.82-rc.495

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adhdev/daemon-core",
-  "version": "0.9.82-rc.494",
+  "version": "0.9.82-rc.495",
   "description": "ADHDev daemon core — CDP, IDE detection, providers, command execution",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -47,8 +47,8 @@
   "author": "vilmire",
   "license": "AGPL-3.0-or-later",
   "dependencies": {
-    "@adhdev/mesh-shared": "0.9.82-rc.494",
-    "@adhdev/session-host-core": "0.9.82-rc.494",
+    "@adhdev/mesh-shared": "0.9.82-rc.495",
+    "@adhdev/session-host-core": "0.9.82-rc.495",
     "@agentclientprotocol/sdk": "^0.16.1",
     "ajv": "^8.20.0",
     "ajv-formats": "^3.0.1",

package/src/commands/router-refine.ts

@@ -89,8 +89,8 @@ export function buildRefineJobHandle(self: DaemonCommandRouter, args: {
  * The full `CommandRouterResult` (with `validationSummary.commandsRun[]` carrying
  * per-command stdout/stderr, `rejectedCommands`, `suggestions`, `suggestedConfig`,
  * the full `patchEquivalence`, and `submoduleReachability.entries[]`/`.unreachable[]`)
- * routinely exceeds 70KB and overflows the coordinator token limit when it rides on a
- * `mesh_wait_events` payload. The full detail is still persisted verbatim to the ledger
+ * routinely exceeds 70KB and overflows the coordinator token limit when surfaced as a
+ * coordinator event payload. The full detail is still persisted verbatim to the ledger
  * (`appendRefineJobLedger`) and `terminalRefineJobs`, so slimming only the EVENT loses
  * nothing — the coordinator can pull the full record on demand via
  * `evidence.ledgerCommand` / `taskHistoryKind`.

package/src/mesh/coordinator-prompt.ts

@@ -676,7 +676,6 @@ const TOOLS_SECTION = `## Available Tools
 | \`mesh_ledger_query\` | Read-only ledger query along the kind/time/node axes (complement to task-axis mesh_task_history): filter by kind, since, node, tail — answer "what happened on node X / what failed since T" without scanning transcripts |
 | \`mesh_reconcile_ledger\` | Reconcile daemon-local ledgers over P2P — import missing entries from remote nodes into the coordinator local ledger |
 | \`mesh_requeue_held_events\` | Restore recoverable held coordinator events (T6 quarantine / pending-trim) back to the pending queue; lossless, no double-requeue |
-| \`mesh_wait_events\` | Long-poll blocking wait for coordinator events (worker completions/approvals/nudges) up to timeoutMs — drains immediately if any are pending, else blocks until they arrive. Use this instead of busy-polling mesh_status/mesh_view_queue after dispatching work |
 | \`mesh_review_inbox\` | List local worktree nodes needing human review — merge candidates and Refinery-blocked results with evidence/diff summaries |
 | \`mesh_record_note\` | Record a durable, provider-neutral operating note (provider quirk / pattern to avoid / recovery lesson). Future coordinators see it under "## Operating Notes" at launch |
 | \`mesh_forget_note\` | Retract a stale/wrong operating note by note_id or exact text so it stops riding into future coordinators' prompts (append-only tombstone; history preserved) |

package/src/mesh/p2p-relay-failure.ts

@@ -29,8 +29,8 @@ export interface P2pRelayFailurePayload extends P2pRelayFailureClassification {
   targetDaemonId?: string;
 }
 
-const NO_FALLBACK_REASON = 'Repo Mesh command/data-plane is P2P-only; WS/REST command fallback is intentionally disabled to preserve the transport boundary.';
-const P2P_NEXT_ACTION = 'Check daemon/P2P health, wait briefly for connection establishment, then do one bounded retry or requeue the mesh task after clearing stale target session metadata.';
+const NO_FALLBACK_REASON = 'This mesh operation needs a live peer-to-peer connection to the node, which is not open right now. This is often transient — the peer may be connecting, slow via TURN relay, or briefly offline. Wait a moment and retry, or re-establish the node\'s connection. Mesh commands use P2P only by design — there is no cloud/WS relay fallback.';
+const P2P_NEXT_ACTION = 'The peer connection is recoverable. Wait a moment for the connection to establish (especially over TURN relay), then retry. If the node remains unreachable, check that the target daemon is running and online, then re-establish its connection.';
 const NON_P2P_NEXT_ACTION = 'Inspect the provider/command error and fix the underlying logic or configuration before retrying.';
 
 function messageFromError(error: unknown): string {