@adhdev/daemon-core 0.9.82-rc.480 → 0.9.82-rc.482

package/src/mesh/mesh-unresolved-forward-outbox.ts

@@ -65,6 +65,36 @@ function getStore(): MeshRuntimeStore | undefined {
     try { return MeshRuntimeStore.getInstance(); } catch { return undefined; }
 }
 
+// ---------------------------------------------------------------------------
+// Reconcile-nudge registry (polling-single-model §2.1 (B)).
+//
+// The spontaneous best-effort immediate push that used to run inline in
+// forwardUnresolvedDelegateEvent was removed: the durable outbox row + the
+// reconcile loop's PHASE 0 retry (acked, retry-capped) is now the ONLY delivery
+// path for an unresolved-delegate event. To keep the happy-path latency low
+// without re-introducing a spontaneous data push, the enqueue site emits a
+// data-free NUDGE: "outbox has work — run the PHASE 0 retry soon". The reconcile
+// loop registers the handler at setup; a lost/unregistered nudge is harmless —
+// the next periodic tick (default 4s) covers it, so nudge loss = bounded delay,
+// never event loss.
+//
+// A registry (rather than a direct import of the reconcile loop) keeps the
+// module graph acyclic: mesh-reconcile-loop already imports from
+// mesh-event-forwarding (via the mesh-events-coordinator barrel), so the
+// forwarding side must not import the loop back.
+// ---------------------------------------------------------------------------
+let retryNudgeHandler: (() => void) | undefined;
+
+/** Register (or clear, with undefined) the PHASE 0 retry nudge handler. */
+export function registerUnresolvedForwardRetryNudge(handler?: () => void): void {
+    retryNudgeHandler = handler;
+}
+
+/** Fire-and-forget nudge: ask the reconcile loop to run the outbox retry soon. */
+export function nudgeUnresolvedForwardRetry(): void {
+    try { retryNudgeHandler?.(); } catch { /* nudge is best-effort; the periodic tick covers */ }
+}
+
 /**
  * Durably enqueue an unresolved-delegate forward for a coordinator daemon. The
  * `forwardPayload` is the flat shape handleMeshForwardEvent reads on the coordinator.

package/src/repo-mesh-types.ts

@@ -14,7 +14,7 @@
 import type { GitRepoStatus, GitCompactSummary } from './git/git-types.js';
 import type { MeshMissionSummary, MeshMissionSlimSummary } from './mesh/mesh-missions.js';
 import type { MeshMagiActivitySummary } from './mesh/mesh-magi-status.js';
-import type { MagiPanelMap, MagiKindPanelMap } from '@adhdev/mesh-shared';
+import type { MagiKindPanelMap } from '@adhdev/mesh-shared';
 
 // ─── Core Mesh Types ────────────────────────────
 
@@ -814,18 +814,12 @@ export interface RepoMeshCoordinatorConfig {
 export interface LocalMeshConfig {
     meshes: LocalMeshEntry[];
     /**
-     * MAGI cross-verification panels (machine-local). Keyed by panel name; each
-     * binds concrete `(node × provider)` members — machine-dependent facts — so
-     * panels live here in meshes.json, never in the repo-shared .adhdev/mesh.json.
-     * Optional: absent on configs written before MAGI existed.
-     */
-    magiPanels?: MagiPanelMap;
-    /**
-     * MAGI-KIND-PANEL: per-task_kind panel bindings (machine-local). Keyed by
-     * task_kind (rca / design / claim_audit / freeform); each maps to ≥1
-     * `(node × provider × model?)` slot. A `mesh_magi_review` invoked with a bare
-     * `task_kind` resolves its panel from here — an unconfigured kind is a hard
-     * error, never a synthesized fallback. Optional; absent on pre-feature configs.
+     * MAGI-KIND-PANEL: per-task_kind panel bindings (machine-local), the SOLE MAGI
+     * panel-resolution surface (the former named-panel `magiPanels` map was removed).
+     * Keyed by task_kind (rca / design / claim_audit / freeform); each maps to ≥1
+     * `(node × provider × model?)` slot. A `mesh_magi_review` resolves its panel from
+     * here — an unconfigured kind is a hard error, never a synthesized fallback.
+     * Optional; absent on pre-feature configs.
      */
     magiKindPanels?: MagiKindPanelMap;
 }

package/src/types.ts

@@ -5,7 +5,13 @@
  * When modifying this file, also update interface contracts in AGENT_PROTOCOL.md.
  */
 import type { StatusReportPayload, AvailableProviderInfo } from './shared-types.js';
-import type { ChatMessageKind } from './providers/chat-message-normalization.js';
+import type {
+  ChatMessageKind,
+  ChatMessageVisibility,
+  ChatMessageTranscriptVisibility,
+  ChatMessageAudience,
+  ChatMessageSource,
+} from './providers/chat-message-normalization.js';
 
 // ── Daemon Status ──
 
@@ -54,11 +60,20 @@ export interface ChatMessage {
   /** Optional: fiber metadata */
   _type?: string;
   _sub?: string;
-  /** Transcript visibility/audience contract for separating chat-visible content from internal/debug runtime rows. */
-  visibility?: 'visible' | 'user' | 'chat' | 'hidden' | 'debug' | 'internal' | (string & {});
-  transcriptVisibility?: 'visible' | 'user' | 'chat' | 'hidden' | 'debug' | 'internal' | (string & {});
-  audience?: 'chat' | 'debug' | 'trace' | 'internal' | (string & {});
-  source?: 'assistant_text' | 'tool_call' | 'terminal_command' | 'runtime_activity' | 'runtime_status' | 'provider_chrome' | 'control' | (string & {});
+  /**
+   * Transcript visibility/audience contract for separating chat-visible content
+   * from internal/debug runtime rows. These reference the canonical named unions
+   * declared alongside the classifier (chat-message-normalization.ts) so the known
+   * values have one source of truth instead of a hand-inlined copy that drifts.
+   * Each alias keeps the `| (string & {})` escape hatch: the read-chat contract
+   * (read-chat-contract.ts) preserves ANY producer-supplied string verbatim, so
+   * the type must stay open — it documents the known values without forbidding
+   * provider-specific extensions.
+   */
+  visibility?: ChatMessageVisibility;
+  transcriptVisibility?: ChatMessageTranscriptVisibility;
+  audience?: ChatMessageAudience;
+  source?: ChatMessageSource;
   userFacing?: boolean;
   internal?: boolean;
   isInternal?: boolean;