haltija 1.13.0-beta.4 → 1.13.0

package/CHANGELOG.md

@@ -1,5 +1,114 @@
 # Changelog
 
+## 1.13.0 (2026-10-18)
+
+The 1.13 betas, released. Read **Security** and **Upgrading from 1.12** before moving off 1.12.x.
+The beta sections below have the detail and the reasoning; this section is the list. The changes
+made after beta.5 are at the end.
+
+### Security
+
+- **Through 1.12.9, anything on your network could drive your browser.** The server listens on
+  every interface and, without `--token`, answered any machine, `/eval` included. Affected: every
+  release through **1.12.9** (the previous `latest`) and **1.13.0-beta.1 to beta.4**. In 1.13.0 a
+  connection from another machine is refused (403) unless the server has a token (virta #815,
+  GitHub #44; first shipped in beta.5). If you stay on 1.12.x, start the server with `--token
+  <secret>` on any network you don't trust.
+- **Pages on this machine can still call the API, and that is by design.** beta.1 listed this as a
+  known issue with "an origin gate planned before 1.13.0". That gate is not coming: the widget is
+  injected into arbitrary pages, so the REST surface must answer any origin, and an origin check
+  would break exactly the pages haltija exists for. `--token` closes it, as it closes a tunnel or
+  reverse proxy running on this machine (which connects from localhost). The README's Security
+  section says what is and isn't covered.
+
+### Upgrading from 1.12
+
+Each of these changes something that worked before. Before → after:
+
+- **Other machines need a token.** Phones, headsets, other computers, and browsers in a container,
+  VM or WSL2 that reach haltija through a forwarded port: they connected freely, and now get a 403
+  until the server has `--token <secret>` and the client sends it (beta.5).
+- **Both transports by default.** `DEV_CHANNEL_MODE` was `http`; it is `both`, so HTTPS 8701 comes
+  up too. `--http` opts out, and says what that costs other projects (beta.1).
+- **The certificate lives in `~/.haltija/certs`.** It was per-install; an existing one is copied
+  forward, so trust you already granted survives (beta.1).
+- **The desktop app's internal server moved from 8701 to 8710.** `HALTIJA_PORT=8701 hj tree`
+  (inspecting the app's own UI) is now `HALTIJA_PORT=8710 hj tree` (beta.1).
+- **Only the server on 8700 takes HTTPS 8701.** A `--port` / `--name` server's HTTPS is now
+  ephemeral, shown in its banner and `/status`, unless you pass `--https-port` (beta.1).
+- **`server` from `haltija/server` is the HTTP listener**, and `server`, `httpServer` and
+  `httpsServer` are typed `ListeningServer` (`port`, `hostname`, `url`, `stop()`) instead of
+  Bun's server type. Code that used other Bun server methods on them needs a cast (beta.1).
+- **Navigate and refresh wait for the page's widget.** They returned at once; now they block until
+  the widget reconnects, up to `--timeout` (default 10 s). A page that doesn't load the widget
+  itself (a bookmarklet tab) waits that long every time: pass `--no-wait` there. `navigate()` and
+  `refresh()` in `DevChannelClient` / `haltija/test` now return `{ reconnected, warning? }` (beta.2).
+- **The widget writes `window.name` while navigating**, and restores the page's own value after.
+  An app that keeps state in `window.name` can see the marker briefly (beta.2).
+- **`press` acts at the focused element.** In `haltija/test` and `DevChannelClient.press` it was one
+  `keydown` at `body`; now it is the full key sequence at the focused element, like `hj key`
+  (beta.4).
+- **Schematics are drawn by tosijs-floorplan.** Same response fields; the picture looks different
+  (beta.5).
+
+### Fixed after beta.5
+
+From the 1.13.0 release review (`reviews/1.13.0-*.md`):
+
+- **A refused connection from another machine is now logged on the server**, once per address, with
+  the `--token` remedy. A browser cannot read why a WebSocket handshake failed, so a widget in a
+  container or VM retried forever while the server said nothing.
+- **`DevChannelClient` and `haltija/test` send `HALTIJA_TOKEN`.** `hj` and the MCP bridge always
+  did; these two never did, so a test suite could not reach a `--token` server at all, which since
+  beta.5 is the setup for any runner on another machine.
+- **`haltija --token=<secret>` sets a token.** The launcher read only `--token <secret>`, so the `=`
+  form, like a misspelled flag, started a server with no token and no complaint. `--flag=value` now
+  works for every launcher flag that takes a value, an unknown flag is reported, and the banner has
+  an `AUTH:` line saying whether a token is in force.
+- **`/drag`, `hj drag` and the `drag` step move pointer-driven controls.** They sent bare mouse
+  events (some of them `CustomEvent`s with no coordinates), so a slider, resize handle or orbit
+  camera that listens for pointer events didn't move while the drag reported success. They now use
+  the same pointer-and-mouse sequence as `dragFrom`, with `buttons` set while pressed.
+- **MCP setup replaces a stale entry.** Before 1.13 setup wrote `node …/apps/mcp/build/index.js`,
+  which no longer exists. `--check` reported such an entry as configured, and re-running setup said
+  "already configured". Both now call it stale, and setup rewrites it. The help named
+  `npx haltija-mcp-setup`, a package that does not exist; it is `npx -p haltija haltija-mcp-setup`.
+- **The `test:integration` lane runs its tests.** It needed a server it was never given, so every
+  1.13 beta attested "0 pass, 11 skip" as a pass. It now starts its own private headless instance,
+  and a lane that only skipped fails.
+- Docs: the README no longer shows a demo image that doesn't exist, and links the API reference and
+  the browser-test guide (`docs/TEST-IN-BROWSER.md`).
+
+## 1.13.0-beta.5 (2026-10-18)
+
+### Changed
+
+- **Schematics are drawn by tosijs-floorplan** (virta #873). `hj map --image`, `hj screenshot
+  --schematic` and the no-capture fallback used haltija's own ~600-line renderer. haltija now emits
+  floorplan's record format and floorplan draws it, so haltija and tosijs share one renderer and one
+  affordance grammar. The response is unchanged: same fields, same `legend`, and refs still drawn as
+  dark pills. What looks different: captions show content instead of tag names (`Place order`, not
+  `@18 button Place order`), long text wraps to the box, checkboxes and radios are drawn as
+  geometry, an editable region wears a `↔` badge, and findings are short coloured bars on the left
+  edge (`contrast 1.1:1`, `target 16x16`) with the full text in the legend. A map with no geometry,
+  or `layout: 'structural'`, is still drawn as stacked boxes by haltija, since floorplan draws only
+  what has bounds. The widget is about 3 KB larger gzipped.
+- **Page text can no longer pose as a binding** (virta #816). In the record format, `text ⟷ path`
+  means "two-way bound to path", and haltija copied page text into its map verbatim, so a page
+  could make its own text read as a writable binding. The `⟷` and `⟵` arrows in page text, labels,
+  values and placeholders now become `<->` and `<-` as the map is built. Link destinations are kept
+  verbatim.
+- **Without `--token`, haltija refuses connections from other machines** (virta #815, GitHub #44).
+  The server listens on every interface, and anything on your network could drive your browser,
+  `/eval` included, unless you had thought to pass `--token`. Now a request or socket whose peer
+  address is not loopback gets a 403 that says to restart with `--token`. Same-machine use is
+  unchanged. To keep using haltija from another device (a phone, a headset, a second computer), start
+  it with `--token <secret>` and send the token as before. The check uses the connection's address,
+  never a header the caller writes.
+  - What it does not change, now said plainly in the README: a page you visit on this machine can
+    still call the API (the widget's whole job), and a tunnel or reverse proxy on this machine
+    connects from localhost, so it counts as local. Use `--token` for either.
+
 ## 1.13.0-beta.4 (2026-10-17)
 
 ### Added

package/README.md

@@ -8,9 +8,6 @@
 
 Unlike screenshot-based tools, Haltija works with the actual DOM. Unlike Playwright, it connects to your real browser — already logged in, same cookies, same bug you're looking at.
 
-<!-- TODO: Replace with actual GIF showing: 1) bunx haltija launches app, 2) agent queries tree, 3) agent clicks something, 4) highlight shows result -->
-![Haltija in action](docs/assets/demo.gif)
-
 > *Haltija* (Finnish): a guardian spirit that watches over a place. In this case, your DOM.
 
 ---
@@ -333,10 +330,18 @@ app also exists but isn't required for either.
 
 - Widget is always visible (no silent snooping)
 - User can pause or kill connection anytime
-- **Not localhost-only.** The server listens on all interfaces (HTTP 8700 and HTTPS 8701 by
-  default), and without `--token` any page you visit, or anything on your network, can call its
-  REST API — including `/eval` in your connected tabs. Use `--token <secret>` (or
-  `HALTIJA_TOKEN`) on any network you don't trust, and don't leave a server running you aren't
+- **Other machines need `--token`.** The server listens on all interfaces (HTTP 8700 and HTTPS
+  8701 by default), but without a token it refuses every connection that doesn't come from this
+  machine. To use haltija from another device (a phone, a headset, a second computer), start it
+  with `--token <secret>` (or `HALTIJA_TOKEN`) and send the same value as `X-Haltija-Token`,
+  `?token=`, or the widget's `token` option. A browser in a container, VM or WSL2 that reaches
+  haltija through a forwarded port also counts as another machine. The server's terminal names
+  each refused address once.
+- **On this machine, any page you visit can call it.** The widget is injected into arbitrary
+  pages, so the REST API answers any origin, `/eval` in your connected tabs included. That is by
+  design for a local dev tool, and `--token` closes it too. A tunnel or reverse proxy on this
+  machine (ngrok, cloudflared, `ssh -R`) connects from localhost and so counts as this machine:
+  if you expose haltija through one, pass `--token`. Don't leave a server running you aren't
   using.
 - Machine-level HTTPS certificate in `~/.haltija/certs`, auto-generated (mkcert if installed,
   otherwise openssl) and renewed before it expires
@@ -405,10 +410,11 @@ hj api                        # Full API reference (markdown)
 hj --help                     # CLI subcommand reference
 ```
 
-- [Full API Reference](./API.md) (auto-generated from schema)
+- [Full API Reference](https://github.com/tonioloewald/haltija/blob/main/API.md) (auto-generated from schema)
 - [Agent Prompt](docs/agent-prompt.md) — Copy-paste prompt for any AI agent
 - [Recipes](docs/recipes.md) — Common workflows
 - [CI Integration](docs/CI-INTEGRATION.md) — E2E testing with Haltija in GitHub Actions
+- [Browser tests from your test runner](docs/TEST-IN-BROWSER.md) — `createBrowserPage` from `haltija/test`: assertions on the host, probes in a real browser
 - [Roadmap](docs/ROADMAP.md)
 
 ---

package/apps/desktop/package.json

@@ -1,6 +1,6 @@
 {
   "name": "haltija-desktop",
-  "version": "1.13.0-beta.4",
+  "version": "1.13.0",
   "private": true,
   "description": "Haltija Desktop - God Mode Browser for AI Agents",
   "homepage": "https://github.com/tonioloewald/haltija",