Fix Kiro post-February storage discovery#339
Open
ozymandiashh wants to merge 1 commit into
Open
Conversation
5133b66 to
9bb295f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #329 by teaching the Kiro provider to discover the post-February 2026 extensionless storage layout while preserving the legacy
.chatparser.What changed
.chatfiles, top-level extensionless session index files, and one-level nested extensionless execution files under each Kiro workspace hash directory.{ executions: [...] }session index files during parsing because they do not contain conversation content.Closes #329.
Validation
npx vitest run tests/providers/kiro.test.ts tests/provider-registry.test.ts— 36/36 tests passed.npm run build— passed.git diff --check— passed.Notes
Validation uses synthetic fixture shapes matching the public issue report. I did not use or include real local Kiro history, local project names, prompts, paths, or usage details.