Converge Alacritty branded director terminals on native hosts #639

New issue

Closed

opened 2026-07-24 22:01:57 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-24 22:01:57 +00:00

Owner

Outcome

Install and converge the branded Alacritty director surface on the native Windows and macOS hosts that launch Ward directors.

The launcher contract landed in agentic-os#730. Native artifact publication is tracked in agentic-os#734.

Ownership

Agentic-os owns the agent-terminal product and Alacritty argument translation. Agent-compose owns renderer-neutral identity. Infrastructure owns persistent installation, host configuration, rollout, and rollback.

Change

After agentic-os#734 publishes native artifacts, install Alacritty, agent-terminal, and a compatible agent-compose version through declared Windows and macOS convergence.
Add an idempotent director-launch entry point that starts one OS window per director and passes Ward as the child command.
Keep Alacritty opaque and single-window in the first rollout. Do not add tabs, panes, multiplexing, shell integration, or a host-global default-terminal change.
Preserve basic Warp availability during canary rollout. Retired Warp launch machinery is removed separately by agentic-os#727.
Add version checks, a dry-run canary, rollback to the prior launcher, and operator documentation.
Update infrastructure docs/FEATURES.md when the capability ships.

Acceptance

Declared Windows and macOS director hosts discover Alacritty, agent-compose, and agent-terminal from a clean login environment.
Convergence is idempotent and carries no host-absolute paths in the authored role.
A dry-run resolves the canonical director identity and a live canary opens one branded Alacritty window with Ward as its child.
The canary preserves readable colors, the stable identity and task title, working directory, and child exit behavior.
No Warp tab, Alacritty tab, or multiplexer dependency is introduced.
Rollback restores the previous director launch entry point without removing Ward or agent-compose.
Infrastructure validation and pre-commit pass.

Live verification wall

A director or ops run must perform the live Windows and macOS canaries. The sealed engineer cannot claim window launch or host convergence from repository evidence alone. This issue should carry the interactive label until those canaries pass.

## Outcome Install and converge the branded Alacritty director surface on the native Windows and macOS hosts that launch Ward directors. The launcher contract landed in [agentic-os#730](https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/730). Native artifact publication is tracked in [agentic-os#734](https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/734). ## Ownership Agentic-os owns the `agent-terminal` product and Alacritty argument translation. Agent-compose owns renderer-neutral identity. Infrastructure owns persistent installation, host configuration, rollout, and rollback. ## Change * After agentic-os#734 publishes native artifacts, install Alacritty, `agent-terminal`, and a compatible agent-compose version through declared Windows and macOS convergence. * Add an idempotent director-launch entry point that starts one OS window per director and passes Ward as the child command. * Keep Alacritty opaque and single-window in the first rollout. Do not add tabs, panes, multiplexing, shell integration, or a host-global default-terminal change. * Preserve basic Warp availability during canary rollout. Retired Warp launch machinery is removed separately by [agentic-os#727](https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/727). * Add version checks, a dry-run canary, rollback to the prior launcher, and operator documentation. * Update infrastructure `docs/FEATURES.md` when the capability ships. ## Acceptance * Declared Windows and macOS director hosts discover Alacritty, agent-compose, and `agent-terminal` from a clean login environment. * Convergence is idempotent and carries no host-absolute paths in the authored role. * A dry-run resolves the canonical director identity and a live canary opens one branded Alacritty window with Ward as its child. * The canary preserves readable colors, the stable identity and task title, working directory, and child exit behavior. * No Warp tab, Alacritty tab, or multiplexer dependency is introduced. * Rollback restores the previous director launch entry point without removing Ward or agent-compose. * Infrastructure validation and pre-commit pass. ## Live verification wall A director or ops run must perform the live Windows and macOS canaries. The sealed engineer cannot claim window launch or host convergence from repository evidence alone. This issue should carry the `interactive` label until those canaries pass.

coilyco-ops added the

autonomy

live-collab

priority

labels

2026-07-29 03:46:30 +00:00

coilyco-ops closed this issue

2026-08-05 21:22:51 +00:00