docs: tease the Flow Mapper in the README - #22
Merged
Conversation
Adds a Flow Mapper entry under the existing "Coming soon" heading, alongside the VS Code extension, with a preview of /flow show against the built-in mock corpus. The capture shows the case the feature exists for: a checkout incident and a customer renewal linking on "incident, checkout", where neither conversation mentions the other and the QBR refers to the incident only in prose, with no ticket number to join on. The feature itself is on feat/flow-mapper; this is README-only. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Adds a Flow Mapper entry under the existing
## Coming soonheading, alongside the VS Code extension, so the README matches the structure already there rather than introducing a new banner style.What's in it
README.md— one section: what/flowdoes, the link it found, and how to read the railassets/flow_mapper_preview.png—/flow showagainst the built-in mock corpus (127 KB)README-only. The feature itself lives on
feat/flow-mapperand is not merged by this PR.About the screenshot
The capture shows the case the feature exists for — a checkout incident and a customer renewal linking on
incident, checkout, where neither conversation mentions the other and the QBR refers to the incident only in prose, with no ticket number to join on.It was rendered by running the command against the mock corpus, so it stays reproducible:
🤖 Generated with Claude Code