webbee 0.3.45__tar.gz → 0.3.47__tar.gz

{webbee-0.3.45 → webbee-0.3.47}/CHANGELOG.md

@@ -1,5 +1,47 @@
 # Changelog
 
+## 0.3.47
+
+The cloud brain now sees BOTH your machine's real clock and your configured
+Imperal profile timezone on every turn -- never just one blindly trusted.
+
+- **What changed:** every coding-context snapshot now carries `client_now`
+  (this machine's actual wall-clock reading, ISO 8601 with UTC offset) and
+  `client_tz_label` (the OS/IANA timezone name) alongside the existing
+  cwd/git/tree/repo_key. The kernel renders both facts side by side and
+  flags a drift explicitly (wrong system clock, a VM in a different zone, a
+  stale profile setting) instead of silently trusting either source.
+- **Why:** the brain previously only knew the CONFIGURED profile timezone
+  server-side -- it had no way to tell if the machine actually running the
+  agent disagreed with that (e.g. a VM parked in UTC, a laptop with a wrong
+  system clock). Now it always has ground truth from both ends.
+- Best-effort: any clock-read failure just omits the fields -- never blocks
+  a turn.
+
+## 0.3.46
+
+Fixed a real jitter bug in text selection: dragging to select past the
+bottom (or top) of the visible output no longer makes the pane "jump
+around" instead of scrolling smoothly.
+
+- **Root cause:** a real terminal fires MOUSE_MOVE far more often than
+  once while the pointer sits at the viewport edge (every pixel of hand
+  tremor counts as a new event) -- and EVERY one of those was scrolling
+  the pane immediately, at the same time the dock's own ticker
+  (`edge_tick`) was ALSO scrolling the same pane every 0.25s to keep the
+  drag going while the mouse holds still. Two independent scroll sources
+  racing each other on the same viewport is exactly what looked like
+  "the window runs back and forth" while trying to select a big chunk of
+  text (Valentin, live 2026-07-31).
+- **Fix:** the immediate scroll now fires ONLY on the actual edge
+  transition (the moment the drag first reaches the edge); every
+  following MOUSE_MOVE at the same edge just keeps the selection armed
+  and leaves ALL the ongoing scrolling to the ticker's one steady 0.25s
+  cadence -- the exact same one-source-of-truth contract the queue/todo
+  panels and tab bar already use for their own edge-forwarded drags, now
+  applied consistently everywhere in the terminal so no two panes/panels
+  ever fight over the same scroll.
+
 ## 0.3.45
 
 Consent prompts stop being an easy-to-miss detail:

{webbee-0.3.45 → webbee-0.3.47}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: webbee
-Version: 0.3.45
+Version: 0.3.47
 Summary: Webbee 🐝 — the Imperal Cloud coding agent in your terminal
 Project-URL: Homepage, https://imperal.io
 Project-URL: Documentation, https://docs.imperal.io

{webbee-0.3.45 → webbee-0.3.47}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "webbee"
-version = "0.3.45"
+version = "0.3.47"
 description = "Webbee 🐝 — the Imperal Cloud coding agent in your terminal"
 readme = "README.md"
 license = "MIT"

webbee-0.3.47/src/webbee/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.3.47"

{webbee-0.3.45 → webbee-0.3.47}/src/webbee/coding_context.py

@@ -1,9 +1,19 @@
 """Coding-context snapshot for the cloud brain (extracted verbatim from
 webbee.session): build_coding_context packages cwd/git/tree/repo identity
 (+ optional repo_profile), and detect_verify_cmd is the CLIENT-detected
-proof-of-done command a marathon carries in that context."""
+proof-of-done command a marathon carries in that context.
+
+client_now (2026-07-31, I-CODING-TIME-CONTRACT): the machine's OWN wall-clock
+reading, captured fresh on every snapshot -- distinct from whatever timezone
+the user has CONFIGURED in their Imperal profile/panel. The brain needs BOTH:
+the configured timezone (what the user SET) and the actual reading on the
+machine running the agent (what time it REALLY is there) so it can flag a
+drift (wrong system clock, VM in a different zone, stale profile setting)
+instead of silently trusting one source. Best-effort: any clock read failure
+degrades to an absent key, never blocks the turn."""
 import os
 import subprocess
+from datetime import datetime
 
 # Heavy dependency/build dirs the file-tree walk and the agent `grep` tool
 # must NEVER descend: they blow up walk time on real repos and (with the tree's
@@ -46,6 +56,19 @@ def build_coding_context(workspace_root: str, intel=None) -> dict:
     root = find_repo_root(cwd)
     d = {"cwd": cwd, "git": git, "tree": "\n".join(paths),
          "repo_key": compute_repo_key(root), "repo_root": root}
+    # I-CODING-TIME-CONTRACT: the machine's actual local wall-clock, ISO 8601
+    # WITH UTC offset (so the kernel can compare it against the user's
+    # CONFIGURED timezone without re-resolving anything) + the IANA zone name
+    # the OS reports, when available. Never raises -- a clock/tzdata error
+    # just omits the key, the kernel falls back to the configured-only view.
+    try:
+        _now_local = datetime.now().astimezone()
+        d["client_now"] = _now_local.isoformat(timespec="seconds")
+        _tzname = _now_local.tzname()
+        if _tzname:
+            d["client_tz_label"] = _tzname
+    except Exception:
+        pass
     if intel is not None and getattr(intel, "ready", False):
         try:
             d["repo_profile"] = intel.repo_profile()

{webbee-0.3.45 → webbee-0.3.47}/src/webbee/selection.py

@@ -87,11 +87,29 @@ def make_select_control(pane, FormattedTextControl, MouseEventType, MouseButton)
                     return NotImplemented
                 pane._edge_ticks = 0                # a fresh MOUSE_MOVE means the pointer isn't parked
                 y = ev.position.y
+                # webbee-code-selection-scroll-jitter-v1: a REAL terminal fires
+                # MOUSE_MOVE far more often than once (every pixel of hand
+                # tremor while parked at the edge trying to select further) --
+                # scrolling immediately on EVERY one of those, on top of
+                # edge_tick() ALREADY scrolling the same pane every 0.25s once
+                # armed, stacked two independent scroll sources racing each
+                # other and made the viewport visibly jump/jitter instead of
+                # scrolling smoothly (Valentin, live 2026-07-31: "окно бегает
+                # туда сюда"). The immediate nudge now fires ONLY on the edge
+                # transition (armed 0 -> 1/-1) for snappy first-touch
+                # feedback; every following MOUSE_MOVE that's STILL at the
+                # same edge just re-affirms the arm (resets _edge_ticks above,
+                # so the runaway guard doesn't fire) and leaves the ONGOING
+                # scroll entirely to edge_tick()'s single steady cadence --
+                # exactly the contract forward_mouse() already uses for the
+                # neighbor panels.
                 if y >= pane._view_h - 1:
-                    pane.scroll(3)
+                    if pane._edge_drag != 1:
+                        pane.scroll(3)
                     pane._edge_drag = 1
                 elif y <= 0:
-                    pane.scroll(-3)
+                    if pane._edge_drag != -1:
+                        pane.scroll(-3)
                     pane._edge_drag = -1
                 else:
                     pane._edge_drag = 0

{webbee-0.3.45 → webbee-0.3.47}/tests/test_coding_context.py

@@ -29,3 +29,15 @@ def test_build_coding_context_still_prunes_dotdirs(tmp_path):
     tree = build_coding_context(str(tmp_path))["tree"]
     assert "src/a.py" in tree
     assert ".secret" not in tree
+
+
+def test_build_coding_context_carries_client_now(tmp_path):
+    # I-CODING-TIME-CONTRACT: the brain needs the machine's ACTUAL wall-clock
+    # reading (distinct from the user's configured profile timezone) on every
+    # snapshot, so it can flag drift instead of blindly trusting one source.
+    import re
+    ctx = build_coding_context(str(tmp_path))
+    assert "client_now" in ctx
+    # ISO 8601 with an explicit UTC offset (+HH:MM/-HH:MM or Z) -- the kernel
+    # compares this against the configured timezone without re-resolving.
+    assert re.match(r"^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}[+-]\d{2}:\d{2}$", ctx["client_now"])

{webbee-0.3.45 → webbee-0.3.47}/tests/test_session.py

@@ -51,7 +51,10 @@ def test_confirm_default_relays_raw_reply_verbatim():
 def test_build_coding_context_shape(tmp_path):
     (tmp_path / "a.txt").write_text("x")
     ctx = build_coding_context(str(tmp_path))
-    assert set(ctx) == {"cwd", "git", "tree", "repo_key", "repo_root"}
+    # I-CODING-TIME-CONTRACT: client_now/client_tz_label ride every snapshot
+    # (best-effort -- a clock-read failure would simply omit them).
+    assert set(ctx) == {"cwd", "git", "tree", "repo_key", "repo_root",
+                        "client_now", "client_tz_label"}
     assert "a.txt" in ctx["tree"]
 
 

{webbee-0.3.45 → webbee-0.3.47}/tests/test_tui.py

@@ -258,6 +258,42 @@ def test_drag_at_bottom_edge_scrolls_and_grows_selection():
     assert pane._edge_drag == 0
 
 
+def test_repeated_mouse_move_at_same_edge_does_not_double_scroll():
+    # webbee-code-selection-scroll-jitter-v1: a real terminal fires MOUSE_MOVE
+    # repeatedly while the pointer sits at the SAME edge (hand tremor) --
+    # only the FIRST one (the 0 -> armed transition) may scroll immediately;
+    # every following MOUSE_MOVE at the same edge must leave the offset
+    # alone (still armed, still selecting) and let edge_tick() do the only
+    # ongoing scrolling, one steady source instead of two racing.
+    from prompt_toolkit.data_structures import Point
+    from prompt_toolkit.mouse_events import MouseButton, MouseEvent, MouseEventType
+
+    from webbee.tui import OutputPane
+
+    pane = OutputPane(width=80)
+    pane._view_h = 10
+    pane._io.write("\n".join(f"line{i}" for i in range(100)))
+    pane._offset = 0
+
+    down = MouseEvent(position=Point(0, 5), event_type=MouseEventType.MOUSE_DOWN,
+                      button=MouseButton.LEFT, modifiers=frozenset())
+    pane.control.mouse_handler(down)
+
+    move = MouseEvent(position=Point(3, 9), event_type=MouseEventType.MOUSE_MOVE,
+                      button=MouseButton.LEFT, modifiers=frozenset())
+    pane.control.mouse_handler(move)
+    assert pane._offset == 3 and pane._edge_drag == 1   # first touch: one immediate nudge
+
+    # the pointer trembles but stays at the SAME bottom row -- must NOT scroll again.
+    pane.control.mouse_handler(move)
+    pane.control.mouse_handler(move)
+    assert pane._offset == 3 and pane._edge_drag == 1   # unchanged -- no double scroll
+
+    # only edge_tick() advances it further, at its own steady cadence.
+    pane.edge_tick()
+    assert pane._offset == 6
+
+
 def test_edge_drag_resets_on_mouse_up_and_top_edge_mirrors():
     from prompt_toolkit.data_structures import Point
     from prompt_toolkit.mouse_events import MouseButton, MouseEvent, MouseEventType

webbee-0.3.45/src/webbee/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.3.45"