Repository navigation
feat(ioa): support application graph entities and relations - #28
Merged
Merged
Conversation
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.
IOA graphs currently show only message references, so applications cannot display task/session relationships alongside the messages that produced them. Add an optional GraphExtension with application-owned nodes and labeled edges, while retaining refs.messages links and message selection. Entity nodes remain nonselectable unless they identify a message.
Center selected messages at readable zoom and recenter on container resize; keep the full-graph overview available for larger histories.
Validation in the cyber-harness consumer: TypeScript compilation, 56 UI regression tests, five graph scenarios (restart separation, cross-node identity, retries/late arrival and invalid metadata), and real Hub desktop/mobile checks using recorded live-model IOA histories.
Consumed by chainreactors/cyber-harness#193. Application metadata parsing and protocol rules remain in that consumer.