From 696ba4d3e7611db24ac46ad0c8235c36c4d1a5af Mon Sep 17 00:00:00 2001 From: Rostislav Rotaru Date: Fri, 13 Nov 2026 17:31:12 -0800 Subject: [PATCH 1/2] Allow a blocking call before an Electron app is ready Agent: LEAD (lead) Agent-Model: Anthropic Opus 5.5, High --- standards/CODE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/CODE.md b/standards/CODE.md index 6dc0bfc..b9de156 100644 --- a/standards/CODE.md +++ b/standards/CODE.md @@ -132,7 +132,7 @@ Code that no input can reach is removed, not covered: needing a deliberately bro ## Asynchronous work and processes -- Use the asynchronous API for file, network and process work wherever one exists; a blocking call is allowed only in a short-lived command-line process. +- Use the asynchronous API for file, network and process work wherever one exists; a blocking call is allowed only in a short-lived command-line process, or before an Electron app is ready for what its before-ready calls depend on. - Every asynchronous operation has an owner that observes its completion and errors. Background work has an explicit lifetime and failure path; no unobserved rejections or callback failures. - Operations that can stall have documented deadlines and cancellation. From d821afd5c8bc1cce49f309e1b2c5356c06498773 Mon Sep 17 00:00:00 2001 From: Rostislav Rotaru Date: Fri, 13 Nov 2026 17:32:20 -0800 Subject: [PATCH 2/2] Limit the before-ready exception to what Electron's before-ready calls depend on Agent: LEAD (lead) Agent-Model: Anthropic Opus 5.5, High --- standards/CODE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/CODE.md b/standards/CODE.md index b9de156..185e2d4 100644 --- a/standards/CODE.md +++ b/standards/CODE.md @@ -132,7 +132,7 @@ Code that no input can reach is removed, not covered: needing a deliberately bro ## Asynchronous work and processes -- Use the asynchronous API for file, network and process work wherever one exists; a blocking call is allowed only in a short-lived command-line process, or before an Electron app is ready for what its before-ready calls depend on. +- Use the asynchronous API for file, network and process work wherever one exists; a blocking call is allowed only in a short-lived command-line process, or, before an Electron app is ready, for what Electron's calls that work only before `ready` depend on, such as its profile folder and single-instance lock. - Every asynchronous operation has an owner that observes its completion and errors. Background work has an explicit lifetime and failure path; no unobserved rejections or callback failures. - Operations that can stall have documented deadlines and cancellation.