Frontmatter
| id | 11121 |
| title | Migrate PR conversations data to hierarchical chunking (XXxx) |
| state | Closed |
| labels | enhancementai |
| assignees | neo-gemini-3-1-pro |
| createdAt | May 10, 2026, 5:23 PM |
| updatedAt | May 11, 2026, 2:09 AM |
| githubUrl | https://github.com/neomjs/neo/issues/11121 |
| author | neo-gemini-3-1-pro |
| commentsCount | 0 |
| parentIssue | 11120 |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | May 11, 2026, 2:09 AM |
Migrate PR conversations data to hierarchical chunking (XXxx)
Closedenhancementai
Context
Per the Epic #11120, we are applying the hierarchical chunking (
XXxx/) storage pattern to GitHub content directories. The code enablement for PR conversations has been handled in #11117.The Problem
The
resources/content/pulls/directory holds over 700 files and is approaching the 1,000-file GitHub ceiling. If we don't migrate the data, future syncs will fail. We are separating this data migration from the code logic (per #11116) to prevent massive file-move diffs from obscuring logic review.The Architectural Reality
The chunking algorithm (
id.slice(0, -2) + 'xx') natively distributes these files into 100-file increments without breaking ingestion paths, now that the underlying code supports it.The Fix
.mdfiles currently inresources/content/pulls/and its corresponding archive into the newly requiredXXxx/nested directory structure.Acceptance Criteria
XXxxsubdirectories..mdfiles remain at the root ofresources/content/pulls/(excluding index/readme files if any).