@adhdev/daemon-core 0.9.82-rc.376 → 0.9.82-rc.378

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (48) hide show
  1. package/dist/commands/chat-commands-debug-bundle.d.ts +14 -0
  2. package/dist/commands/chat-commands-read.d.ts +7 -0
  3. package/dist/commands/chat-commands-scope.d.ts +39 -0
  4. package/dist/commands/chat-commands-shared.d.ts +33 -0
  5. package/dist/commands/chat-commands-write.d.ts +14 -0
  6. package/dist/commands/chat-commands.d.ts +9 -49
  7. package/dist/commands/router.d.ts +3 -470
  8. package/dist/index.js +3166 -3115
  9. package/dist/index.js.map +1 -1
  10. package/dist/index.mjs +3561 -3510
  11. package/dist/index.mjs.map +1 -1
  12. package/dist/mesh/mesh-coordinator-config.d.ts +21 -0
  13. package/dist/mesh/mesh-event-classify.d.ts +5 -0
  14. package/dist/mesh/mesh-event-forwarding.d.ts +18 -0
  15. package/dist/mesh/mesh-events-coordinator.d.ts +4 -92
  16. package/dist/mesh/mesh-events-utils.d.ts +3 -0
  17. package/dist/mesh/mesh-ledger-reconciliation.d.ts +0 -1
  18. package/dist/mesh/mesh-node-identity.d.ts +289 -0
  19. package/dist/mesh/mesh-queue-assignment.d.ts +86 -0
  20. package/dist/mesh/mesh-refine-gates.d.ts +428 -0
  21. package/dist/mesh/mesh-runtime-store.d.ts +0 -3
  22. package/dist/providers/native-history/constants.d.ts +12 -0
  23. package/dist/runtime-defaults.d.ts +2 -0
  24. package/package.json +2 -2
  25. package/src/commands/chat-commands-debug-bundle.ts +398 -0
  26. package/src/commands/chat-commands-read.ts +2327 -0
  27. package/src/commands/chat-commands-scope.ts +54 -0
  28. package/src/commands/chat-commands-shared.ts +114 -0
  29. package/src/commands/chat-commands-write.ts +880 -0
  30. package/src/commands/chat-commands.ts +20 -3697
  31. package/src/commands/router.ts +59 -3631
  32. package/src/mesh/mesh-coordinator-config.ts +97 -0
  33. package/src/mesh/mesh-event-classify.ts +51 -0
  34. package/src/mesh/mesh-event-forwarding.ts +1502 -0
  35. package/src/mesh/mesh-events-coordinator.ts +30 -2993
  36. package/src/mesh/mesh-events-pending.ts +1 -10
  37. package/src/mesh/mesh-events-stale.ts +3 -14
  38. package/src/mesh/mesh-events-utils.ts +52 -14
  39. package/src/mesh/mesh-ledger-reconciliation.ts +0 -2
  40. package/src/mesh/mesh-node-identity.ts +1887 -0
  41. package/src/mesh/mesh-queue-assignment.ts +1457 -0
  42. package/src/mesh/mesh-refine-gates.ts +1652 -0
  43. package/src/mesh/mesh-runtime-store.ts +0 -37
  44. package/src/providers/cli-provider-instance.ts +40 -1
  45. package/src/providers/native-history/constants.ts +19 -0
  46. package/src/providers/native-history/dispatcher.ts +2 -3
  47. package/src/providers/spec/native-history-executor.ts +1 -9
  48. package/src/runtime-defaults.ts +39 -0
@@ -0,0 +1,428 @@
1
+ /**
2
+ * Mesh refine validation gates & gitlink fast-forward evaluation
3
+ *
4
+ * Extracted from commands/router.ts (behavior-preserving move). Contains:
5
+ * - the MeshCoordinator config-format type
6
+ * - refine validation / patch-equivalence / effective-diff / submodule
7
+ * reachability gates and their summary types + job handles
8
+ * - gitlink trivial-fast-forward evaluation and submodule alignment helpers
9
+ *
10
+ * router.ts re-exports every public symbol from here so existing import paths
11
+ * keep working. `CommandRouterResult` is imported type-only from router.ts
12
+ * (erased at compile time — no runtime import cycle).
13
+ */
14
+ import type { WorktreeBootstrapState } from '../mesh/worktree-bootstrap-config.js';
15
+ import type { CommandRouterResult } from '../commands/router.js';
16
+ export type MeshCoordinatorConfigFormat = 'claude_mcp_json' | 'hermes_config_yaml';
17
+ type MeshRefineValidationStatus = 'passed' | 'failed' | 'skipped';
18
+ type MeshRefineValidationSummary = {
19
+ status: MeshRefineValidationStatus;
20
+ required: true;
21
+ commandsRun: Array<Record<string, unknown>>;
22
+ bootstrapCommandsRun: Array<Record<string, unknown>>;
23
+ rejectedCommands: Array<Record<string, unknown>>;
24
+ skippedReason?: string;
25
+ failureKind?: string;
26
+ failureCode?: string;
27
+ /** Human-readable cause when failureKind === 'spawn_resolution_failed' (win32 .cmd shim, etc). */
28
+ spawnResolutionError?: string;
29
+ timeoutMs: number;
30
+ outputLimitBytes: number;
31
+ configSource?: string;
32
+ configSourceType?: string;
33
+ suggestions?: unknown[];
34
+ suggestedConfig?: unknown;
35
+ /**
36
+ * M2-3: the bootstrap stage recorded separately from validation so review
37
+ * surfaces can distinguish environment failures from validation failures.
38
+ * cached — worktree_bootstrap was 'ready' (staleInputs unchanged), skipped
39
+ * ran — worktree_bootstrap was stale/never-ran and re-ran successfully
40
+ * failed — bootstrap run failed (refine stops before validation)
41
+ * skipped — refine config validation.bootstrap === 'skip'
42
+ * legacy — deprecated validation.bootstrapCommands path was used
43
+ * not_configured — no bootstrap definition anywhere
44
+ */
45
+ bootstrap?: {
46
+ stage: 'cached' | 'ran' | 'failed' | 'skipped' | 'legacy' | 'not_configured';
47
+ status?: string;
48
+ skipped?: boolean;
49
+ configSource?: string;
50
+ staleReason?: string;
51
+ error?: string;
52
+ commandsRun?: Array<Record<string, unknown>>;
53
+ };
54
+ /** M2-2: deprecation notices from the refine config (e.g. bootstrapCommands). */
55
+ deprecationWarnings?: string[];
56
+ };
57
+ type MeshRefineStageStatus = 'passed' | 'failed' | 'skipped';
58
+ type MeshRefinePatchEquivalenceSummary = {
59
+ status: MeshRefineStageStatus;
60
+ equivalent: boolean;
61
+ baseHead: string;
62
+ branchHead: string;
63
+ mergeBase?: string;
64
+ mergedTree?: string;
65
+ expectedPatchId?: string;
66
+ actualPatchId?: string;
67
+ durationMs: number;
68
+ error?: string;
69
+ stdout?: string;
70
+ stderr?: string;
71
+ actionableHint?: MeshRefineSubmoduleConflictHint;
72
+ /**
73
+ * Set when a `merge-tree` submodule conflict was reclassified as a trivial
74
+ * gitlink fast-forward and the gate passed via a synthesized merge tree.
75
+ */
76
+ gitlinkTrivialFastForward?: {
77
+ resolved: boolean;
78
+ gitlinks: Array<{
79
+ path: string;
80
+ baseCommit?: string;
81
+ branchCommit?: string;
82
+ fastForward: boolean;
83
+ }>;
84
+ reason?: string;
85
+ };
86
+ };
87
+ type MeshRefineEffectiveDiffSummary = {
88
+ status: MeshRefineStageStatus;
89
+ /** True when there is at least one root-tree change between base and branch (incl. gitlink bumps). */
90
+ hasEffectiveDiff: boolean;
91
+ baseHead: string;
92
+ branchHead: string;
93
+ /** Root-level paths that differ between base and branch (capped). */
94
+ changedPaths?: string[];
95
+ /** Submodule paths with uncommitted/divergent commits but NO committed gitlink bump in the root tree. */
96
+ submoduleHints?: Array<{
97
+ path: string;
98
+ reason: string;
99
+ }>;
100
+ durationMs: number;
101
+ error?: string;
102
+ stdout?: string;
103
+ stderr?: string;
104
+ };
105
+ type MeshRefineSubmoduleConflictHint = {
106
+ kind: 'submodule_conflict';
107
+ message: string;
108
+ conflicts: Array<{
109
+ path: string;
110
+ baseCommit?: string;
111
+ branchCommit?: string;
112
+ }>;
113
+ nextSteps: string[];
114
+ };
115
+ type MeshRefineSubmoduleAlignmentSummary = {
116
+ status: 'passed' | 'failed' | 'skipped';
117
+ changedGitlinkPaths: string[];
118
+ outOfSyncPaths: string[];
119
+ updatedPaths: string[];
120
+ verifiedPaths: string[];
121
+ durationMs: number;
122
+ reason?: string;
123
+ command?: string;
124
+ error?: string;
125
+ stdout?: string;
126
+ stderr?: string;
127
+ };
128
+ type MeshRefineSubmoduleReachabilityEntry = {
129
+ path: string;
130
+ commit: string;
131
+ reachable: boolean;
132
+ publishRequired?: boolean;
133
+ autoPublishAllowed?: boolean;
134
+ autoPublishAttempted?: boolean;
135
+ autoPublishSucceeded?: boolean;
136
+ autoPublishVerified?: boolean;
137
+ autoPublishRefspec?: string;
138
+ autoPublishSkippedReason?: string;
139
+ importedFromWorktree?: boolean;
140
+ checkedLocal?: boolean;
141
+ localReachable?: boolean;
142
+ remote?: string;
143
+ remoteUrl?: string;
144
+ remoteReachable?: boolean;
145
+ remoteMainBranch?: string;
146
+ remoteMainReachable?: boolean;
147
+ fetchedFromOrigin?: boolean;
148
+ error?: string;
149
+ publishStdout?: string;
150
+ publishStderr?: string;
151
+ };
152
+ type MeshRefineSubmoduleReachabilitySummary = {
153
+ status: MeshRefineStageStatus;
154
+ checked: number;
155
+ unreachable: MeshRefineSubmoduleReachabilityEntry[];
156
+ entries: MeshRefineSubmoduleReachabilityEntry[];
157
+ durationMs: number;
158
+ autoPublishAllowed?: boolean;
159
+ autoPublishPolicySource?: string;
160
+ error?: string;
161
+ };
162
+ export type MeshRefineAsyncJobStatus = 'accepted' | 'completed' | 'failed';
163
+ export type MeshRefineJobHandle = {
164
+ success: true;
165
+ async: true;
166
+ status: MeshRefineAsyncJobStatus;
167
+ jobId: string;
168
+ interactionId: string;
169
+ meshId: string;
170
+ nodeId: string;
171
+ targetNodeId: string;
172
+ targetDaemonId?: string;
173
+ workspace?: string;
174
+ startedAt: string;
175
+ completedAt?: string;
176
+ duplicate?: boolean;
177
+ retryOfJobId?: string;
178
+ /**
179
+ * The coordinator daemon ID that initiated this refine job.
180
+ * When set, events for this job are scoped to that coordinator's
181
+ * pending-events queue instead of the shared broadcast queue.
182
+ */
183
+ targetCoordinatorDaemonId?: string;
184
+ eventDelivery: {
185
+ pendingEvents: true;
186
+ ledger: true;
187
+ };
188
+ evidence: {
189
+ pendingEventsCommand: 'get_pending_mesh_events';
190
+ ledgerCommand: 'get_mesh_ledger_slice';
191
+ taskHistoryKind: 'task_dispatched' | 'task_completed' | 'task_failed';
192
+ };
193
+ };
194
+ export type MeshRefineTerminalJob = MeshRefineJobHandle & {
195
+ result?: Record<string, unknown>;
196
+ };
197
+ export type MeshRefineBatchJobStatus = 'accepted' | 'completed' | 'failed';
198
+ /**
199
+ * Async handle returned by the batch Refinery the instant a convergence run is
200
+ * accepted. Mirrors {@link MeshRefineJobHandle} (async:true / status:'accepted' +
201
+ * terminal pending-event + ledger delivery) but scopes a whole batch of sibling
202
+ * nodes rather than a single node. The synthetic `batchLabel` is used as the
203
+ * `nodeLabel` for the shared refine event/message renderer.
204
+ */
205
+ export type MeshRefineBatchJobHandle = {
206
+ success: true;
207
+ async: true;
208
+ batch: true;
209
+ status: MeshRefineBatchJobStatus;
210
+ jobId: string;
211
+ interactionId: string;
212
+ meshId: string;
213
+ batchLabel: string;
214
+ nodeIds: string[];
215
+ nodeCount: number;
216
+ order: string[];
217
+ startedAt: string;
218
+ completedAt?: string;
219
+ duplicate?: boolean;
220
+ targetCoordinatorDaemonId?: string;
221
+ eventDelivery: {
222
+ pendingEvents: true;
223
+ ledger: true;
224
+ };
225
+ evidence: {
226
+ pendingEventsCommand: 'get_pending_mesh_events';
227
+ ledgerCommand: 'get_mesh_ledger_slice';
228
+ taskHistoryKind: 'task_dispatched' | 'task_completed' | 'task_failed';
229
+ };
230
+ };
231
+ export type MeshRefineBatchTerminalJob = MeshRefineBatchJobHandle & {
232
+ result?: Record<string, unknown>;
233
+ };
234
+ export declare function truncateValidationOutput(value: unknown): string;
235
+ /**
236
+ * A spawn-resolution failure is when the executable itself could not be found by
237
+ * the OS spawn boundary — `spawn <cmd> ENOENT` — as opposed to the command
238
+ * running and exiting non-zero. On win32 this is the .cmd-shim case: libuv's
239
+ * spawn search appends only .com/.exe, so a bare `npm`/`npx`/`tsc` (which are
240
+ * .cmd shims) ENOENTs even though it is installed. It carries no stderr, so it
241
+ * must be detected by error.code/syscall, not by string-matching output.
242
+ */
243
+ export declare function isSpawnResolutionError(error: any): boolean;
244
+ export declare function describeSpawnError(error: any, command: string, spawnResolutionFailed: boolean): string;
245
+ export declare function recordMeshRefineStage(stages: Array<Record<string, unknown>>, stage: string, status: MeshRefineStageStatus, startedAt: number, details?: Record<string, unknown>): void;
246
+ export declare function buildSubmodulePublishRequiredNextStep(entries: MeshRefineSubmoduleReachabilityEntry[]): string;
247
+ /**
248
+ * Async git exec helper used across the synchronous-refine stage pipeline. Bound
249
+ * once in the orchestrator and threaded through RefineContext so every stage runs
250
+ * git the same way (execFile + promisify, utf8). Returns the child's stdout/stderr.
251
+ */
252
+ export type RefineExecFileAsync = (file: string, args: string[], options: {
253
+ cwd: string;
254
+ encoding: 'utf8';
255
+ }) => Promise<{
256
+ stdout: string;
257
+ stderr: string;
258
+ }>;
259
+ /**
260
+ * Accumulated state shared by the synchronous-refine stages. The orchestrator
261
+ * (executeMeshRefineNodeSynchronously) seeds this in the resolve_refs stage and
262
+ * each later stage reads / extends it. `branchHead` and `patchEquivalence` are the
263
+ * only fields a stage mutates after creation (auto-rebase updates both), so they
264
+ * are carried on the mutable context rather than re-threaded through return types.
265
+ */
266
+ export interface RefineContext {
267
+ meshId: string;
268
+ nodeId: string;
269
+ args: any;
270
+ refineStages: Array<Record<string, unknown>>;
271
+ execFileAsync: RefineExecFileAsync;
272
+ mesh: any;
273
+ node: any;
274
+ sourceNode: any;
275
+ repoRoot: string;
276
+ branch: string;
277
+ baseBranch: string;
278
+ baseHead: string;
279
+ branchHead: string;
280
+ validationSummary: Awaited<ReturnType<typeof runMeshRefineValidationGate>>;
281
+ patchEquivalence: Awaited<ReturnType<typeof runMeshRefinePatchEquivalenceGate>>;
282
+ submoduleReachability: Awaited<ReturnType<typeof runMeshRefineSubmoduleReachabilityGate>>;
283
+ }
284
+ /**
285
+ * Stage outcome for the synchronous-refine pipeline. A stage either produces a
286
+ * terminal CommandRouterResult (an early-exit gate failure, or a successful
287
+ * already-merged short-circuit), in which case the orchestrator returns it
288
+ * immediately, or it returns `continue` with the (possibly extended) context for
289
+ * the next stage. This makes the orchestrator a flat sequence of stage calls
290
+ * while preserving the original body's exact early-return control flow.
291
+ */
292
+ export type RefineStageOutcome = {
293
+ kind: 'terminal';
294
+ result: CommandRouterResult;
295
+ } | {
296
+ kind: 'continue';
297
+ ctx: RefineContext;
298
+ };
299
+ export declare function resolveRefineryAutoPublishSubmoduleMainCommits(mesh: any, workspace: string): {
300
+ enabled: boolean;
301
+ source?: string;
302
+ };
303
+ export declare function runMeshRefinePatchEquivalenceGate(repoRoot: string, baseHead: string, branchHead: string): Promise<MeshRefinePatchEquivalenceSummary>;
304
+ export type MeshWorktreePatchContainmentSummary = {
305
+ /** True only when merging worktreeHead into ref introduces no new patch. */
306
+ contained: boolean;
307
+ ref: string;
308
+ worktreeHead: string;
309
+ mergeBase?: string;
310
+ mergedTree?: string;
311
+ /** patch-id of (ref -> synthesized merge tree); empty string when nothing new is added. */
312
+ residualPatchId?: string;
313
+ durationMs: number;
314
+ /** Set when the check could not run (treated conservatively as NOT contained). */
315
+ error?: string;
316
+ };
317
+ /**
318
+ * Patch-equivalence containment check for the worktree force-cleanup convergence
319
+ * guard. Answers a narrower question than {@link runMeshRefinePatchEquivalenceGate}:
320
+ * "are the worktree branch's changes ALREADY present in `ref` (e.g. origin/main),
321
+ * even though the worktree HEAD's commit SHA is not an ancestor of ref?"
322
+ *
323
+ * This is the cherry-pick / squash / rebase case: the same content landed on the
324
+ * default ref under a different commit SHA, so `merge-base --is-ancestor` (the
325
+ * primary cleanup guard) reports the worktree as un-converged and refuses to
326
+ * remove it. Refinery already accepts patch-equivalent landings via merge-tree +
327
+ * patch-id; this brings the same notion of "convergence" to the cleanup guard.
328
+ *
329
+ * Mechanism: synthesize the merge of `worktreeHead` into `ref` (reusing the same
330
+ * trivial-gitlink-fast-forward handling as the refine gate) and compute the
331
+ * patch-id of (ref -> mergedTree). If that residual diff is EMPTY, merging the
332
+ * worktree adds nothing new on top of ref — its changes are already present there
333
+ * and the worktree is safe to remove. A non-empty residual means the worktree
334
+ * still carries content not in ref, so it is NOT contained and must stay blocked.
335
+ *
336
+ * Conservative by construction: any merge-tree / patch-id failure, a genuine
337
+ * (non-trivial) submodule conflict, or any thrown error yields `contained: false`
338
+ * so an exception can never widen the cleanup allow-list.
339
+ */
340
+ export declare function checkWorktreeChangesPatchEquivalentInRef(repoRoot: string, ref: string, worktreeHead: string): Promise<MeshWorktreePatchContainmentSummary>;
341
+ /**
342
+ * No-op guard: detect a "silent no-op" merge before the Refinery merge runs.
343
+ *
344
+ * A silent no-op occurs when the refine target branch's ROOT tree is byte-identical
345
+ * to the merge base (origin/main). This is the trap where a submodule (e.g. oss) has
346
+ * real commits but the root branch never committed the gitlink (oss-pointer) bump, so
347
+ * the root diff Refinery would merge is empty. Merging that produces a merge commit with
348
+ * no content change — reported as "success" while the actual work never reaches main.
349
+ *
350
+ * A committed gitlink bump (the legitimate oss-pointer bump) DOES show up in the root
351
+ * tree diff (as a 160000-mode entry), so this guard does NOT block legitimate refines —
352
+ * it only fires when the root tree diff vs base is COMPLETELY empty.
353
+ *
354
+ * Runs after the patch-equivalence gate; the "already merged via other path" case
355
+ * (branch has real changes already present in base) is handled upstream and never
356
+ * reaches here, so an empty root diff at this point is genuinely a no-op.
357
+ */
358
+ export declare function runMeshRefineEffectiveDiffGate(repoRoot: string, baseHead: string, branchHead: string): Promise<MeshRefineEffectiveDiffSummary>;
359
+ /**
360
+ * Result of evaluating whether a `git merge-tree --write-tree` submodule
361
+ * conflict is in fact a trivial gitlink fast-forward that should pass the
362
+ * patch-equivalence gate.
363
+ *
364
+ * `git merge-tree` (and `git merge` with the default recursive strategy)
365
+ * refuses to 3-way merge gitlinks unless the case is "trivial" — and it
366
+ * treats *any* gitlink that differs across merge-base/base/branch as
367
+ * non-trivial, even when the branch-side commit is a strict descendant of the
368
+ * base-side commit (i.e. a real fast-forward). Refinery only ever wants to
369
+ * accept the branch's recorded gitlink, so a fast-forwardable bump is safe to
370
+ * resolve to the branch side without any conflict.
371
+ */
372
+ type GitlinkTrivialFastForwardEvaluation = {
373
+ /** True only when the merge-tree conflict is *fully* explained by trivial-ff gitlinks. */
374
+ trivial: boolean;
375
+ /** Why the evaluation declined to treat the conflict as trivial (set when trivial=false). */
376
+ reason?: string;
377
+ /** Per-path detail for the changed gitlinks that were inspected. */
378
+ gitlinks: Array<{
379
+ path: string;
380
+ baseCommit?: string;
381
+ branchCommit?: string;
382
+ fastForward: boolean;
383
+ }>;
384
+ };
385
+ /**
386
+ * Return the changed gitlink paths between base and branch whose advance is a
387
+ * strict fast-forward (the base-side commit is an ancestor of the branch-side
388
+ * commit inside that submodule's repo). These are the paths whose patch-id hunk
389
+ * may legitimately differ when base has advanced the same submodule, so they
390
+ * are safe to exclude from the patch-equivalence comparison. A non-ff (genuinely
391
+ * diverged) gitlink is deliberately excluded from this set so it still fails the
392
+ * gate.
393
+ */
394
+ export declare function collectFastForwardGitlinkPaths(repoRoot: string, baseHead: string, branchHead: string): string[];
395
+ /**
396
+ * Decide whether a merge-tree submodule conflict between base and branch is a
397
+ * trivial gitlink fast-forward (and nothing else).
398
+ *
399
+ * The conflict is treated as trivial ONLY when:
400
+ * 1. at least one changed gitlink exists,
401
+ * 2. every changed gitlink fast-forwards (base-commit is an ancestor of the
402
+ * branch-commit inside that submodule's repo), and
403
+ * 3. the *only* paths that changed on both sides of the merge (i.e. the paths
404
+ * that could possibly produce a 3-way conflict — the intersection of
405
+ * mergeBase→base and mergeBase→branch changes) are gitlinks. Any
406
+ * overlapping non-gitlink path means a genuine content conflict could be
407
+ * hiding behind the submodule failure, so we keep the block.
408
+ *
409
+ * If any of these fail, the conflict is left as a genuine block. This never
410
+ * passes a regular-file conflict or a diverged (non-ff) gitlink.
411
+ */
412
+ export declare function evaluateGitlinkTrivialFastForward(repoRoot: string, baseHead: string, branchHead: string): GitlinkTrivialFastForwardEvaluation;
413
+ export declare function alignRefinerySubmodulesAfterMerge(repoRoot: string, previousBaseHead: string, currentHead: string, options?: {
414
+ submoduleIgnorePaths?: string[];
415
+ }): Promise<MeshRefineSubmoduleAlignmentSummary>;
416
+ export declare function runMeshRefineSubmoduleReachabilityGate(repoRoot: string, mergedTree: string, options?: {
417
+ allowAutoPublishSubmoduleMainCommits?: boolean;
418
+ autoPublishPolicySource?: string;
419
+ worktreeRoot?: string;
420
+ }): Promise<MeshRefineSubmoduleReachabilitySummary>;
421
+ export declare function buildMeshRefineValidationPlan(mesh: any, workspace: string): Record<string, unknown>;
422
+ export declare function runMeshRefineValidationGate(mesh: any, workspace: string, opts?: {
423
+ /** M2-2: persisted node bootstrap state for staleness evaluation. */
424
+ persistedBootstrapState?: WorktreeBootstrapState | null;
425
+ /** M2-2: called after an inherit-mode bootstrap run so the caller can persist the new state. */
426
+ onBootstrapStateChange?: (state: WorktreeBootstrapState) => void;
427
+ }): Promise<MeshRefineValidationSummary>;
428
+ export {};
@@ -19,9 +19,6 @@ export declare class MeshRuntimeStore {
19
19
  hasCompletionFingerprint(fingerprint: string): boolean;
20
20
  recordCompletionFingerprint(fingerprint: string, ttlMs: number): void;
21
21
  sweepExpiredFingerprints(): void;
22
- recordDirectDelivered(coordinatorDaemonId: string, fingerprint: string, ttlMs: number): void;
23
- wasDirectDelivered(coordinatorDaemonId: string, fingerprint: string): boolean;
24
- sweepExpiredDirectDelivered(): void;
25
22
  private maybeCheckpointWal;
26
23
  private ensureLegacyQueueMigrated;
27
24
  getQueueEntries(meshId: string, statuses?: MeshTaskStatus[]): MeshWorkQueueEntry[];
@@ -0,0 +1,12 @@
1
+ /**
2
+ * Spawn-bind grace window: an on-disk rollout whose session_meta.timestamp
3
+ * lands within ±SPAWN_BIND_GRACE_MS of the daemon's spawnedAtMs is treated
4
+ * as belonging to that daemon session. 10s is long enough to absorb codex
5
+ * binary startup latency on cold caches and short enough that two
6
+ * back-to-back launches don't both fall inside the same window.
7
+ *
8
+ * Shared by the declarative executor (providers/spec/native-history-executor.ts)
9
+ * and the codex runtime disambiguator (providers/native-history/dispatcher.ts) —
10
+ * both apply the identical ±10s session-binding window.
11
+ */
12
+ export declare const SPAWN_BIND_GRACE_MS = 10000;
@@ -9,3 +9,5 @@ export declare const MIN_SESSION_HOST_DIAGNOSTICS_SUBSCRIPTION_INTERVAL_MS = 500
9
9
  export declare const DEFAULT_SESSION_HOST_DIAGNOSTICS_SUBSCRIPTION_INTERVAL_MS = 10000;
10
10
  export declare const DEFAULT_SESSION_HOST_READY_TIMEOUT_MS = 15000;
11
11
  export declare const STANDALONE_CDP_SCAN_INTERVAL_MS = 15000;
12
+ export declare function readMeshTimeoutEnvMs(names: string | string[], defaultMs: number): number;
13
+ export declare const MESH_CONNECT_TIMEOUT_MS: number;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@adhdev/daemon-core",
3
- "version": "0.9.82-rc.376",
3
+ "version": "0.9.82-rc.378",
4
4
  "description": "ADHDev daemon core — CDP, IDE detection, providers, command execution",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -46,7 +46,7 @@
46
46
  "author": "vilmire",
47
47
  "license": "AGPL-3.0-or-later",
48
48
  "dependencies": {
49
- "@adhdev/mesh-shared": "0.9.82-rc.376",
49
+ "@adhdev/mesh-shared": "0.9.82-rc.378",
50
50
  "@adhdev/session-host-core": "*",
51
51
  "@agentclientprotocol/sdk": "^0.16.1",
52
52
  "ajv": "^8.20.0",