grid, daemon, docs: take the XTVERSION and DA3 identity from the host #194

Merged

natsukium merged 1 commit from grid/host-identity into main 2026-10-19 19:50:31 +09:00

Conversation 0 Commits 1 Files changed 11 +243 -22

natsukium commented 2026-10-19 19:40:01 +09:00

Owner

Copy link

Part of #160 (policy amendment: XTVERSION / DA3 identity).

felis-grid answered XTVERSION with felis and its own crate version, and DA3 with the unit ID felis-1. With the library crates on independent versions, the felis app would report the grid's version, and an embedder of felis-grid would answer as felis.

• felis-grid: ReplyIdentity (printable ASCII only, so it cannot break the DCS frame) set through Grid::set_reply_identity. With an identity, XTVERSION replies DCS > | <xtversion> ST and DA3 the hex of the unit ID; without one, XTVERSION is unanswered and DA3 replies xterm's 00000000. Kept across RIS, not dumped.
• felis-daemon: stamps felis <app version> / felis-1 in ParseCore::new and on grids restored by an in-place upgrade, so a carried session names the daemon it now runs under. The replies felis sends are unchanged.
• The protocol coverage matrix and the vttest smoke set the identity explicitly.
• docs/reference/protocols/vt-compliance.md "Reporting and queries".

Tests: grid unit tests for both identity states, RIS and the ASCII check; daemon tests for a spawned grid, a restored grid that carried a stale identity, and the dump omitting the identity. Each daemon test fails with its stamp removed.

Part of #160 (policy amendment: XTVERSION / DA3 identity). felis-grid answered XTVERSION with `felis` and its own crate version, and DA3 with the unit ID `felis-1`. With the library crates on independent versions, the felis app would report the grid's version, and an embedder of felis-grid would answer as felis. - felis-grid: `ReplyIdentity` (printable ASCII only, so it cannot break the DCS frame) set through `Grid::set_reply_identity`. With an identity, XTVERSION replies `DCS > | <xtversion> ST` and DA3 the hex of the unit ID; without one, XTVERSION is unanswered and DA3 replies xterm's `00000000`. Kept across RIS, not dumped. - felis-daemon: stamps `felis <app version>` / `felis-1` in `ParseCore::new` and on grids restored by an in-place upgrade, so a carried session names the daemon it now runs under. The replies felis sends are unchanged. - The protocol coverage matrix and the vttest smoke set the identity explicitly. - `docs/reference/protocols/vt-compliance.md` "Reporting and queries". Tests: grid unit tests for both identity states, RIS and the ASCII check; daemon tests for a spawned grid, a restored grid that carried a stale identity, and the dump omitting the identity. Each daemon test fails with its stamp removed.

natsukium added 1 commit 2026-10-19 19:40:01 +09:00

grid, daemon, docs: take the XTVERSION and DA3 identity from the host ... 9b6ac08219

felis-grid answered XTVERSION with `felis` and its own crate version,
and DA3 with the unit ID `felis-1`. Once the library crates carry
versions independent of the app, the felis app would name the grid's
version, and an embedder of felis-grid would answer as felis. The
identity is the host's, so the grid now formats the replies from a
ReplyIdentity the host sets, and stays anonymous without one.

The daemon stamps its own identity on every grid it builds, restored
ones included; the identity is left out of the upgrade dump so a
carried session names the daemon it now runs under.

Assisted-by: Claude Code

natsukium merged commit 6ca3e144de into main 2026-10-19 19:50:31 +09:00

natsukium deleted branch grid/host-identity 2026-10-19 19:50:31 +09:00

natsukium referenced this pull request from a commit 2026-10-19 19:50:31 +09:00

Merge pull request 'grid, daemon, docs: take the XTVERSION and DA3 identity from the host' (#194) from grid/host-identity into main

natsukium referenced this pull request 2026-10-20 09:21:11 +09:00

changelog: record the crates.io publish and the host-supplied reply identity #202

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

Area/ci

CI workflows (.forgejo/workflows/)

  

Area/cli

felis-cli crate, the felis front-door binary

  

Area/client

felis-client crate, the winit GUI frontend

  

Area/client-core

felis-client-core crate, shadow screen, config, connect_or_spawn_daemon

  

Area/daemon

felis-daemon crate, session pool, IPC server

  

Area/deps

Dependency bumps

  

Area/docs

Documentation tree when no narrower area fits

  

Area/grid

felis-grid crate, cells, scrollback, image store

  

Area/manual

User-facing docs: tutorials, how-to, user-facing reference pages

  

Area/nix

Nix flake, home-manager module, package definitions

  

Area/protocol

felis-protocol crate, felis.proto, frame layout, version constants

  

Area/pty

felis-pty crate, PTY backends

  

Area/render

felis-render-wgpu crate, GPU pipeline, atlas

  

Area/shaping

felis-shaping crate, swash shaper, font fallback

  

Area/skills

Agent skills (skills/felis, .agents/skills/)

  

Area/transport

felis-transport crate, framing, socket/pipe, SSH carrier

  

Area/vt

felis-vt crate, VT parser, dispatch

  

Compat/Breaking

Breaking change that won't be backward compatible

  

Kind/Bug

Something is not working

  

Kind/Documentation

Documentation changes

  

Kind/Enhancement

Improve existing functionality

  

Kind/Feature

New functionality

  

Kind/Performance

Throughput, latency, or memory cost

  

Kind/Security

This is security issue

  

Kind/Testing

Issue or pull request related to testing

  

perf-regression-accepted

Passes the instruction-count bench gate for an intended cost; state why in a PR comment

  

Reviewed

Confirmed

Issue has been confirmed

  

Reviewed

Duplicate

This issue or pull request already exists

  

Reviewed

Invalid

Invalid issue

  

Reviewed

Won't Fix

This issue won't be fixed

  

Status

Blocked

Something is blocking this issue or pull request

  

Status

Need More Info

Feedback is required to reproduce issue or to continue work

  

Status

Upstream

Waiting on a change in an upstream project

No labels

Area/ci

Area/cli

Area/client

Area/client-core

Area/daemon

Area/deps

Area/docs

Area/grid

Area/manual

Area/nix

Area/protocol

Area/pty

Area/render

Area/shaping

Area/skills

Area/transport

Area/vt

Compat/Breaking

Kind/Bug

Kind/Documentation

Kind/Enhancement

Kind/Feature

Kind/Performance

Kind/Security

Kind/Testing

perf-regression-accepted

Reviewed

Confirmed

Reviewed

Duplicate

Reviewed

Invalid

Reviewed

Won't Fix

Status

Blocked

Status

Need More Info

Status

Upstream

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

felis-terminal/felis!194

No description provided.