forked from BasedHardware/omi
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathtask-thread.yaml
More file actions
34 lines (32 loc) · 1.93 KB
/
Copy pathtask-thread.yaml
File metadata and controls
34 lines (32 loc) · 1.93 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
version: 2
name: task-thread
tier: manual
description: "Existing scenario-13 task-thread continuity proof, including the mounted task chat panel and composer"
app: non-prod
covers:
# scenario-13-task-thread-e2e.sh opens the real TaskChatPanel for first,
# second, and resumed workstream projections and captures each mounted UI.
- desktop/macos/Desktop/Sources/MainWindow/Components/TaskChatPanel.swift
- desktop/macos/Desktop/Sources/ProactiveAssistants/Assistants/TaskAgent/TaskChatState.swift
# The panel the scenario opens is driven by TaskChatCoordinator: it resolves
# the workstream, mounts the thread, and sends into it. The first/second/
# resumed projections above are its behaviour.
- desktop/macos/Desktop/Sources/ProactiveAssistants/Assistants/TaskAgent/TaskChatCoordinator.swift
# The sends above reach the kernel through TaskChatRuntime.query, which grounds
# each user turn in the current time (SCA-358 datetime injector).
- desktop/macos/Desktop/Sources/ProactiveAssistants/Assistants/TaskAgent/TaskChatRuntime.swift
preconditions:
- named_non_production_bundle_ui_lane
- task_thread_scenario_13_fixture_available
steps:
- id: S1
name: Run the task-backed thread continuity proof
do: "Run `cd desktop/macos && OMI_APP_NAME=omi-task-thread-e2e bash scripts/scenario-13-task-thread-e2e.sh` against the named non-production bundle. Verify the script's jq assertions pass for the first task, resumed second task, shared workstream/kernel session, v2 cited artifact, and dispatch-required external-send decision."
expect:
text_visible:
- Continue this work...
- id: S2
name: Verify captured task chat panels remain mounted
do: "Inspect the first-task.png, second-task.png, and resumed-task.png evidence written by the script. Each capture must show the task-scoped chat header and the 'Continue this work...' composer, with no route or bridge failure."
expect:
interactive_count: { min: 1 }