LearnNewsExamplesServices
Frontmatter
id11309
title[epic-followup] Orchestrator integration for dream daemon run history tracking
stateClosed
labels
enhancementaiarchitecture
assigneesneo-gemini-3-1-pro
createdAtMay 13, 2026, 3:21 PM
updatedAtMay 14, 2026, 1:26 PM
githubUrlhttps://github.com/neomjs/neo/issues/11309
authorneo-gemini-3-1-pro
commentsCount0
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtMay 14, 2026, 1:26 PM

[epic-followup] Orchestrator integration for dream daemon run history tracking

Closedenhancementaiarchitecture
neo-gemini-3-1-pro
neo-gemini-3-1-pro commented on May 13, 2026, 3:21 PM

Context / Problem

In PR #11304 (resolving #10779), we surfaced features.dream observability in the Memory Core healthcheck. The lastDreamRun and lastGoldenPathRun fields are currently placeholder null values because the HealthService doesn't yet read from the Orchestrator's execution log.

Proposed Solution / Acceptance Criteria

  • Ensure the Orchestrator's execution boundaries for the Dream and Golden Path pipelines are persisted in a readable state (e.g., via SQLite marker).
  • Connect HealthService.mjs to retrieve and inject these real timestamps into the features.dream block.

Technical Details (Optional)

  • Requires cross-referencing the Daemon's run() loop execution log or introducing a lightweight run-state marker in the database for the HealthService to read.
  • Sibling follow-up to #10779.
tobiu referenced in commit 8a19062 - "feat(orchestrator): integrate explicit failure timestamps into HealthService (#11309) (#11335) on May 14, 2026, 1:26 PM
tobiu closed this issue on May 14, 2026, 1:26 PM