Files
MeshTerm/meshterm/tools/watchtower.py
T
Jean-Pierre MartineauandClaude Opus 5 284e35edb4 Main menu: five sections, each one an answer to the question
The menu asks "What would you like to do?" and then grouped its rows by
subject, which is not an answer to that. Mesh had grown to seven of the
nineteen rows — live watching, passive browsing, and one transmit action
in the same bucket — and Tools said nothing at all, since everything in
the menu is a tool.

So each section now names a doing, and holds what shares it:

  Message      Chat · Channels · Courier · Contacts
  Watch        Dashboard · Live feed · Watchtower · Time machine
  Explore      Map · Mesh walk · Trace target · Trace path · Trophy case
  This node    Device info · Device configuration · Device actions · Send advert
  Other nodes  Repeater admin · TX optimize

Four rows moved for a reason. Contacts is the address book the three
features above it pick a recipient from, not a mesh view. Time machine is
the past tense of the Dashboard, and was stranded in the grab-bag. Send
advert is your own node announcing itself — a device action, filed with
the mesh views only because it was about the mesh. And Repeater admin and
TX optimize are the same job — someone else's radio, over the mesh, with
credentials — which the old Device-management/Tools split hid.

The two walks join the topology views they walk over, with the boards
that score them underneath: see a node, walk to it, get scored. Nothing
is renamed (a menu row still names the screen it opens) and no section is
now larger than five rows or smaller than two.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-11 02:22:07 -04:00

72 lines
2.5 KiB
Python

"""The ``watchtower`` tool: a passive sentinel over the nodes you care about.
Opens the Watchtower screen (see :mod:`meshterm.ui.watchtower_screen`): the alert log
with acknowledge/clear, the watchlist, and per-node rules. The rules themselves run in
the background for the whole session (see :mod:`meshterm.services.watchtower`) — a
silence alarm when a starred node goes quiet, an SNR-sag warning when its receptions
degrade, a recovery note when it returns, and a mesh-wide heads-up when a never-before-
seen node appears. Unacknowledged alerts show as the ``▲ n`` badge in the header, so
nothing here needs to be open to be on duty.
Menu-only: the sentinel is inherently a live, session-long service; scripted runs can
read the same history through ``monitor``/``nodes``.
"""
from __future__ import annotations
from typing import Any, Optional
import typer
from ..context import AppContext
from .base import Tool, ToolResult, register
@register
class WatchtowerTool(Tool):
"""Watch starred nodes: silence alarms, SNR sag, new-node sightings."""
name = "watchtower"
title = "Watchtower"
icon = "🚨"
help = "Alerts for watched nodes — silence, SNR sag, new arrivals"
category = "Watch"
order = 30 # after the live views: the section's always-on alerting eye
async def prompt_params(self, ctx: AppContext) -> Optional[dict[str, Any]]:
"""Run the Watchtower screen; there are never parameters to collect.
The screen presents everything itself and returns when dismissed, so
returning ``None`` tells the menu the invocation is complete (the same
pattern as the ``dashboard`` tool).
Args:
ctx: Shared application context.
Returns:
Always ``None``.
"""
from ..ui.watchtower_screen import open_watchtower
await open_watchtower(ctx)
return None
async def run(self, ctx: AppContext, params: dict[str, Any]) -> ToolResult:
"""Nothing runs here: the Watchtower lives inside :meth:`prompt_params`.
Args:
ctx: Shared application context.
params: Unused.
Returns:
An empty :class:`ToolResult` (only reachable from a scripted call).
"""
return ToolResult(summary={})
def register_cli(self, app: typer.Typer) -> None:
"""Register no CLI command — the Watchtower is a live, menu-only feature.
Args:
app: The Typer application (untouched).
"""