-
Notifications
You must be signed in to change notification settings - Fork 1
feat: keep GNB Event Lineage focus on a linked DAG node (v2.17.0) #264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
seonghobae
merged 58 commits into
feat/ask-agent-open-focus-event-lineage-v2160
from
feat/event-lineage-node-keeps-gnb-focus-v2170
Aug 21, 2026
Merged
Changes from all commits
Commits
Show all changes
58 commits
Select commit
Hold shift + click to select a range
abcf59b
feat: keep GNB Event Lineage focus on a linked DAG node (v2.17.0)
seonghobae 9fce955
fix(ui): preserve analysis-run cutoff across DAG navigation
seonghobae eb06d6d
fix: ignore stale post detail responses
seonghobae 222262e
feat: open Ask Agent cited posts onto Event Lineage (v2.16.0)
seonghobae e9fe3d7
feat: keep GNB Event Lineage focus on a linked DAG node (v2.17.0)
seonghobae c290748
fix(ui): preserve analysis-run cutoff across DAG navigation
seonghobae 77c86e4
fix: ignore stale post detail responses
seonghobae f0c8b1e
test(red): reproduce stale Keyman drill state
seonghobae f4cac96
chore: remove red repair workflow while restacking Event Lineage PR
seonghobae 9e5a271
fix(semantics): scope organization name resolutions by context
seonghobae 6898f5d
fix(authz): scope counterparty entity resolution
seonghobae d52ae3e
fix(kg): merge catalog aliases in relationship network
seonghobae d425c28
fix(ontology): reject invalid summary actor types
seonghobae 5e17a22
fix(ask): return authorized event timeline
seonghobae 03ff920
chore: restack Event Lineage on current Ask Agent head
seonghobae bbb88cf
fix(test): apply context resolution migration to API DB
seonghobae 6b431e7
fix(ask): retain bounded global context and DOM order
seonghobae 1878eec
chore: restack Event Lineage on current Ask Agent head
seonghobae f0680f4
fix(events): register account operation mutations
seonghobae 957d883
fix(semantics): label numbered footnotes
seonghobae 557d451
fix(ask): preserve authorized lower-ranked sources
seonghobae 2962ebe
chore: restack Event Lineage on current Ask Agent head
seonghobae 163be7d
chore: restack Event Lineage on current Ask Agent head
seonghobae f4ccd3b
chore: restack Event Lineage on current Ask Agent
seonghobae 849a59e
chore: restack Event Lineage on current Ask Agent
seonghobae bd5a059
chore: reconcile remote Event Lineage restack
seonghobae 542df21
chore: restack Event Lineage on final Ask Agent
seonghobae 8df5078
chore: restack Event Lineage on final Ask Agent
seonghobae d84ee2c
chore: restack Event Lineage on final Ask Agent
seonghobae 6c4b1d5
Merge remote-tracking branch 'origin/feat/ask-agent-open-focus-event-…
seonghobae f68fe16
Merge commit 'fb92785d388d3546a80ce0b7d2bcb57c5ae15d0f' of https://gi…
seonghobae 8501381
fix: reject generic relation verification hits
seonghobae 50c8b8a
fix: align embedded image accessibility assertion
seonghobae ad8e806
merge: propagate current Ask Agent stack into Event Lineage
seonghobae 017b79d
Merge remote-tracking branch 'origin/feat/ask-agent-open-focus-event-…
seonghobae afb2e92
Merge remote-tracking branch 'origin/feat/ask-agent-open-focus-event-…
seonghobae 41558dc
test: cover current content schema and embedding agent contract
seonghobae efe1c43
Merge remote-tracking branch 'origin/feat/event-lineage-node-keeps-gn…
seonghobae 02f5afb
Merge current Ask Agent lineage base into event lineage
seonghobae ca5f793
Merge concurrent event-lineage branch updates
seonghobae 172e52e
merge: propagate current Ask Agent lineage base
seonghobae f07ceb3
fix: restore unique ADR numbering
seonghobae 2f780fe
fix: keep Valkey ADR numbering unique
seonghobae c2e31bb
merge: propagate corrected Weekly VOC lineage base
seonghobae b70e17e
merge: propagate current protected board base
seonghobae 335dd08
fix: keep Weekly VOC test option typed
seonghobae 993b693
merge: propagate current board branch head
seonghobae d5dbdf7
merge: propagate current semantic-source parent
seonghobae 0beabed
merge: restack GNB focus onto current Ask Agent base
seonghobae 3ed21fe
Merge remote-tracking branch 'origin/feat/ask-agent-open-focus-event-…
seonghobae 2ff8826
Merge remote-tracking branch 'origin/feat/ask-agent-open-focus-event-…
seonghobae d207b62
Merge remote-tracking branch 'origin/feat/ask-agent-open-focus-event-…
seonghobae bcdc459
fix: recover expired ask sessions and localize timeline
seonghobae 8832216
fix: localize event lineage post actions
seonghobae 39f2126
Merge remote-tracking branch 'origin/feat/ask-agent-open-focus-event-…
seonghobae f970b21
Merge remote-tracking branch 'origin/feat/ask-agent-open-focus-event-…
seonghobae 7ff36d4
fix: preserve semantic image and summary boundaries
seonghobae 9f24b68
fix: keep ADR numbers unique
seonghobae File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| # 2.17.0 A linked Event Lineage node keeps GNB focus | ||
|
|
||
| Opening a linked Event Lineage DAG node from a GNB-focused popup keeps | ||
| Event Lineage focused and names Keyman and evaluation next. A home-list | ||
| DAG walk does not. No TEPP theta is invented. | ||
|
|
||
| Ask Agent now replaces an expired saved session once, then stores the new | ||
| session. The Event Lineage timeline heading, list, and post-button | ||
| accessibility labels are translated in the supported locales. |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| # 2.17.0 — Preserve table image boundaries and avoid duplicate summaries | ||
|
|
||
| ## Fixed | ||
|
|
||
| - Inline or invalid images no longer split a table row or surrounding | ||
| paragraph into disconnected semantic units. | ||
| - Opening a post requests its summary once; the explicit retry action remains | ||
| the only path that requests another summary. |
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 Info: Counterparty resolution candidate set narrowed to authorized entities
fetch_post_counterparties(entity_relationship_ingestion.py) andfetch_relationship_network(entity_relationship_ingestion.py) now build theirCorporateEntityCandidatelist only fromcorporate_entityrows whose id is in the authorized-entity set, replacing the previous unconditionalselect ... from corporate_entity. This is an intentional security narrowing (covered by the newtest_counterparties_do_not_expose_unauthorized_catalog_entity), but it is also a behavioral change: a counterparty name that appears on a public post and matches a real catalog entity the caller is NOT affiliated with will now resolve tonullinstead of carrying the catalog id. That is the safer outcome (the related endpoints re-check ABAC anyway), but consumers relying on public-post names resolving to catalog ids will see fewer resolved links.(Refers to this code)
Was this helpful? React with 👍 or 👎 to provide feedback.