fix: walkthrough frontmatter + clarify identity requirements for chat#130
Merged
Conversation
Jay2113
approved these changes
May 19, 2026
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.
Changes
Walkthrough frontmatter — adds
name+descriptiontoecs-incident-walkthrough.mdso Kiro can keyword-match and auto-load it (per steering docs).Identity resolution clarity — removes misleading suggestions that
SendMessageworks on investigation executionIds or without identity resolution:Why
The walkthrough needs
name/descriptionfor Kiro's auto-inclusion to keyword-match it (follow-up from PR #127 review).The identity docs sent users down a rabbit hole — both
CreateChatandSendMessagerequire identity resolution. If one fails, the other will too. Investigations (create-backlog-task+list-journal-records) are the correct fallback since they don't require user identity.