Track terminfo capability follow-ups

[natemoo-re]

The terminfo foundation establishes static detection, probe transport, capability events, and the Term.update() sink. Protocol-specific behavior should land as focused PRs that add the capability spec section, evidence, and gated consumer together.

In flight

• spec: add terminfo & capability layer specification #130 — terminfo & capability layer spec (stack of 4: feat: terminfo capability core (parser, detectTerminal) #131, feat: input parser probe-response recognition → CapabilityEvent #132, feat: term.update() folds CapabilityEvents into runtime capabilities #133)

Protocol follow-ups

• 💡 Color-encoding modes (16-color / 256-color) derived from terminfo #60 — Color encoding modes (16 / 256 / truecolor) derived from terminfo
• CSI 2026 synchronized output
• Pointer shape probing and output (coordinate with feat(input): OSC22 #101)
• Kitty keyboard capability and gated mode setup
• Kitty graphics capability and gated emission
• Theme probing consumers for OSC 10/11/12/21

Evidence, negotiation & infrastructure follow-ups

From https://terminfo.dev/api/v1/data.json (generated 2026-09-10):

• Terminal identity evidence: DA2, DA3, XTVERSION
• Kitty keyboard progressive flags: disambiguate, report-events, report-alternate, report-all-keys, report-text
• Kitty graphics subprotocols: transmit, display, animation, Unicode placeholders
• Input negotiation: CSI u, modifyOtherKeys, mouse modes, focus tracking, bracketed paste
• Geometry reporting: XTWINOPS 14/16/18 and OSC 1337/776 cell-size reports
• Theme and palette: OSC 4, OSC 17/19, OSC 104, OSC 117/119, mode 2031
• Clipboard and shell integration: OSC 52, OSC 7, OSC 133, OSC 633
• Alternate-screen variants and scrollback semantics
• Terminfo-backed output strings for cursor movement and erase operations
• Sixel and iTerm2 graphics capability reporting

These are tracking items only; each should get its own focused spec and implementation PR when prioritized.