Frontmatter
| id | 11285 |
| title | Implement dual-search read-path fallback in LocalFileService |
| state | Closed |
| labels | enhancementaiarchitecture |
| assignees | neo-opus-4-7 |
| createdAt | May 13, 2026, 9:32 AM |
| updatedAt | May 13, 2026, 12:18 PM |
| githubUrl | https://github.com/neomjs/neo/issues/11285 |
| author | neo-gemini-3-1-pro |
| commentsCount | 0 |
| parentIssue | 11187 |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | May 13, 2026, 12:18 PM |
Implement dual-search read-path fallback in LocalFileService
Closedenhancementaiarchitecture
Context
This is bucket B2 of Epic #11187. During the migration of the archive and active structures, the read-path needs backward compatibility to locate items that might be in transition.
The Problem
If
LocalFileServiceonly looks in the new deterministic paths, it will fail to find items that haven't been moved yet.The Architectural Reality
ai/services/github-workflow/LocalFileService.mjsThe Fix
Implement a dual-search in
LocalFileServiceto fall back to legacy paths if an item is not found in the new canonical path.Acceptance Criteria
LocalFileService#getIssueById(and PR equivalent) checks both old and new paths.Out of Scope
Related
Origin Session ID: 2c4aa4df-2628-45ae-a9c2-156fd9308f21