Skip to content

feat(ipc): ipcRenderer.invoke / ipcMain.handle facade with Electron error text (Zettlr) #547

Description

@0monish

Generated by an AI agent (Claude Code) on behalf of @0monish during Wayfinder charting of the Electron compatibility program; rewritten 2026-10-07 by the doctrine-audit repair pass (change log at the end). Planning only — no implementation is authorized by this issue.

Parent

Epic #463 · Map #391 · Unit F04 · Kind: feature · Tier: Tier 1 · Maturity target: L2 · Size: M · Milestone: next

What 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 at Status: approved.

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 controls (each names the one mutation that must fail)

  • Collapsing handler errors to a generic message makes the handler-throw entry fail

Ownership and gates

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)

Activity

  1. added theissue type on Oct 6, 2026
  2. added
    enhancementNew feature or request
    compat:tier-1Electron compat Tier 1 (arch 04 §4)
    ready-for-agentFully specified; an AFK agent can take it
    needs-specNeeds an approved docs/agents/spec-template.md spec before implementation
    milestone:nextNeeded after the first proof (Zettlr or strict profile)
    on Oct 6, 2026
  3. 0monish commented on Oct 6, 2026

    @0monish
    MemberAuthor

    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.md as a PR, stopped for human approval; implement only after Status: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    compat:tier-1Electron compat Tier 1 (arch 04 §4)electron-compatElectron compatibility program areaenhancementNew feature or requestmilestone:nextNeeded after the first proof (Zettlr or strict profile)needs-specNeeds an approved docs/agents/spec-template.md spec before implementationready-for-agentFully specified; an AFK agent can take it

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions