Repository navigation
UX — F75 workbench active state, F95, F97 proof of life on the harness card - #119
Merged
Merged
Conversation
…and the harness card (F75, F95, F97) F75 — a workbench conversation row carries its live state: the agent's turn from the session hot state and the runs the conversation waits on with their phase, through the existing useApiQuery and entity-event broker paths on the ['space', spaceId, …] keys, never a per-row fetch. F95 — the run surface's harness task shows the same live card the chat shows — last tool line, elapsed time, turns — from the step's activity stream, one component mounted in both places, not a second rendering. F97 — the harness activity card leads with the agent's last status or plain-text message and the time since its last activity, then the files it changed, with the tool lines collapsed behind a disclosure; exit codes are shown only where the harness reports them truthfully (F84 is open, so a command's non-zero exit is not shown as failure). Tests state each property: a row with a running commission renders its phase; the run surface mounts the card for a harness task carrying activity; the card's lead line is the last status or message and the tool lines are collapsed by default. Any extension of the activity event shape is in the Zod schema first and derived from there.
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.
The UX slice of Plan 315 §6 — F75, F95, F97 — so the operator sees a conversation's and a commission's state without opening each one:
useApiQueryand entity-event broker paths on the['space', spaceId, …]keys, never a per-row fetch.Tests state each property: a row with a running commission renders its phase; the run surface mounts the card for a harness task carrying activity; the card's lead line is the last status or message and the tool lines are collapsed by default. Any extension of the activity event shape is in the Zod schema first and derived from there.