Repository navigation
feat(ipc): ipcRenderer.invoke / ipcMain.handle facade with Electron error text (Zettlr) #547
Description
Activity
- addedelectron-compatElectron compatibility program areaElectron compatibility program area
on Oct 6, 2026 - addedenhancementNew feature or requestNew feature or requestcompat:tier-1Electron compat Tier 1 (arch 04 §4)Electron compat Tier 1 (arch 04 §4)ready-for-agentFully specified; an AFK agent can take itFully specified; an AFK agent can take itneeds-specNeeds an approved docs/agents/spec-template.md spec before implementationNeeds an approved docs/agents/spec-template.md spec before implementationmilestone:nextNeeded after the first proof (Zettlr or strict profile)Needed after the first proof (Zettlr or strict profile)
on Oct 6, 2026 This was generated by AI during triage.
Agent Brief
Category: enhancement
Summary: feat(ipc): ipcRenderer.invoke / ipcMain.handle facade with Electron error text (Zettlr)Current behavior:
See the ticket body.Desired behavior:
Invoke handler registry separate from the listener registry; handle/handleOnce/removeHandler; IpcMainInvokeEvent; Electron's error renderings for duplicate handler, non-function handler, missing handler and handler throw. Needs a KEL-142 §7 amendment because the live bridge collapses handler failures to KELD-API-001 without app text.First deliverable: a spec from
docs/agents/spec-template.mdas a PR, stopped for human approval; implement only afterStatus: approved.Key interfaces:
- none named beyond the acceptance criteria
Acceptance criteria:
- A conformance entry citing the pinned Electron v44.4.5 sentence lands first for invoke round trip, handler-throw text, no-handler text, duplicate-handle throw and invoke rejection on non-cloneable args
- Zettlr mounts with its invoke/handle sites and no KELD-WV floor errors
- Negative control: Collapsing handler errors to a generic message makes the handler-throw entry fail
Out of scope:
- anything not named above
Tracker of record and claim location: see "Ownership and gates" in the issue body.
Parent
Epic #463 · Map #391 · Unit F04 · Kind:
feature· Tier: Tier 1 · Maturity target: L2 · Size: M · Milestone:nextWhat to build
Invoke handler registry separate from the listener registry; handle/handleOnce/removeHandler; IpcMainInvokeEvent; Electron's error renderings for duplicate handler, non-function handler, missing handler and handler throw. Needs a KEL-142 §7 amendment because the live bridge collapses handler failures to KELD-API-001 without app text.
Spec gate: the first deliverable is a spec from
docs/agents/spec-template.md, opened as a PR and stopped for human approval; implementation starts only atStatus: approved.Acceptance criteria
Negative controls (each names the one mutation that must fail)
Ownership and gates
docs/agents/workflow.md§ Tracker issue (rule lands with docs(agents): record the #517 tracker-of-record rule in root AGENTS.md and the workflow claim protocol #520). Linear reference: KEL-80 (Backlog) carries a link to this issue.The authoritative agent contract is the latest Agent Brief comment on this issue (triage skill); this body is the planning record.
Out of scope
none stated
Change log (doctrine-audit repair, 2026-10-07)