termapy 0.78.0__tar.gz → 0.79.0__tar.gz

{termapy-0.78.0 → termapy-0.79.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: termapy
-Version: 0.78.0
+Version: 0.79.0
 Summary: A TUI serial terminal with ANSI color support, built on Textual and pyserial
 Keywords: serial,terminal,tui,textual,pyserial,embedded,xmodem,ymodem
 Author: Chuck Bass
@@ -20,7 +20,7 @@ Classifier: Programming Language :: Python :: 3.15
 Classifier: Topic :: Communications
 Classifier: Topic :: System :: Hardware
 Classifier: Topic :: Terminals :: Serial
-Requires-Dist: textual>=0.80
+Requires-Dist: textual>=2.0
 Requires-Dist: prompt-toolkit>=3.0
 Requires-Dist: pygments>=2.20.0
 Requires-Dist: tree-sitter>=0.25.0,<0.27
@@ -31,6 +31,7 @@ Requires-Dist: packaging>=24.0
 Requires-Dist: frist>=0.21
 Requires-Dist: platformdirs>=4.0
 Requires-Dist: crcglot>=0.32.1
+Requires-Dist: pyelftools>=0.33
 Requires-Dist: termapy[mcp,web] ; extra == 'all'
 Requires-Dist: mcp>=2,<3 ; extra == 'mcp'
 Requires-Dist: textual-serve>=1.1 ; extra == 'web'
@@ -101,6 +102,12 @@ For your own device, one line creates a config and connects:
 termapy --new my_device COM4 115200 8N1
 ```
 
+For a new dev board, a starter project gives it a command monitor that answers you and an MCP agent on day one. The Raspberry Pi Pico and the ESP32-S3 DevKitC-1 have one; see the Dev boards help page:
+
+```sh
+termapy --board pico
+```
+
 For a plain-text terminal (no TUI), use CLI mode:
 
 ```sh
@@ -150,11 +157,26 @@ See the [detailed feature comparison](docs/comparison.md) against RealTerm, Cool
 
 </details>
 
+## Feature status
+
+Termapy is in beta: everything not listed here is stable and ready for public testing. These parts work and are used daily, but they are still being developed, sit outside the compatibility promise, and may change in any release.
+
+| Feature | Commands | Status |
+| --- | --- | --- |
+| MCP server | `/mcp` | preview |
+| Device files | `/dev` | preview |
+| Symbols | `/sym` | preview |
+| Memory access | `/mem` | preview |
+| Dev board starters | `/board` | prototype |
+| Device-side firmware | `/firmware` | prototype |
+
+**Preview** works but may change in any release; **prototype** is new and incomplete, and may change or be removed. `/help` shows each command's level in every listing and on its page, the MCP catalog carries it, and a prototype says so once a session when it first runs.
+
 ## Security
 
-Termapy runs with your privileges and does whatever you — or a connected MCP client — tell it, so point it at devices, profiles, and MCP clients you trust. The MCP server is **sandboxed by default**: an automated agent is confined to the serial device and config directory (at worst, a hostile device or profile hangs the session), and each class of host access below stays off until you opt in.
+Termapy runs with your privileges and does whatever you — or a connected MCP client — tell it, so point it at devices, profiles, and MCP clients you trust. The MCP server is a preview, and its limits on host access are not complete yet: by default it refuses the access below on the main routes, but known gaps remain (listed in the [MCP server](src/termapy/help/mcp-server.md) help), so the MCP client's own permissions are the real boundary.
 
-| Host access (off by default) | Opt in with |
+| Host access (refused by default on the main routes) | Opt in with |
 | --- | --- |
 | Files outside the config directory | `TERMAPY_MCP_FS_UNCONFINED=1` |
 | Network sockets (`socket://`, `rfc2217://`) | `TERMAPY_MCP_NET_EGRESS=1` |
@@ -173,6 +195,9 @@ Each flag takes any boolean token (`1`, `on`, `true`, `yes`, ...); a value outsi
 | Ctrl+S  | Save SVG screenshot                 |
 | Ctrl+T  | Save text screenshot                |
 | Ctrl+P  | Command palette                     |
+| Ctrl+C  | Copy the selected output text       |
+| Ctrl+A  | Select all output (click it first)  |
+| Shift+Up | Select output lines from the prompt; then Shift+arrows grow it |
 | F1–F4   | Help / Cfg / Run / Proto buttons (Ctrl+Shift+1–4 in VS Code); F10 edits the config |
 | Up/Down | Cycle through command history       |
 | Escape  | Clear input / exit history browsing |
@@ -245,6 +270,7 @@ The most common ones:
 | `/cfg.auto <key> <value>`            | Set an in-memory config key immediately (no confirmation)                     |
 | `/cfg.list`                          | List all config files                                                         |
 | `/cfg.load <name>`                   | Switch to a different config by name                                          |
+| `/cfg.loaded`                        | Show what the config load loaded: plugin files, symbols, device files         |
 | `/cfg.show`                          | Open the current config file in the system viewer                             |
 | `/cfg.help`                          | Same as `/help cfg`                                                           |
 | `/ss.svg {name}`                     | Save SVG screenshot                                                           |
@@ -252,7 +278,7 @@ The most common ones:
 | `/ss.list`                           | List screenshots, newest first, with size and age                             |
 | `/ss.explore`                        | Open the screenshot folder in the system file explorer                        |
 | `/cls`                               | Clear the terminal screen                                                     |
-| `/run {filename}`                    | Open Run picker (bare TUI), list scripts (bare CLI), or run; nests 5 deep     |
+| `/run {filename}`                    | Open Run picker (bare TUI), list scripts (bare CLI), or run; nests 5 deep; `--echo` shows each command line as it runs |
 | `/run.list`                          | List .run files in run/, newest first, with size, age, and summary            |
 | `/run.rename <old> <new>`            | Rename a script (`.run` kept; never overwrites)                               |
 | `/run.help`                          | Same as `/help run`                                                           |
@@ -291,31 +317,32 @@ The most common ones:
 | `/proto.list`                        | List .pro files in proto/, newest first, with size, age and each one's `name`  |
 | `/proto.rename <old> <new>`          | Rename a protocol script (`.pro` kept; never overwrites)                      |
 | `/proto.hex {on\|off\|toggle}`        | Same flag as `/term.hex`                                                      |
-| `/proto.crc.list {pat}`              | List available CRC algorithms (optional glob filter)                          |
+| `/proto.crc.list {pat}`              | List available CRC algorithms (optional name pattern: `modbus`, `crc16*`)     |
 | `/proto.crc.info <name>`             | Show CRC algorithm parameters and description                                 |
 | `/proto.crc.calc <n> {d}`            | Compute CRC over hex bytes, quoted text, or a file; omit data to verify check string |
 | `/proto.crc.find bin=<hex>\|asc=<text>\|cmd=<trigger>` | Identify CRC algorithm from a captured packet, text, or a command's reply |
 | `/proto.info`                        | Print current protocol state                                                  |
-| `/mem.dump <target> {len} {type}`    | Hexdump or typed word columns at an address or symbol                         |
+| `/mem.dump <target> {len} {type}`    | Hexdump or typed word columns; columns follow the output level (bytes at quiet, +ASCII at normal, +address at verbose) |
 | `/mem.read <target> {type}`          | One typed value: scalar, char, register field, bit or slice                   |
-| `/mem.write <target> <hex>`          | Write hex bytes, or set a register field/bit (audited; destructive over MCP)  |
+| `/mem.write <target> <value>`        | Write a value to a named symbol, register or field, or hex bytes at an address (audited; destructive over MCP) |
 | `/mem.or <target> <mask>`            | Boolean ops on one word (also `.and`, `.clear`, `.xor`, `.not`); atomic via `MEM.M` where expressible |
 | `/mem.str <target> {max}`            | Read a NUL-terminated string as a first-class value                           |
 | `/mem.info`                          | Memory access config: dialect, block limit, width, endian, atomic modify      |
 | `/sym <addr\|name>`                  | Symbol table: name to address, or address to `name+offset`                   |
-| `/sym.import {file} {format=<value>}` | Convert a linker map to `sym/<cfg>.symbols.json` and load it (bare: re-import the same map) |
+| `/sym.import {file} {format=<value>}` | Convert an ELF or a linker map to `sym/<cfg>.symbols.json` and load it (bare: re-import the same file) |
 | `/sym.info`                          | Show the loaded symbol table: file, source, counts by section, range          |
 | `/sym.load {path}`                   | Load a symbol table (default: the cfg sidecar `/sym.import` writes)           |
-| `/sym.search <pattern>`              | Search symbols by name: exact, glob, regex, or substring                      |
+| `/sym.search <pattern>`              | Search symbols by name: the exact name, else a name pattern (`gpio`, `Mon*`)  |
 | `/sym.unload`                        | Clear the loaded symbol table                                                 |
 | `/dev.import <file> {format=<value>} {category=<value>} {to=<value>} {use=on\|off}` | Convert a vendor register description (CMSIS-SVD) into this config's `lib/` and reference it from `dev/` (`to=global` shares it) |
 | `/dev.lib {pattern}`                 | List the parts the libraries hold (available, not loaded), with their layer  |
 | `/dev.list`                          | List the devices this config has loaded, with layer and placement            |
+| `/dev.regs <device> {pattern}`       | List a loaded device's registers from its file (never the chip), hazards flagged |
 | `/dev.use <part> {at=<value>}`       | Add a library part to this config; `at=NAME@ADDR ...` places a relocatable one |
 | `/var {name}`                        | List user variables, or show one by name                                      |
 | `/var.set <NAME> <value>`            | Set a user variable                                                           |
 | `/var.clear`                         | Clear all user variables                                                      |
-| `/env.list {pattern}`                | List environment variables (all, by name, or glob)                            |
+| `/env.list {pattern}`                | List environment variables (all, or a name pattern: `path`, `COM*`)           |
 | `/env.set <name> <value>`            | Set a session-scoped environment variable                                     |
 | `/env.reload`                        | Re-snapshot variables from the OS environment                                 |
 | `/cap.text <f> ...`                  | Capture serial text to file for a timed duration                              |
@@ -359,6 +386,7 @@ termapy_cfg/
     │   ├── temp_plot.py
     │   └── traffic.py
     ├── sym/                            # symbol tables (demo.symbols.json, auto-loaded)
+    ├── dev/                            # device files (console.device.json: the UART block CONSOLE names)
     └── proto/                          # protocol test scripts
         ├── at_test.pro
         ├── bitfield_inline.pro
@@ -402,7 +430,7 @@ You can also manage environment variables at runtime with REPL commands:
 
 | Command                 | Description                                        |
 | ----------------------- | -------------------------------------------------- |
-| `/env.list {pattern}`   | List variables (all, by name, or glob like `COM*`) |
+| `/env.list {pattern}`   | List variables (all, or a name pattern: `COM*`)    |
 | `/env.set <name> <val>` | Set a session-scoped variable (in-memory only)     |
 | `/env.reload`           | Re-snapshot variables from the OS environment      |
 
@@ -572,18 +600,9 @@ Set `serial.flow_control` to `"manual"` to get DTR, RTS, and Break buttons in th
 <!-- validate-config-keys -->
 ```json
 {
-    "config_version": 30,
+    "config_version": 33,
     "title": "",
     "border_color": "",
-    "max_lines": 10000,
-    "default_ui": "tui",
-    "vt100_hint": true,
-    "cmd_prefix": "/",
-    "cli_prompt": "$(CFG)> ",
-    "cli_completion": true,
-    "config_read_only": false,
-    "profile_path": "",
-    "validate_typed_args": false,
     "serial": {
         "port": "COM4",
         "baud_rate": 115200,
@@ -593,44 +612,57 @@ Set `serial.flow_control` to `"manual"` to get DTR, RTS, and Break buttons in th
         "stop_bits": 1,
         "flow_control": "none"
     },
-    "encoding": "utf-8",
-    "cmd_delay_ms": 0,
-    "protocol": "text",
-    "ndjson_field_routing": {
-        "response_id": "id",
-        "error_field": "error",
-        "event_field": "event"
-    },
-    "default_response_timeout_ms": 1000,
     "auto_connect": false,
     "auto_reconnect": false,
     "on_connect_cmd": "",
     "tui_on_connect_cmd": "",
     "cli_on_connect_cmd": "",
     "mcp_on_connect_cmd": "",
+    "encoding": "utf-8",
     "eol": "\r",
     "eol_rx": "auto",
+    "eol_markers": false,
     "send_bare_enter": false,
+    "cmd_delay_ms": 0,
+    "multiline_paste": true,
+    "multiline_paste_delay_ms": 10,
     "echo": false,
     "echo_fmt": "[purple]$(CFG)> {cmd}[/]",
-    "log_file": "",
-    "show_traceback": false,
-    "proto_frame_gap_ms": 50,
-    "proto_results_template": "{name}_results.json",
     "timestamps": false,
-    "eol_markers": false,
     "line_no": false,
     "hex": false,
+    "max_lines": 10000,
+    "max_grep_lines": 100,
+    "protocol": "text",
+    "ndjson_field_routing": {
+        "response_id": "id",
+        "error_field": "error",
+        "event_field": "event"
+    },
     "request_mode": false,
     "request_err_pattern": "(?i)^(ERROR|ERR|FAULT)\\b",
-    "json_style": "compact",
     "strip_device_echo": false,
-    "max_grep_lines": 100,
+    "json_style": "compact",
+    "profile_path": "",
+    "validate_typed_args": false,
+    "default_response_timeout_ms": 1000,
+    "log_file": "",
     "file_xfer_root": "",
+    "proto_frame_gap_ms": 50,
+    "proto_results_template": "{name}_results.json",
+    "default_ui": "tui",
+    "quiet_start": true,
+    "vt100_hint": true,
+    "cmd_prefix": "/",
+    "cli_prompt": "$(CFG)> ",
+    "cli_completion": true,
+    "show_traceback": false,
     "cfg_enabled": true,
     "run_enabled": true,
     "proto_enabled": true,
     "record_enabled": true,
+    "config_read_only": false,
+    "custom_buttons_side": "bottom",
     "custom_buttons": []
 }
 ```
@@ -907,7 +939,7 @@ The device supports a full AT command set. Type commands and get responses just
 | `AT+STATUS`        | Device status (LED, uptime, connections)          |
 | `AT+RESET`         | Reset device (simulates boot sequence)            |
 | `mem <addr> [len]` | Hex memory dump (deterministic, max 256 bytes)    |
-| `help`             | List all commands                                 |
+| `help`             | The command landscape, grouped                    |
 
 #### GPS / NMEA commands
 
@@ -1011,7 +1043,7 @@ It's also a reversible toggle from inside the TUI, like `/cli` <-> `/tui`: `/vt1
 
 ### Symbols, memory and parts
 
-`/sym.import build/mem.map` turns your linker map into names, so `/mem.read gTemp` reads a variable by name instead of by address. `/dev.import part.svd` does the same for the silicon: a vendor CMSIS-SVD becomes a **device file** -- every register of the part with its bit fields -- stored once in the config's `lib/` and referenced from its `dev/`, so `/mem.read PORT_GROUP0_DIR` works and a checked-in config folder carries its parts. A part on the external bus (two ADCs, an FPGA block) is written once with register offsets and placed per board: `/dev.use acme-adc16 at=ADC1@0x60000000 ADC2@0x60001000`. Registers are live silicon, not variables, so `/mem.*` refuses bulk reads over them, refuses reads of write-only registers, and logs the rest. The device side is the MEM wire spec (`examples/firmware/termapy_mem.c`, a drop-in) or a profile block describing your monitor's own peek/poke grammar. See the Symbols, Devices and Memory help pages.
+`/sym.import out/default.elf` turns your build into names, sizes and C types (from its debug info), so `/mem.read gTemp` reads a variable by name instead of by address, signed or float as declared; a linker map works too, with names and sizes only. A `const` in the build keeps its value, and a pointer constant to a peripheral names its registers under your own name (`SPI_PORT_DIR` for `PORTC_DIR`). `/dev.import part.svd` does the same for the silicon: a vendor CMSIS-SVD becomes a **device file** -- every register of the part with its bit fields -- stored once in the config's `lib/` and referenced from its `dev/`, so `/mem.read PORT_GROUP0_DIR` works and a checked-in config folder carries its parts. A part on the external bus (two ADCs, an FPGA block) is written once with register offsets and placed per board: `/dev.use acme-adc16 at=ADC1@0x60000000 ADC2@0x60001000`. Registers are live silicon, not variables, so `/mem.*` refuses bulk reads over them, refuses reads of write-only registers, and logs the rest. The device side is the MEM wire spec (`/firmware.copy mem` writes the drop-in `termapy_mem.c` into your tree) or a profile block describing your monitor's own peek/poke grammar. See the Symbols, Devices and Memory help pages.
 
 ### Plugins
 
@@ -1047,7 +1079,7 @@ COMMAND = Command(
 
 Resolution is the same in every frontend (TUI, CLI, MCP server) and reruns on every config switch; a folder plugin can never take an app hook's name.
 
-Subcommands (`/tool.run`, `/tool.status`), typed parameters, scriptable return values, the full `PluginContext` API with its five handles and capability gating, and the `ctx.internal` escape hatch that built-ins use are all in the [Writing plugins](src/termapy/help/writing-plugins.md) guide, which also ships in the in-app help.
+Subcommands (`/tool.run`, `/tool.status`), typed parameters, scriptable return values, the full `PluginContext` API with its five handles and capability gating, and `ctx.internal`, the engine and host services every plugin may use, are all in the [Writing plugins](src/termapy/help/writing-plugins.md) guide, which also ships in the in-app help.
 
 <details>
 <summary>Example plugins</summary>
@@ -1212,7 +1244,7 @@ Every command runs on a worker thread, the serial reader is the only long-lived
 </details>
 
 <details>
-<summary><strong>Test coverage</strong> - 5077 tests</summary>
+<summary><strong>Test coverage</strong> - 6018 tests</summary>
 
 Run the full suite with `uv run pytest`. (The count above is the one place it
 is tracked; `release_prep` refreshes it each release.) The coverage figure is

{termapy-0.78.0 → termapy-0.79.0}/README.md

@@ -54,6 +54,12 @@ For your own device, one line creates a config and connects:
 termapy --new my_device COM4 115200 8N1
 ```
 
+For a new dev board, a starter project gives it a command monitor that answers you and an MCP agent on day one. The Raspberry Pi Pico and the ESP32-S3 DevKitC-1 have one; see the Dev boards help page:
+
+```sh
+termapy --board pico
+```
+
 For a plain-text terminal (no TUI), use CLI mode:
 
 ```sh
@@ -103,11 +109,26 @@ See the [detailed feature comparison](docs/comparison.md) against RealTerm, Cool
 
 </details>
 
+## Feature status
+
+Termapy is in beta: everything not listed here is stable and ready for public testing. These parts work and are used daily, but they are still being developed, sit outside the compatibility promise, and may change in any release.
+
+| Feature | Commands | Status |
+| --- | --- | --- |
+| MCP server | `/mcp` | preview |
+| Device files | `/dev` | preview |
+| Symbols | `/sym` | preview |
+| Memory access | `/mem` | preview |
+| Dev board starters | `/board` | prototype |
+| Device-side firmware | `/firmware` | prototype |
+
+**Preview** works but may change in any release; **prototype** is new and incomplete, and may change or be removed. `/help` shows each command's level in every listing and on its page, the MCP catalog carries it, and a prototype says so once a session when it first runs.
+
 ## Security
 
-Termapy runs with your privileges and does whatever you — or a connected MCP client — tell it, so point it at devices, profiles, and MCP clients you trust. The MCP server is **sandboxed by default**: an automated agent is confined to the serial device and config directory (at worst, a hostile device or profile hangs the session), and each class of host access below stays off until you opt in.
+Termapy runs with your privileges and does whatever you — or a connected MCP client — tell it, so point it at devices, profiles, and MCP clients you trust. The MCP server is a preview, and its limits on host access are not complete yet: by default it refuses the access below on the main routes, but known gaps remain (listed in the [MCP server](src/termapy/help/mcp-server.md) help), so the MCP client's own permissions are the real boundary.
 
-| Host access (off by default) | Opt in with |
+| Host access (refused by default on the main routes) | Opt in with |
 | --- | --- |
 | Files outside the config directory | `TERMAPY_MCP_FS_UNCONFINED=1` |
 | Network sockets (`socket://`, `rfc2217://`) | `TERMAPY_MCP_NET_EGRESS=1` |
@@ -126,6 +147,9 @@ Each flag takes any boolean token (`1`, `on`, `true`, `yes`, ...); a value outsi
 | Ctrl+S  | Save SVG screenshot                 |
 | Ctrl+T  | Save text screenshot                |
 | Ctrl+P  | Command palette                     |
+| Ctrl+C  | Copy the selected output text       |
+| Ctrl+A  | Select all output (click it first)  |
+| Shift+Up | Select output lines from the prompt; then Shift+arrows grow it |
 | F1–F4   | Help / Cfg / Run / Proto buttons (Ctrl+Shift+1–4 in VS Code); F10 edits the config |
 | Up/Down | Cycle through command history       |
 | Escape  | Clear input / exit history browsing |
@@ -198,6 +222,7 @@ The most common ones:
 | `/cfg.auto <key> <value>`            | Set an in-memory config key immediately (no confirmation)                     |
 | `/cfg.list`                          | List all config files                                                         |
 | `/cfg.load <name>`                   | Switch to a different config by name                                          |
+| `/cfg.loaded`                        | Show what the config load loaded: plugin files, symbols, device files         |
 | `/cfg.show`                          | Open the current config file in the system viewer                             |
 | `/cfg.help`                          | Same as `/help cfg`                                                           |
 | `/ss.svg {name}`                     | Save SVG screenshot                                                           |
@@ -205,7 +230,7 @@ The most common ones:
 | `/ss.list`                           | List screenshots, newest first, with size and age                             |
 | `/ss.explore`                        | Open the screenshot folder in the system file explorer                        |
 | `/cls`                               | Clear the terminal screen                                                     |
-| `/run {filename}`                    | Open Run picker (bare TUI), list scripts (bare CLI), or run; nests 5 deep     |
+| `/run {filename}`                    | Open Run picker (bare TUI), list scripts (bare CLI), or run; nests 5 deep; `--echo` shows each command line as it runs |
 | `/run.list`                          | List .run files in run/, newest first, with size, age, and summary            |
 | `/run.rename <old> <new>`            | Rename a script (`.run` kept; never overwrites)                               |
 | `/run.help`                          | Same as `/help run`                                                           |
@@ -244,31 +269,32 @@ The most common ones:
 | `/proto.list`                        | List .pro files in proto/, newest first, with size, age and each one's `name`  |
 | `/proto.rename <old> <new>`          | Rename a protocol script (`.pro` kept; never overwrites)                      |
 | `/proto.hex {on\|off\|toggle}`        | Same flag as `/term.hex`                                                      |
-| `/proto.crc.list {pat}`              | List available CRC algorithms (optional glob filter)                          |
+| `/proto.crc.list {pat}`              | List available CRC algorithms (optional name pattern: `modbus`, `crc16*`)     |
 | `/proto.crc.info <name>`             | Show CRC algorithm parameters and description                                 |
 | `/proto.crc.calc <n> {d}`            | Compute CRC over hex bytes, quoted text, or a file; omit data to verify check string |
 | `/proto.crc.find bin=<hex>\|asc=<text>\|cmd=<trigger>` | Identify CRC algorithm from a captured packet, text, or a command's reply |
 | `/proto.info`                        | Print current protocol state                                                  |
-| `/mem.dump <target> {len} {type}`    | Hexdump or typed word columns at an address or symbol                         |
+| `/mem.dump <target> {len} {type}`    | Hexdump or typed word columns; columns follow the output level (bytes at quiet, +ASCII at normal, +address at verbose) |
 | `/mem.read <target> {type}`          | One typed value: scalar, char, register field, bit or slice                   |
-| `/mem.write <target> <hex>`          | Write hex bytes, or set a register field/bit (audited; destructive over MCP)  |
+| `/mem.write <target> <value>`        | Write a value to a named symbol, register or field, or hex bytes at an address (audited; destructive over MCP) |
 | `/mem.or <target> <mask>`            | Boolean ops on one word (also `.and`, `.clear`, `.xor`, `.not`); atomic via `MEM.M` where expressible |
 | `/mem.str <target> {max}`            | Read a NUL-terminated string as a first-class value                           |
 | `/mem.info`                          | Memory access config: dialect, block limit, width, endian, atomic modify      |
 | `/sym <addr\|name>`                  | Symbol table: name to address, or address to `name+offset`                   |
-| `/sym.import {file} {format=<value>}` | Convert a linker map to `sym/<cfg>.symbols.json` and load it (bare: re-import the same map) |
+| `/sym.import {file} {format=<value>}` | Convert an ELF or a linker map to `sym/<cfg>.symbols.json` and load it (bare: re-import the same file) |
 | `/sym.info`                          | Show the loaded symbol table: file, source, counts by section, range          |
 | `/sym.load {path}`                   | Load a symbol table (default: the cfg sidecar `/sym.import` writes)           |
-| `/sym.search <pattern>`              | Search symbols by name: exact, glob, regex, or substring                      |
+| `/sym.search <pattern>`              | Search symbols by name: the exact name, else a name pattern (`gpio`, `Mon*`)  |
 | `/sym.unload`                        | Clear the loaded symbol table                                                 |
 | `/dev.import <file> {format=<value>} {category=<value>} {to=<value>} {use=on\|off}` | Convert a vendor register description (CMSIS-SVD) into this config's `lib/` and reference it from `dev/` (`to=global` shares it) |
 | `/dev.lib {pattern}`                 | List the parts the libraries hold (available, not loaded), with their layer  |
 | `/dev.list`                          | List the devices this config has loaded, with layer and placement            |
+| `/dev.regs <device> {pattern}`       | List a loaded device's registers from its file (never the chip), hazards flagged |
 | `/dev.use <part> {at=<value>}`       | Add a library part to this config; `at=NAME@ADDR ...` places a relocatable one |
 | `/var {name}`                        | List user variables, or show one by name                                      |
 | `/var.set <NAME> <value>`            | Set a user variable                                                           |
 | `/var.clear`                         | Clear all user variables                                                      |
-| `/env.list {pattern}`                | List environment variables (all, by name, or glob)                            |
+| `/env.list {pattern}`                | List environment variables (all, or a name pattern: `path`, `COM*`)           |
 | `/env.set <name> <value>`            | Set a session-scoped environment variable                                     |
 | `/env.reload`                        | Re-snapshot variables from the OS environment                                 |
 | `/cap.text <f> ...`                  | Capture serial text to file for a timed duration                              |
@@ -312,6 +338,7 @@ termapy_cfg/
     │   ├── temp_plot.py
     │   └── traffic.py
     ├── sym/                            # symbol tables (demo.symbols.json, auto-loaded)
+    ├── dev/                            # device files (console.device.json: the UART block CONSOLE names)
     └── proto/                          # protocol test scripts
         ├── at_test.pro
         ├── bitfield_inline.pro
@@ -355,7 +382,7 @@ You can also manage environment variables at runtime with REPL commands:
 
 | Command                 | Description                                        |
 | ----------------------- | -------------------------------------------------- |
-| `/env.list {pattern}`   | List variables (all, by name, or glob like `COM*`) |
+| `/env.list {pattern}`   | List variables (all, or a name pattern: `COM*`)    |
 | `/env.set <name> <val>` | Set a session-scoped variable (in-memory only)     |
 | `/env.reload`           | Re-snapshot variables from the OS environment      |
 
@@ -525,18 +552,9 @@ Set `serial.flow_control` to `"manual"` to get DTR, RTS, and Break buttons in th
 <!-- validate-config-keys -->
 ```json
 {
-    "config_version": 30,
+    "config_version": 33,
     "title": "",
     "border_color": "",
-    "max_lines": 10000,
-    "default_ui": "tui",
-    "vt100_hint": true,
-    "cmd_prefix": "/",
-    "cli_prompt": "$(CFG)> ",
-    "cli_completion": true,
-    "config_read_only": false,
-    "profile_path": "",
-    "validate_typed_args": false,
     "serial": {
         "port": "COM4",
         "baud_rate": 115200,
@@ -546,44 +564,57 @@ Set `serial.flow_control` to `"manual"` to get DTR, RTS, and Break buttons in th
         "stop_bits": 1,
         "flow_control": "none"
     },
-    "encoding": "utf-8",
-    "cmd_delay_ms": 0,
-    "protocol": "text",
-    "ndjson_field_routing": {
-        "response_id": "id",
-        "error_field": "error",
-        "event_field": "event"
-    },
-    "default_response_timeout_ms": 1000,
     "auto_connect": false,
     "auto_reconnect": false,
     "on_connect_cmd": "",
     "tui_on_connect_cmd": "",
     "cli_on_connect_cmd": "",
     "mcp_on_connect_cmd": "",
+    "encoding": "utf-8",
     "eol": "\r",
     "eol_rx": "auto",
+    "eol_markers": false,
     "send_bare_enter": false,
+    "cmd_delay_ms": 0,
+    "multiline_paste": true,
+    "multiline_paste_delay_ms": 10,
     "echo": false,
     "echo_fmt": "[purple]$(CFG)> {cmd}[/]",
-    "log_file": "",
-    "show_traceback": false,
-    "proto_frame_gap_ms": 50,
-    "proto_results_template": "{name}_results.json",
     "timestamps": false,
-    "eol_markers": false,
     "line_no": false,
     "hex": false,
+    "max_lines": 10000,
+    "max_grep_lines": 100,
+    "protocol": "text",
+    "ndjson_field_routing": {
+        "response_id": "id",
+        "error_field": "error",
+        "event_field": "event"
+    },
     "request_mode": false,
     "request_err_pattern": "(?i)^(ERROR|ERR|FAULT)\\b",
-    "json_style": "compact",
     "strip_device_echo": false,
-    "max_grep_lines": 100,
+    "json_style": "compact",
+    "profile_path": "",
+    "validate_typed_args": false,
+    "default_response_timeout_ms": 1000,
+    "log_file": "",
     "file_xfer_root": "",
+    "proto_frame_gap_ms": 50,
+    "proto_results_template": "{name}_results.json",
+    "default_ui": "tui",
+    "quiet_start": true,
+    "vt100_hint": true,
+    "cmd_prefix": "/",
+    "cli_prompt": "$(CFG)> ",
+    "cli_completion": true,
+    "show_traceback": false,
     "cfg_enabled": true,
     "run_enabled": true,
     "proto_enabled": true,
     "record_enabled": true,
+    "config_read_only": false,
+    "custom_buttons_side": "bottom",
     "custom_buttons": []
 }
 ```
@@ -860,7 +891,7 @@ The device supports a full AT command set. Type commands and get responses just
 | `AT+STATUS`        | Device status (LED, uptime, connections)          |
 | `AT+RESET`         | Reset device (simulates boot sequence)            |
 | `mem <addr> [len]` | Hex memory dump (deterministic, max 256 bytes)    |
-| `help`             | List all commands                                 |
+| `help`             | The command landscape, grouped                    |
 
 #### GPS / NMEA commands
 
@@ -964,7 +995,7 @@ It's also a reversible toggle from inside the TUI, like `/cli` <-> `/tui`: `/vt1
 
 ### Symbols, memory and parts
 
-`/sym.import build/mem.map` turns your linker map into names, so `/mem.read gTemp` reads a variable by name instead of by address. `/dev.import part.svd` does the same for the silicon: a vendor CMSIS-SVD becomes a **device file** -- every register of the part with its bit fields -- stored once in the config's `lib/` and referenced from its `dev/`, so `/mem.read PORT_GROUP0_DIR` works and a checked-in config folder carries its parts. A part on the external bus (two ADCs, an FPGA block) is written once with register offsets and placed per board: `/dev.use acme-adc16 at=ADC1@0x60000000 ADC2@0x60001000`. Registers are live silicon, not variables, so `/mem.*` refuses bulk reads over them, refuses reads of write-only registers, and logs the rest. The device side is the MEM wire spec (`examples/firmware/termapy_mem.c`, a drop-in) or a profile block describing your monitor's own peek/poke grammar. See the Symbols, Devices and Memory help pages.
+`/sym.import out/default.elf` turns your build into names, sizes and C types (from its debug info), so `/mem.read gTemp` reads a variable by name instead of by address, signed or float as declared; a linker map works too, with names and sizes only. A `const` in the build keeps its value, and a pointer constant to a peripheral names its registers under your own name (`SPI_PORT_DIR` for `PORTC_DIR`). `/dev.import part.svd` does the same for the silicon: a vendor CMSIS-SVD becomes a **device file** -- every register of the part with its bit fields -- stored once in the config's `lib/` and referenced from its `dev/`, so `/mem.read PORT_GROUP0_DIR` works and a checked-in config folder carries its parts. A part on the external bus (two ADCs, an FPGA block) is written once with register offsets and placed per board: `/dev.use acme-adc16 at=ADC1@0x60000000 ADC2@0x60001000`. Registers are live silicon, not variables, so `/mem.*` refuses bulk reads over them, refuses reads of write-only registers, and logs the rest. The device side is the MEM wire spec (`/firmware.copy mem` writes the drop-in `termapy_mem.c` into your tree) or a profile block describing your monitor's own peek/poke grammar. See the Symbols, Devices and Memory help pages.
 
 ### Plugins
 
@@ -1000,7 +1031,7 @@ COMMAND = Command(
 
 Resolution is the same in every frontend (TUI, CLI, MCP server) and reruns on every config switch; a folder plugin can never take an app hook's name.
 
-Subcommands (`/tool.run`, `/tool.status`), typed parameters, scriptable return values, the full `PluginContext` API with its five handles and capability gating, and the `ctx.internal` escape hatch that built-ins use are all in the [Writing plugins](src/termapy/help/writing-plugins.md) guide, which also ships in the in-app help.
+Subcommands (`/tool.run`, `/tool.status`), typed parameters, scriptable return values, the full `PluginContext` API with its five handles and capability gating, and `ctx.internal`, the engine and host services every plugin may use, are all in the [Writing plugins](src/termapy/help/writing-plugins.md) guide, which also ships in the in-app help.
 
 <details>
 <summary>Example plugins</summary>
@@ -1165,7 +1196,7 @@ Every command runs on a worker thread, the serial reader is the only long-lived
 </details>
 
 <details>
-<summary><strong>Test coverage</strong> - 5077 tests</summary>
+<summary><strong>Test coverage</strong> - 6018 tests</summary>
 
 Run the full suite with `uv run pytest`. (The count above is the one place it
 is tracked; `release_prep` refreshes it each release.) The coverage figure is

{termapy-0.78.0 → termapy-0.79.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "termapy"
-version = "0.78.0"
+version = "0.79.0"
 description = "A TUI serial terminal with ANSI color support, built on Textual and pyserial"
 license = "MIT"
 license-files = ["LICENSE"]
@@ -32,7 +32,7 @@ classifiers = [
     "Topic :: Terminals :: Serial",
 ]
 dependencies = [
-    "textual>=0.80",
+    "textual>=2.0",
     "prompt-toolkit>=3.0",
     "pygments>=2.20.0",
     "tree-sitter>=0.25.0,<0.27",
@@ -43,6 +43,7 @@ dependencies = [
     "frist>=0.21",
     "platformdirs>=4.0",
     "crcglot>=0.32.1",
+    "pyelftools>=0.33",
 ]
 
 [[project.authors]]
@@ -86,7 +87,10 @@ extra-paths = [
 ]
 
 [tool.ty.src]
-exclude = ["src/termapy/vendor/**"]
+exclude = [
+    "src/termapy/vendor/**",
+    "src/termapy/boards/*/firmware/**",
+]
 
 [tool.pyright]
 extraPaths = [
@@ -96,6 +100,7 @@ extraPaths = [
 exclude = [
     "src/termapy/vendor",
     "src/termapy/html",
+    "src/termapy/boards/*/firmware",
 ]
 
 [tool.ruff]

{termapy-0.78.0 → termapy-0.79.0}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "termapy"
-version = "0.78.0"
+version = "0.79.0"
 description = "A TUI serial terminal with ANSI color support, built on Textual and pyserial"
 license = "MIT"
 license-files = ["LICENSE"]
@@ -26,7 +26,7 @@ classifiers = [
 dependencies = [
     # Core TUI framework (without [syntax] extra to avoid installing 16 tree-sitter
     # grammars - we only need json, toml, bash for our editors, listed below)
-    "textual>=0.80",
+    "textual>=2.0",
     # pyserial is vendored in src/termapy/vendor/serial/ (see vendor/LICENSES.md)
     "prompt-toolkit>=3.0",
     "pygments>=2.20.0",
@@ -137,6 +137,12 @@ dependencies = [
     # /proto.crc.detect (single-frame is unaffected).  Surfacing it is a
     # follow-up, not a floor concern.  Floor moves to 0.31.0.
     "crcglot>=0.32.1",
+    # ELF + DWARF reader behind /sym.import of a build's .elf: symbols from
+    # the symbol table, C types from the debug info.  Public domain, pure
+    # Python, no dependencies.  Imported only inside the elf converter, so
+    # startup and the flag paths never load it.  0.33 is the floor tested
+    # (DWARF 2 from XC32, DWARF 5 from Clang).
+    "pyelftools>=0.33",
 ]
 
 [project.optional-dependencies]
@@ -225,7 +231,7 @@ extra-paths = ["src/termapy/vendor", "scripts"]
 # exclude mirrors [tool.ty.src]: don't LINT the vendored code, but it
 # stays visible for import resolution.
 extraPaths = ["src/termapy/vendor", "scripts"]
-exclude = ["src/termapy/vendor", "src/termapy/html"]
+exclude = ["src/termapy/vendor", "src/termapy/html", "src/termapy/boards/*/firmware"]
 
 [tool.ty.src]
 # The gate (.githooks/pre-commit, release_prep) runs `ty check` with no
@@ -236,7 +242,9 @@ exclude = ["src/termapy/vendor", "src/termapy/html"]
 # modules (fcntl, termios, select.POLL*) in its platform shims, and ty
 # flags every reference as unresolved on Windows.  We still need the
 # extra-paths above so `import serial` resolves from our own code.
-exclude = ["src/termapy/vendor/**"]
+# A dev board's starter firmware (boards/<board>/firmware/) runs on the
+# board under MicroPython; its imports (machine) exist only there.
+exclude = ["src/termapy/vendor/**", "src/termapy/boards/*/firmware/**"]
 
 [tool.ruff]
 # 100 (not the black-default 88) buys room for inline suppression reasons