You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/session-log.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -385,4 +385,5 @@
385
385
- 2026-04-08: Updated `.agents/workflow.md` so chat ownership is now a constant repo rule. The workflow file now defines stable Engine versus Desktop/UI ownership, cross-boundary stop rules, branch and dirty-tree preflight checks, and a requirement to record the validation actually run.
386
386
- 2026-04-08: Started issue #214 renderer tab binding registry hardening. This slice is limited to `desktop/renderer/app.js` plus `.agents` continuity, and replaces the long `bindTabContentEvents` conditional chain with a local handler registry without changing renderer behavior.
387
387
- 2026-04-08: Completed issue #214 renderer tab binding registry hardening. `bindTabContentEvents` now dispatches through a local `TAB_CONTENT_EVENT_BINDERS` registry in `desktop/renderer/app.js`, and `npm run smoke` still passes via local runs fallback.
388
+
- 2026-04-10: Started issue #346 to harden `desktop-smoke` result persistence after CI repeatedly failed with raw `ENOENT` on missing `result.json` in a planning-only PR. The slice is limited to `desktop/main.js`, `desktop/scripts/smoke.js`, and `.agents` continuity so smoke emits structured failures instead of crashing when Electron exits too early.
388
389
- 2026-04-10: Added the desktop layout regression remediation block after reviewing the post-merge desktop state in real screenshots. Opened issues #342, #343, and #344 to target empty-pane collapse, stronger active-surface focus and context containment, and better runs-family density plus right-rail space budgeting without reopening core or `research_ui` scope.
# Issue #346 — Desktop smoke result persistence in CI
2
+
3
+
## Goal
4
+
Prevent `desktop-smoke` from failing with a raw missing-file error before the smoke harness can read or emit a structured result.
5
+
6
+
---
7
+
8
+
## Why this matters
9
+
Planning-only Desktop/UI PRs are being blocked by a smoke harness failure that occurs before `result.json` exists. The harness needs a reliable failure path even when Electron exits before the normal smoke callback completes.
10
+
11
+
---
12
+
13
+
## Scope
14
+
15
+
### In scope
16
+
- smoke result persistence
17
+
- early-exit and renderer-failure handling for smoke runs
18
+
- minimal harness hardening in `desktop/scripts/smoke.js`
19
+
20
+
### Out of scope
21
+
- renderer UI changes
22
+
-`research_ui` changes
23
+
- core, broker, CLI, or CI workflow edits
24
+
25
+
---
26
+
27
+
## Relevant files
28
+
29
+
-`desktop/main.js`
30
+
-`desktop/scripts/smoke.js`
31
+
32
+
---
33
+
34
+
## Expected deliverable
35
+
36
+
A smoke harness that always produces a structured result or a clear structured failure message instead of crashing with `ENOENT` on missing `result.json`.
37
+
38
+
---
39
+
40
+
## Done when
41
+
42
+
- CI no longer fails with raw `ENOENT` for missing smoke output
43
+
- smoke runs persist a result even when Electron exits too early
44
+
- local smoke validation still passes for normal fallback and real-path cases
0 commit comments