Repository navigation
Description
Wire the LSP bridge into the T27 OS window: an LSP item in the status bar, a host feed job, and an "Open in editor" row that shows the editor's route to the language server. specs/t27os/lsp_bridge.t27 (#12271, the decisions) already says what to show; this issue adds the item id, its rank and click page to specs/t27os/statusbar.t27 and the draw and feed calls to specs/t27os/glass_window.t27. Part of the LSP epic, Refs #12209 (wave 5, T27 OS integration). Only .t27: no code in any other language, not even scratch probes or a loader; see skill only-t27.
glass_window.t27 has @extern imports, so t27c cannot compile it: test it with t27b test specs/t27os/glass_window.t27 and build with make t27os on the lab, never on the Mac (heavy run). tri land refuses such a branch, so it lands as a plain PR.
Depends on specs/t27os/lsp_bridge.t27 (#12271) merged on master. Edits two existing T27 OS files, so it runs alone (no other lane may hold either file).
Prior art:
- The existing status items and their feeds,
IT_SRVandIT_LANESinspecs/t27os/statusbar.t27and their draw calls inspecs/t27os/glass_window.t27. specs/t27os/lanes_view.t27: one shell job every N seconds writes a file under~/.t27os/, the window reads it, all parsing is in the spec.
Boundary
- specs/t27os/statusbar.t27
- specs/t27os/glass_window.t27
User Scenarios
- Given the language server is running, when the window draws the status bar, then an item
LSP READY 3E 2Wappears between the lanes item and the Queen item, from the feed line; with no server the item is absent. - Given the window is too narrow, when items fold, then the LSP item folds before the lanes item and after the clock (rank given in
item_rank), and the fold tooltip lists its text. - Given the user clicks the LSP item, when the page opens, then it shows the server state, the counts and the last message, with a button that restarts the service.
- Given the user opens a project in an editor from the editor list, when the editor row is drawn, then the row shows the bridge's route word (
config,extensionorparked). - Given the statusbar tests, when
t27b testruns, then the existing tests still pass and the new item has its own tests (rank, page, fold).
Requirements
- FR-001:
statusbar.t27MUST gainIT_LSPwith a rank and a click page, andIT_COUNTand the fold bookkeeping MUST stay consistent (every existing statusbar test passes unchanged except the ones that assert the count). - FR-002:
glass_window.t27MUST read the feed file written by one host job every few seconds and pass the line to the bridge; it MUST NOT parse the line itself. - FR-003: The host job's command line MUST be data in the bridge (used), not a literal in the window.
- FR-004: Drawing MUST use the bridge's text and route words only; no colors or glyphs decided in the bridge.
- FR-005: No new
@externbeyond the ones the window already imports; if one is needed, it is listed in the issue before the change.
Success Criteria
t27b test specs/t27os/statusbar.t27andt27b test specs/t27os/glass_window.t27pass on the lab, with at least 6 new tests for the LSP item; the command and the totals are pasted in the issue.make t27osbuilds on the lab and a screenshot of the status bar with the LSP item is attached to the PR.git diff --name-only masterlists onlyspecs/t27os/statusbar.t27andspecs/t27os/glass_window.t27(0 hand-written files in other languages).
Activity
gHashTag commentedon Nov 17, 2026
Referenced specs exist: specs/t27os/statusbar.t27 and specs/t27os/glass_window.t27.