✨ ScoutNext: curated home feed + conversation loading; Knowledge search (SCO-062)#199
Merged
Conversation
- Home activity now reads the broker's curated home feed (named actors, accurate user/assistant roles, one row per message) instead of the raw /v1/activity lifecycle firehose; the firehose stays on the Tail tab - Resolve mobile conversation snapshots against the live broker snapshot — real c.* / dm.* conversation ids and bare agent ids all map to their actual conversation, fixing transcripts that silently wouldn't load - Conversation transcript gains loading / empty / failed states with retry, so an empty session reads as intentional instead of a black void - RECENT agents list collapses to single-line rows (project only when on a branch) - In-app comms mark-read via a broker read-cursor RPC + bridge surfaces
- Runtime knowledge module (@openscout/runtime/knowledge): QMD store, session indexer, path resolution, types + tests - Knowledge search screen + inspector slot, search-route right-panel sizing, and KnowledgeHit state on the scout Provider - Session knowledge indexing wired into the web server - SCO-062 design doc, review notes, and studio search-results study
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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.
Two independent bodies of work on this branch.
1. ScoutNext mobile + bridge (
0beb4b0f)Fixes the mobile Home feed and conversation loading, plus in-app comms surfaces.
Home activity feed — curated, not the firehose. The Home tab was reading the raw
/v1/activitylifecycle firehose (ask_opened,flight_updated,invocation_recorded…) and substring-guessing roles, which produced meaninglessothertokens, inverted attribution, and duplicate/inert rows. It now reads the broker's curated home feed (/v1/home): one row per message, named actors, accurateuser/assistantroles, every row thread-linked. The raw firehose stays where it belongs — the Tail tab. (Home is an orientation surface; it reads curated sources.)Conversations wouldn't load. A pre-existing bug: the bridge router blindly wrapped every routed id into
dm.operator.{id}, which only resolved for agents that happen to have an operator DM. Agents whose history lives in ac.…conversation (and Home-activity taps carrying realc.…ids) all 404'd withUnknown mobile session. Resolution now happens in the snapshot service against the live broker snapshot: direct hit → operator DM → most-recent participating conversation. Validated against live data across bare agent ids,c.…,dm.…, and unknown ids.Transcript states. The conversation view now has explicit loading / empty / failed (with retry) states, so an empty session reads as intentional rather than a black void.
Misc. RECENT agents list collapses to single-line rows (project shown only when on a branch); in-app comms mark-read via a broker read-cursor RPC + bridge connection surfaces.
2. Knowledge search + context index — SCO-062 (
d704f2df)@openscout/runtime/knowledge): QMD store, session indexer, path resolution, types + testsKnowledgeHitstate on the scout ProviderValidation
other, no duplicates).tscnoise in the web package is unrelated).Note on commit structure
These two features were committed separately, but the ScoutNext changes had to be one commit: the session's fixes were interleaved line-by-line with pre-existing uncommitted ScoutNext-surface work (comms mark-read, activity-row tap affordance) inside the same hunks of shared files, so a finer split wasn't cleanly possible.