MingaEditor.Window.Content (Minga v0.1.0)

Polymorphic content reference for window panes.

A window can host any content type: a file buffer, an agent chat session, a terminal, etc. This module defines the authoritative tagged union for window content identity.

Why a tagged tuple instead of a protocol?

Window content references are stored in the window tree, serialized for tab save/restore, and pattern-matched in the render pipeline. A simple tagged tuple ({:buffer, pid}, {:agent, session_ref}) is easier to serialize, pattern-match, and debug than a protocol struct. This module handles only identity/reference polymorphism.

Content types

Tag	Reference	Editable?
`:buffer`	`pid()` (Buffer.Process)	Yes
`:agent_chat`	`:semantic`	No
`:empty`	`:semantic`	No

:empty is the zero-buffers launchpad surface (#2689): the window stays open with no backing buffer, and the frontends render the semantic launchpad frame natively. Only these tags are implemented today. Add future content types when they ship.

Summary

Types

t()

A content reference identifying what a window pane displays.

Functions

agent_chat()

Creates a semantic agent chat content reference.

agent_chat?(arg1)

Returns true if this content reference is an agent chat.

buffer(pid)

Creates a buffer content reference.

buffer?(arg1)

Returns true if this content reference is a file buffer.

buffer_pid(arg1)

Returns the buffer pid if this is a buffer content reference, nil otherwise.

editable?(arg1)

Returns true if the content is editable (supports insert mode).

empty()

Creates a semantic empty-state (launchpad) content reference.

empty?(arg1)

Returns true if this content reference is the empty-state launchpad.

pid(arg1)

Returns the underlying pid for any content type.