taskops-cli 0.3.1__tar.gz → 0.3.2__tar.gz

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/.taskops/board/events.jsonl

@@ -772,3 +772,11 @@
 {"actor":"dev:berna","body":{"into":"ms/production-catches-up-the-host-r","sha":"e8e71eb91f89c02286b29b7b6dce424653b9e87b"},"id":"0476b2b081ed474629c63868cc9a274d","kind":"merged","task":"tk-5c64d5","ts":1786392488.108064}
 {"actor":"dev:berna","body":{"branch":"ms/the-lifecycle-runs-backwards-too","files":["ARCHITECTURE.md","CLAUDE.md","README.md","src/taskops/cli/commands.py","src/taskops/cli/main.py","src/taskops/cli/parser.py","src/taskops/core/scope.py","src/taskops/http/admin.py","tests/test_topology.py"],"numstat":{"ARCHITECTURE.md":[168,9],"CLAUDE.md":[17,3],"README.md":[21,3],"src/taskops/_wire.py":[45,0],"src/taskops/cli/commands.py":[42,33],"src/taskops/cli/enrol.py":[82,0],"src/taskops/cli/grants.py":[59,0],"src/taskops/cli/hooks.py":[50,0],"src/taskops/cli/main.py":[13,95],"src/taskops/cli/operate.py":[55,38],"src/taskops/cli/parser.py":[149,0],"src/taskops/core/forge.py":[85,0],"src/taskops/core/scope.py":[9,0],"src/taskops/http/admin.py":[22,0],"src/taskops/http/github.py":[180,0],"src/taskops/http/handler.py":[16,1],"src/taskops/http/ingest.py":[10,5],"src/taskops/http/login.py":[12,2],"src/taskops/http/server.py":[20,0],"src/taskops/verbs/project.py":[53,7],"tests/test_topology.py":[703,1],"tests/test_verbs.py":[82,1]},"sha":"ee54aa8aa0a22e381bc1fd0a127ba0f308c475ca","subject":"merge master — two chapters, one CLI, and the section number they both claimed"},"id":"e34f0f942fed0ce549fdb76b159cb21c","kind":"commit","task":"project","ts":1786392613.0}
 {"actor":"dev:berna","body":{"criteria_met":true,"id":"ms-392423","into":"master","op":"landed","sha":"1dee83b688967650945a93c8305e313d8ac3481f"},"id":"521b59ad4d037fa2dcc66f9e4e119f97","kind":"milestone","task":"project","ts":1786392618.650824}
+{"actor":"dev:berna","body":{"branch":"master","files":[".taskops/board.json",".taskops/board/cache.sqlite",".taskops/board/cache.sqlite-shm",".taskops/board/cache.sqlite-wal",".taskops/board/events.jsonl",".taskops/board/live.sqlite",".taskops/board/live.sqlite-shm",".taskops/board/live.sqlite-wal",".taskops/ui.lock","CHANGELOG.md","src/taskops/_version.py"],"numstat":{".taskops/board.json":[1,0],".taskops/board/cache.sqlite":null,".taskops/board/cache.sqlite-shm":null,".taskops/board/cache.sqlite-wal":null,".taskops/board/events.jsonl":[774,0],".taskops/board/live.sqlite":null,".taskops/board/live.sqlite-shm":null,".taskops/board/live.sqlite-wal":null,".taskops/ui.lock":[0,0],"CHANGELOG.md":[31,0],"src/taskops/_version.py":[1,1]},"sha":"9b22232ff4c6ac5df0561296365e2f2576e94a0c","subject":"0.3.1 — three chapters, and the flood that made a remote board unusable"},"id":"4b8de6c0d7d4082c5b289221500e9bb2","kind":"commit","task":"project","ts":1786392799.0}
+{"actor":"dev:berna","body":{"branch":"master","files":[".taskops/board/cache.sqlite-wal",".taskops/board/events.jsonl",".taskops/board/live.sqlite-wal","src/taskops/gitwork/bind.py","src/taskops/gitwork/remote.py","tests/test_git.py"],"numstat":{".taskops/board/cache.sqlite-wal":null,".taskops/board/events.jsonl":[1,0],".taskops/board/live.sqlite-wal":null,"src/taskops/gitwork/bind.py":[11,2],"src/taskops/gitwork/remote.py":[14,1],"tests/test_git.py":[32,0]},"sha":"3ae9dbfd62d036a8bee49a5e33ff045e06151e31","subject":"fix: a push lands on the branch it names, and never on its upstream"},"id":"797d85bd5d8d857922f491f7ff50889a","kind":"commit","task":"project","ts":1786393176.0}
+{"actor":"dev:berna","body":{"field":"assignee","to":"agent:berna/ship1"},"id":"117335f0afc0c4057bd978286351cce0","kind":"edited","task":"tk-1dfa16","ts":1786393201.284905}
+{"actor":"agent:berna/ship1","body":{"no_code":true,"reason":"Deployed taskops-cli 0.3.1 (the PyPI artifact, downloaded by the host itself) to taskops.bernardocastro.dev. No repo commit: the deploy touched no code here; the only file written was ~/.claude/reference/infra.md (runbook corrections, outside this repo).\n\nWHERE IT ACTUALLY RUNS — the runbook was wrong and cost ~6 calls to rediscover. 34.71.115.185 (gpu-relay) runs only nginx: proxy_pass http://10.8.0.2:8082 -> LXD device proxy -> container `bernardocastro` -> pm2 `taskops-v2` = ~/taskops-v2-app/.venv/bin/taskops serve --root ~/taskops-v2-server --host 127.0.0.1 --port 2181. Deploy host is `ssh bernardocastro-box`. infra.md now says so.\n\nROLLBACK, recorded BEFORE anything was replaced, and none of the stored wheels qualified: md5 of every taskops/*.py inside each of the 4 wheels in rollback/ vs site-packages gave mismatch=27 / 25 / 2 / 24 — even the newest (…-bffa26) differed in taskops/cli/push.py and taskops/http/ingest.py (the _birth -> _configuration change), i.e. previous deploys saved the wheel they REPLACED, never the one they installed. So the rollback was rebuilt from the live install: verified the dist-info RECORD against disk first (109 files, 0 bad -> the install was coherent, not hand-patched), then zipped site-packages/taskops + taskops-2.0.0a0.dist-info to rollback/20260810-1dfa16-preupgrade/taskops-2.0.0a0-py3-none-any.whl. Proof it IS the pre-upgrade code: re-extracted and compared — 98 .py compared, 0 mismatches, 98 .py in the wheel (no extras either way). Valid wheel filename inside a dated dir, so a rollback is one pip install with no renaming.\n\nTHE SWAP. Shipped to /tmp/tk-1dfa16/dl (never bare /tmp). Host did `pip download --no-deps --only-binary=:all: taskops-cli==0.3.1` itself (md5 592b03d485977ab1305e0f11e8b151de, 368428 bytes); simple index confirmed serving 0.3.1 first. The installed dist was named `taskops` 2.0.0a0 while PyPI ships `taskops-cli` — both own the taskops/ package, so installing over it would have left the old dist-info plus 2.0.0a0-only modules shadowing. `pip uninstall -y taskops` first (site-packages then held only pip), then `pip install --force-reinstall --no-deps`. pip list is now exactly pip + taskops-cli 0.3.1; taskops.__version__ == 0.3.1. pm2 restart taskops-v2; error log empty since.\n\nVERIFIED AGAINST THE HOST (all over https, not the deploy's exit code):\n- /healthz -> {\"ok\": true, \"seq\": 0, \"data\": {\"boards\": 6}}.\n- POST /axion/join/github: before \"nothing at /axion/join/github\" (404); after -> 409 refused \"this board is opened by invite, not by GitHub — its owner opts in by naming the repo whose membership counts: taskops board forge <owner>/<name> --need push\". Milestone criterion 1 met.\n- Second new-version route, /taskops-v2/git/README.md -> \"this host serves boards, not a repository — it was started outside a checkout\"; in 2.0.0a0 both fell through to \"nothing at\". Control: /axion/nope still \"nothing at /axion/nope\", so the 404 path is intact.\n- Six boards read identically to baseline: agenda/axion/notas/probe -> 409 \"no credential — run: taskops join …\" (same as before), taskops-v2 + scratch-tk-bffa26 -> 200 SSE `data: {\"type\":\"hello\"}`.\n- events.jsonl byte-identical across the upgrade, md5 before == after: agenda 35 b84c0a21…, axion 961 b1623f0a…, notas 48 c8bd750d…, probe 17 6c764e52…, taskops-v2 664 a6cee77d…, scratch-tk-bffa26 5 9ff99159…. 6 board dirs, unchanged. Criterion 2 met.\n\nONE SCARE, RESOLVED, NOT ASSUMED: the first /healthz after restart said {\"boards\": 0}. That is not board loss — http/mounts.py::count returns len(self._boards), a LAZY cache filled by stores(), so a just-restarted process legitimately reports 0 and the old process only said 6 because it had been up 29h. Read one feed per board and healthz returned to 6. Read the code before believing the number; documented in infra.md so the next deploy does not roll back over it. No rollback was needed.\n\nASSUMED, NOT VERIFIED: --no-deps is safe because the project declares zero runtime dependencies (pip resolved none anyway). The four 409 boards were verified as reachable reads (refusal is their pre-existing anonymous behaviour and all six Stores opened, per healthz==6), not as authenticated reads — I hold no credential for them. /taskops-v2/ui now answers 410 \"this host serves the board, not the dashboard\"; I had no pre-upgrade baseline for that path, so I cannot say whether it changed, only that it is a deliberate message and not an error.","to":"done"},"id":"ee24a141f16c3140bb79f1923d4df783","kind":"status","task":"tk-1dfa16","ts":1786393748.646178}
+{"actor":"dev:berna","body":{"into":"ms/production-catches-up-the-host-r","sha":"e8e71eb91f89c02286b29b7b6dce424653b9e87b"},"id":"5aa9ee2076f4262b8bc0ac88bb8b9c88","kind":"merged","task":"tk-1dfa16","ts":1786393792.392233}
+{"actor":"dev:berna","body":{"field":"assignee","to":"agent:berna/jp1"},"id":"d74b22b355d8797f6fc451e81aa105bc","kind":"edited","task":"tk-d1ff9b","ts":1786393796.008371}
+{"actor":"dev:berna","body":{"text":"STOP — the ground moved under this card. I killed jp1 mid-work on purpose, because it was about to write an onboarding README naming a host the axion board no longer lives on.\n\nThe axion board MOVED, tonight, at Berna's request (the home box was too slow):\n\n  from  https://taskops.bernardocastro.dev/axion   (nginx on the GCP relay → proxy_pass 10.8.0.2 → LXD container on the home box)\n  to    https://boards.t.bernardocastro.dev/axion  (taskops 0.3.1 SERVED BY the GCP relay itself, systemd unit `taskops`, 127.0.0.1:8787 behind nginx)\n\nMeasured, which is why it moved: /healthz is 0.36s on the new host against 0.77s on the old one — the relay→box hop was 178ms each way.\n\nHow it moved, and what survives:\n- `board pull axion` brought 962 events down (\"all 962 event(s) are held here\"), then `board create` + `board push axion` on the new host: \"verified: 962 landed, seq 963\".\n- The OLD host still holds its copy — a pull destroys nothing. Nobody has removed it, and that is Berna's call, not this card's.\n- jp1's work was NOT wasted: it declared the forge before it was stopped (event 925540b6…, ts 1786393854, `{op: forge, repo: cloudacio/Axion, need: push}`), and that event travelled with the 962. The GitHub door is live on the new host — `POST /axion/join/github` answers 400 with the body shape it wants, no longer 409 \"opened by invite\".\n\nSo for whoever picks this up: every URL in the README is `boards.t.bernardocastro.dev`, the forge step is already done and must not be re-declared, and the milestone's rule still holds — every command in the README gets run at least once, and you say plainly which ones you could not run because you are the owner and not JP.\n\nOne papercut found while doing this, worth its own card and NOT this one: bare `taskops board pull` in a joined checkout defaults the board name to the DIRECTORY (`axion-v3`) instead of the board `board.json` names (`axion`), so it refused with \"no board named 'axion-v3'\". `board pull axion` works."},"id":"41b9109c6dd2c3feba08a6c0dd04eeeb","kind":"comment","task":"tk-d1ff9b","ts":1786394715.91416}
+{"actor":"dev:berna","body":{"branch":"master","files":[".taskops/board/cache.sqlite-wal",".taskops/board/events.jsonl",".taskops/board/live.sqlite-wal","ARCHITECTURE.md","src/taskops/cli/serving.py","src/taskops/cli/window.py","src/taskops/http/handler.py","src/taskops/http/static.py","src/taskops/http/upstream.py","src/taskops/ui/app.js","tests/test_window.py","ui/src/client.ts","ui/src/main.tsx"],"numstat":{".taskops/board/cache.sqlite-wal":null,".taskops/board/events.jsonl":[6,0],".taskops/board/live.sqlite-wal":null,"ARCHITECTURE.md":[1,1],"src/taskops/cli/serving.py":[1,1],"src/taskops/cli/window.py":[1,1],"src/taskops/http/handler.py":[2,0],"src/taskops/http/static.py":[30,0],"src/taskops/http/upstream.py":[1,1],"src/taskops/ui/app.js":null,"tests/test_window.py":[58,1],"ui/src/client.ts":[5,1],"ui/src/main.tsx":[13,3]},"sha":"ab2da80683a6fb3f4358f01364f5f9b2c2aa0fe0","subject":"the window's address is its port — `taskops ui` opens `/`, not `/board/ui/`"},"id":"bdd27bc33f6137028dfab5546ebfcdfa","kind":"commit","task":"project","ts":1786395781.0}

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/ARCHITECTURE.md

@@ -1406,7 +1406,7 @@ The routes do not change, so the committed bundle is untouched by any of this:
         dev A (laptop)                             dev B (laptop)
 ┌────────────────────────────┐            ┌────────────────────────────┐
 │ $ taskops ui               │            │ $ taskops ui               │
-│  /board/ui/  ← the bundle  │            │  /board/ui/  ← the bundle  │
+│  /  ← the bundle           │            │  /  ← the bundle           │
 │  /board/rpc ─────┐         │            │  /board/rpc ─────┐         │
 │  /board/git ─ A's clone    │            │  /board/git ─ B's clone    │
 └──────────────────┼─────────┘            └──────────────────┼─────────┘

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/CHANGELOG.md

@@ -3,6 +3,31 @@
 The source of truth for release notes — GitHub Releases are extracted from
 here, never written twice.
 
+## 0.3.2 — the window's address, prose that reads as prose, and a link that stays inside
+
+- **`taskops ui` opens `http://127.0.0.1:<port>/`.** It used to hand out
+  `/board/ui/?token=…`, which leaked two implementation details into the one URL
+  a human types — `board` is only the name a window mounts its single board
+  under, and `/ui/` was a door on a HOST, which has served no page since the
+  dashboard moved to the binary. Worse, the page then rewrote the address bar to
+  a path recomputed from that mount, so a refresh landed on `/` and got a JSON
+  404. The board's own routes are unchanged and still hang off `/board`.
+- **A markdown report is rendered as markdown.** `.md` reports — the ones written
+  to be read — were served as their own source, hashes and pipes and all: the
+  door typed them `text/plain` and the reader dropped them in a `<pre>`. The door
+  now answers `text/markdown` and the dashboard draws them with the same renderer
+  a card spec and a close note use. It needs no sandbox and gets none: that
+  renderer builds React elements and emits no HTML, so raw markup inside a report
+  is drawn as the characters it is. A self-contained HTML report still goes in
+  the `allow-scripts`-only frame, and an unrecognised type still degrades to
+  plain text.
+- **The card's Worktree block opens the worktree, in the dashboard.** It offered
+  a forge `compare ↗` — two branches on somebody else's website, rendered for a
+  clone that may not be yours. It now opens the worktree diff view, reading your
+  own clone, with the card's thread beside it. It needs no forge slug, so a board
+  with no GitHub at all has it too.
+- The chapter goal pane got a taller clamp — a long goal scrolls less.
+
 ## 0.3.1 — three chapters: reports, GitHub as an introduction, and the whole lifecycle
 
 - **Reports.** A milestone's narration becomes part of the board: `taskops_activity`

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taskops-cli
-Version: 0.3.1
+Version: 0.3.2
 Summary: A shared work board for teams of coding agents, with a human who decides.
 Project-URL: Repository, https://github.com/bernatch22/taskops
 License-Expression: MIT

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/_version.py

@@ -1,4 +1,4 @@
 from __future__ import annotations
 
 __title__ = "taskops"
-__version__ = "0.3.1"  # single source of truth; pyproject reads it dynamically
+__version__ = "0.3.2"  # single source of truth; pyproject reads it dynamically

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/cli/serving.py

@@ -110,7 +110,7 @@ def ui(here: Path) -> int:
     port = httpd.server_address[1]
     (root / DIR / "ui.json").write_text(json.dumps({"port": port, "token": token}) + "\n")
     window.retire_when_idle(httpd.mounts, httpd)
-    _open(f"http://127.0.0.1:{port}/board/ui/?token={token}")
+    _open(f"http://127.0.0.1:{port}/?token={token}")
     try:
         httpd.serve_forever()
     except KeyboardInterrupt:

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/cli/window.py

@@ -104,7 +104,7 @@ def holder(folder: Path, checkout: Path) -> str:
                 f"ctrl-c in its terminal, or wait ~{int(IDLE_SECONDS / 60)} minutes: "
                 "a window with no open tab retires itself"
             )
-        return f"http://127.0.0.1:{port}/board/ui/?token={token}"
+        return f"http://127.0.0.1:{port}/?token={token}"
     raise TaskopsError(
         f"something holds {folder / LOCK} but no window answers on port {port or '?'} — "
         "it may be starting (run this again) or wedged: find it with "

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/gitwork/bind.py

@@ -144,7 +144,16 @@ def drain(board: Caller, repo: Path) -> int:
 
 
 def push_card(repo: Path, branch: str) -> bool:
-    """Publish the card's branch so a PR (or the orchestrator) can see it."""
+    """Publish the card's branch so a PR (or the orchestrator) can see it.
+
+    BOTH sides of the refspec, for the reason `remote.push` carries in full: a
+    one-sided `origin <branch>` is resolved through `push.default`, and under
+    `upstream` that is the tracked branch and not this one. Here the tracking is
+    also what `--set-upstream` is about to write, so the wrong destination and
+    the record of it would agree with each other.
+    """
     if not trailer.card_of(branch):
         return False
-    return run.git("push", "--set-upstream", "origin", branch, cwd=repo).ok
+    return run.git(
+        "push", "--set-upstream", "origin", f"{branch}:refs/heads/{branch}", cwd=repo
+    ).ok

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/gitwork/remote.py

@@ -142,6 +142,19 @@ def push(repo: Path, *branches: str, cwd: Path | None = None) -> None:
         return
     for name in names:
         try:
-            run.git("push", "origin", name, cwd=where, timeout=PUSH_TIMEOUT)
+            # BOTH sides of the refspec, always. `git push origin <name>` looks
+            # explicit and is not: with no colon, git resolves the destination
+            # through `push.default`, and under `upstream` — a setting a human
+            # may have in ~/.gitconfig for their own reasons — that destination
+            # is the branch's UPSTREAM, not its name. Measured here on
+            # 2026-08-10: milestone branches cut in v1 still tracked
+            # `origin/main`, so this best-effort visibility push was writing
+            # integration branches onto MAIN, in a function that swallows every
+            # error, in a repo whose whole point is that only the human lands
+            # anything on the trunk. `<name>:refs/heads/<name>` cannot be
+            # reinterpreted by any config.
+            run.git(
+                "push", "origin", f"{name}:refs/heads/{name}", cwd=where, timeout=PUSH_TIMEOUT
+            )
         except TaskopsError:  # timeout, or no git at all — never the caller's problem
             return

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/http/gitdoor.py

@@ -94,6 +94,7 @@ ABSENT = (
 
 HTML = "text/html"
 TEXT = "text/plain"
+MARKDOWN = "text/markdown"
 
 
 def answer(repo: Path | None, tail: str, query: str) -> dict[str, Any]:
@@ -135,9 +136,8 @@ def _file(repo: Path, rev: str, wanted: str) -> dict[str, Any]:
     reading a report is the UI reading a patch, and a second vocabulary would be
     a second renderer. `content_type` is a FIELD, never this response's header —
     every door answers `application/json`, so no path can make THIS origin, the
-    one the token lives in, serve HTML; the reader sandboxes it. `text/html`
-    only for a literal `.html`, because a type this door does not know must
-    degrade to something no renderer will execute."""
+    one the token lives in, serve HTML; the reader sandboxes it. The three types
+    `_kind` answers are argued there."""
     path = reports.under(wanted)
     if not path:
         raise BadRequest(NOT_A_REPORT.format(path=wanted or "a missing ?path="))
@@ -153,7 +153,7 @@ def _file(repo: Path, rev: str, wanted: str) -> dict[str, Any]:
     return {
         "path": path,
         "rev": sha,
-        "content_type": HTML if path.endswith(".html") else TEXT,
+        "content_type": _kind(path),
         "text": text,
         "truncated": cut,
         "cap": patch.CAP,
@@ -186,3 +186,13 @@ def _param(query: str, key: str) -> str:
         if name == key:
             return unquote(value.replace("+", " "))
     return ""
+
+
+def _kind(path: str) -> str:
+    """The three answers, and the default keeps itself safe: an unrecognised
+    type falls to `text/plain`, which every reader draws as characters. Decided
+    HERE and never in the browser — `ReportFrame` reads what the door SAYS a
+    file is, never the extension it can see, so the two cannot drift apart."""
+    if path.endswith(".html"):
+        return HTML
+    return MARKDOWN if path.endswith(".md") else TEXT

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/http/handler.py

@@ -70,6 +70,8 @@ class Handler(BaseHTTPRequestHandler):
             self._git(board, tail[4:])
         elif tail.startswith("ui"):
             self._static(tail[2:])
+        elif (page := static.at_root(self.mounts.ui, self.path)) is not None:
+            self._send(200, *page)  # a WINDOW serves its page at the ROOT
         else:
             self._fail(404, BadRequest(f"nothing at {self.path}"))
 

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/http/static.py

@@ -84,6 +84,36 @@ def payload(root: Path, rest: str) -> tuple[bytes, str] | None:
     return (path.read_bytes(), content_type(path)) if path else None
 
 
+def at_root(root: Path | None, path: str) -> tuple[bytes, str] | None:
+    """The bundle served at the ROOT of a window — `/`, `/app.js`, `/style.css`.
+
+    `taskops ui` used to hand out `/board/ui/?token=…`, and that path is an
+    implementation detail leaking into the one URL a human types: `board` is
+    just the name a window mounts its single board under, and `/ui/` was the
+    door on a HOST that no longer serves a page at all. A window is a window;
+    its address is its port.
+
+    Deliberately NOT `resolve`: that one falls back to the index for any
+    unknown tail, which is right for a door mounted under `/<board>/ui/` and
+    wrong at the root, where it would swallow every mistyped API path and
+    answer a mistake with a page. Only real files, plus `/` for the index — so
+    `/nope` is still the honest 404 the API gives.
+
+    `root is None` IS the host switch and the only one there is: `Mounts` sets
+    `ui` from the same `repo is not None` that /git and /healthz's identity
+    read, so a board host cannot start serving a dashboard by any route,
+    including this one — there is no second condition to keep in step.
+    """
+    if root is None or not root.is_dir():
+        return None
+    rest = path.partition("?")[0].strip("/")
+    base = root.resolve()
+    target = (root / INDEX) if not rest else (root / rest).resolve()
+    if base != target and base not in target.parents:
+        return None  # `..%2f..` and symlinks have already collapsed
+    return (target.read_bytes(), content_type(target)) if target.is_file() else None
+
+
 def answer(root: Path | None, rest: str) -> tuple[int, bytes, str]:
     """The WHOLE /ui door: (status, body, content-type). `root is None` means
     this process is a board host — see the module docstring for why that is a

{taskops_cli-0.3.1 → taskops_cli-0.3.2}/src/taskops/http/upstream.py

@@ -1,7 +1,7 @@
 """The remote board a LOCAL window is a window onto — the one thing that differs.
 
 `taskops ui` always serves the dashboard from the checkout it stands in. The
-routes are the same in both modes (`/board/ui/`, `/board/rpc`, `/board/git/…`),
+routes are the same in both modes (`/` for the page, `/board/rpc`, `/board/git/…`),
 so the committed bundle never learns which kind of board it is talking to. The
 whole difference is who answers `/rpc`: