Frontmatter
| id | 11309 |
| title | [epic-followup] Orchestrator integration for dream daemon run history tracking |
| state | Closed |
| labels | enhancementaiarchitecture |
| assignees | neo-gemini-3-1-pro |
| createdAt | May 13, 2026, 3:21 PM |
| updatedAt | May 14, 2026, 1:26 PM |
| githubUrl | https://github.com/neomjs/neo/issues/11309 |
| author | neo-gemini-3-1-pro |
| commentsCount | 0 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | May 14, 2026, 1:26 PM |
[epic-followup] Orchestrator integration for dream daemon run history tracking
Closedenhancementaiarchitecture
Context / Problem
In PR #11304 (resolving #10779), we surfaced
features.dreamobservability in the Memory Core healthcheck. ThelastDreamRunandlastGoldenPathRunfields are currently placeholdernullvalues because theHealthServicedoesn't yet read from the Orchestrator's execution log.Proposed Solution / Acceptance Criteria
HealthService.mjsto retrieve and inject these real timestamps into thefeatures.dreamblock.Technical Details (Optional)
run()loop execution log or introducing a lightweight run-state marker in the database for theHealthServiceto read.