taskops-cli 0.5.2__tar.gz → 0.5.4__tar.gz

{taskops_cli-0.5.2 → taskops_cli-0.5.4}/ARCHITECTURE.md

@@ -1526,9 +1526,16 @@ below — and comes back only standing on a real history: the forge mirror, in
 That cascade is ONE function — `ui/src/links.tsx::cascade`, beside the slug and
 the link templates it already owned — and `ui/src/components/card/Patch.tsx`
 only DRAWS the step it is handed, so no component holds a fallback order of its
-own. It feeds the dossier's **Files changed** (the card as a PR:
-`compare/ms/<slug>...tk-<id>`, the file list from `stat`, each file's patch on
-expand via `?path=`) and the fold on every commit row. Availability is
+own. It feeds the dossier's **Files changed** (the card as a PR, over the range
+the BOARD recorded rather than two branch names — `links.tsx::cardRange`: one
+recorded commit goes through `commit/<sha>`, which the door diffs against its
+first parent, and several become `compare/<first>^...<last>`, whose base is the
+oldest commit's PARENT so that commit's own changes are inside the range. Both
+ends are durable, which is what makes the pane render for a card whose `tk-*`
+and `ms/*` branches were pruned before this host became the remote — the head
+alone was not enough, 0.5.2 shipped that and the pane stayed empty. Then the
+file list from `stat`, each file's patch on expand via `?path=`) and the fold on
+every commit row. Availability is
 DISCOVERED, not configured: the first refusal whose words are
 `gitdoor.py::NO_REPO` flips a module-level flag for the session and nothing asks
 again — an unknown ref does not flip it, because that means "ask again for
@@ -1542,6 +1549,10 @@ effect firing, and that half is covered against a real server in
 chapter): `pages/WorktreeDiff.tsx`, the full-width page a Worktrees row opens,
 hands its whole range `<milestone branch>...tk-<id>` to the very same
 `FilesChanged` — plus a summary bar, which is a prop on it and not a second ask.
+Two live BRANCHES there, deliberately, where the dossier asks by sha: that page's
+subject is a working tree that exists on disk right now, so where its two tips
+stand IS the question. `FilesChanged` therefore takes a whole `GitTarget` rather
+than a base/head pair — a pair could only ever express the second question.
 Nothing else moved to do that: **no verb, no stored key, no change to the door**,
 and no component fetches a patch outside `cascade()`. The one seam this cost is
 `FileList` exported beside `FilesChanged` — the pure half, given a step — for

{taskops_cli-0.5.2 → taskops_cli-0.5.4}/CHANGELOG.md

@@ -3,6 +3,43 @@
 The source of truth for release notes — GitHub Releases are extracted from
 here, never written twice.
 
+## 0.5.4 — the Files-changed pane renders for a landed card
+
+**0.5.3 is withdrawn in all but name.** It carries this release's source fix but
+the PREVIOUS release's committed UI bundle, so a hosted page served by it still
+asks for branch names and the pane stays empty. The cause is worth writing down:
+the version bump, the changelog and the tag were made while the shell was still
+inside a card's worktree after a conflict resolution, so `v0.5.3` points at that
+card's branch — which holds `links.tsx::cardRange` but not the chapter-closing
+rebuild of `src/taskops/ui/app.js`. Every gate passed there, because that tree
+was internally consistent; what was missing was the rest of the chapter. A
+release is cut from the trunk, and the check that catches this is comparing the
+bundle a host SERVES against the one the tag committed — which is now a deploy
+step, not a habit.
+
+- **The pane asked for two branch names, and a landed card has neither.**
+  0.5.2 made the HEAD durable — the card's newest recorded sha instead of its
+  branch — and stopped there. The BASE stayed the chapter's branch name, and for
+  every card that landed before this host became the board's remote that branch
+  was pruned on the forge, so the compare refused and the pane was empty while
+  the commits sat in the trunk. Reported live on tk-bffa26 and tk-c37061.
+- **The range now comes from the card's own commits, both ends**
+  (`ui/src/links.tsx::cardRange`): one recorded commit goes through the commit
+  door, which already diffs a commit against its first parent; several become
+  `compare/<oldest>^...<newest>`. The base is the oldest commit's PARENT, not
+  the oldest commit — `git diff` is exclusive of its base, so
+  `<oldest>...<newest>` answers 200 with that commit's own changes silently
+  missing, which is a pane that looks complete and is not. No server change was
+  needed: `<sha>^` already passed the ref shape and resolves through `^{commit}`.
+- **Pinned where it broke.** The pane renders the route it asked for and a smoke
+  section reads that route off the rendered component — the previous attempt was
+  pinned one layer below the call site, so a call-site mutation went green while
+  the pane stayed broken. `smoke.sh` derives the same route from the LIVE card
+  payload and asserts the first commit's files are in the answer.
+- **"so them was never pushed here"** — the host's missing-ref refusal had a
+  plural substitution in a subject slot. The number now runs through the whole
+  sentence, and both forms are pinned as bytes.
+
 ## 0.5.2 — the host holds the git; GitHub is the copy
 
 0.5.0 and 0.5.1 built the hosted window on a mirror the host PULLED from the

{taskops_cli-0.5.2 → taskops_cli-0.5.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: taskops-cli
-Version: 0.5.2
+Version: 0.5.4
 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.5.2 → taskops_cli-0.5.4}/smoke.sh

@@ -15,7 +15,7 @@
 # (`tests/test_topology.py`), against a host it created.
 #
 #   sh smoke.sh                                  # the author's host, defaults below
-#   sh smoke.sh <host> <public-board> <private-board> <card-branch> <landed-branch>
+#   sh smoke.sh <host> <public-board> <private-board> <card-branch> <landed-card> <reported-card>
 #
 # Every assertion is here because it FAILED once, in production, against a real
 # reader — the comment above each one says which report it comes from. Nothing
@@ -37,6 +37,10 @@ BRANCH=${4:-tk-32d2ba}
 # the fault that turned the pull mirror inside out (§16, 2026-08-31). The host
 # holds the history now and never prunes, so this ref must answer forever.
 LANDED=${5:-tk-dfaff7}
+# The card the Files-changed pane was reported blank on (2026-08-31): two
+# recorded commits, so it exercises the RANGE arm of the rule below, not the
+# single-commit door.
+REPORTED=${6:-tk-bffa26}
 
 BASE="https://$HOST"
 C="curl -sS -m 15"
@@ -228,18 +232,74 @@ code=$(printf %s "$got" | sed -n '1s/[^ ]* \([0-9][0-9]*\).*/\1/p')
   "HTTP $code — a private board is not world-clonable"
 pass "GET /$PRIVATE/repo.git upload-pack (anonymous)" "HTTP 401"
 
-# ── (h) a LANDED card still renders its diff ─────────────────────────────────
-# Reported 2026-08-31 against the pull mirror, and the reason this chapter
-# exists: `tk-dfaff7`'s branch was pruned on the forge when its chapter landed,
-# so the board — whose git was a --mirror of the forge — lost the diff of work
-# that is intact in the trunk. The host holds the history now and refuses ref
-# deletions, so this URL must answer for the life of the board.
-head_ln "a card whose branch was pruned on the forge"
-body=$($C "$BASE/$BOARD/api/git/commit/$LANDED") || fail "GET git/commit/$LANDED" "no answer"
-case $body in
-  *'"patch"'*) pass "GET /$BOARD/api/git/commit/$LANDED" \
-    "a diff ($(printf %s "$body" | wc -c | tr -d ' ') bytes)" ;;
-  *) fail "GET git/commit/$LANDED" "no diff: $(printf %s "$body" | head -c 300)" ;;
-esac
+# ── (h) the Files-changed pane's OWN range, for the two reported cards ───────
+# This section REPLACES the one that asked `git/commit/<the landed card's branch
+# name>` (written 2026-08-30 for the pull mirror). That assertion is not
+# recoverable and must not come back: `tk-dfaff7`'s branch was pruned on the
+# forge before this host became the board's remote, so the ref was never pushed
+# here and the host — which prunes nothing — has nothing to serve under that
+# name. Asking a landed card for its BRANCH was the fault itself, in the smoke
+# as much as in the pane.
+# Reported 2026-08-31 on tk-bffa26: the pane asked
+# compare(base=ms/promotion-survives-its-own-confi, head=tk-bffa26) and the
+# milestone branch does not exist on the host — pruned before the host became
+# the remote — so a landed card showed nothing while its diff sat right there
+# (proven on tk-dfaff7, whose recorded commit answers 45898 bytes through the
+# commit door). This chapter moved the pane onto the card's OWN recorded
+# commits, so the assertion has to ask what the pane asks and derive it the same
+# way, or it would go green against a broken pane.
+#
+# `links.tsx::cardRange` is the rule, verbatim: no sha → nothing to assert; ONE
+# recorded commit → `git/commit/<sha>`, which the door already diffs against its
+# first parent; SEVERAL → `git/compare/<oldest>^...<newest>`, the base being the
+# OLDEST commit's PARENT because git diff excludes its base. `gitRoute`
+# percent-encodes each ref (`^` → %5E) and leaves `...` literal, since the
+# separator is the route's grammar and not part of either ref.
+#
+# python3 reads the shas and nothing else does the arithmetic: the payload
+# carries `sha` in more places than `commits` (the history and the merge record
+# among them), so a grep over the whole body picks the wrong first and last ref
+# and would pass on a range no pane ever asks for.
+head_ln "the pane's own range, for both reported cards"
+for card in "$LANDED" "$REPORTED"; do
+  payload=$($C -X POST "$BASE/$BOARD/api/rpc" -H 'Content-Type: application/json' \
+    -d "{\"verb\": \"card\", \"args\": {\"task\": \"$card\"}}") \
+    || fail "POST card $card" "no answer"
+  # route on the first line, the first commit's own files on the rest — one read
+  # of the payload, and the same read the pane does.
+  asked=$(printf %s "$payload" | python3 -c '
+import json, sys, urllib.parse
+data = json.load(sys.stdin).get("data") or {}
+shas = [c["sha"] for c in (data.get("commits") or []) if isinstance(c.get("sha"), str) and c["sha"]]
+if not shas:
+    sys.exit("no recorded commit")
+q = urllib.parse.quote
+route = ("git/commit/" + q(shas[-1], safe="") if len(shas) == 1
+         else "git/compare/" + q(shas[0] + "^", safe="") + "..." + q(shas[-1], safe=""))
+print(route)
+for name in (data["commits"][0].get("files") or []):
+    print(name)
+') || fail "card $card" "could not derive the pane's range"
+  route=$(printf %s "$asked" | sed -n 1p)
+  body=$($C "$BASE/$BOARD/api/$route") || fail "GET $route" "no answer ($card)"
+  case $body in
+    *'"patch": "diff'*|*'"patch":"diff'*)
+      pass "GET /$BOARD/api/$route" \
+        "$card renders ($(printf %s "$body" | wc -c | tr -d ' ') bytes)" ;;
+    *) fail "GET $route" "$card: no patch: $(printf %s "$body" | head -c 300)" ;;
+  esac
+  # THE dropped-base assertion: with the base at the newest commit (or at a
+  # branch tip) the answer is still a patch — it is just the wrong one. Only the
+  # FIRST commit's own files prove the range reaches back to where it started.
+  printf '%s\n' "$asked" | sed -n '2,$p' | while read -r name; do
+    [ -n "$name" ] || continue
+    case $body in
+      *"\"$name\""*) : ;;
+      *) fail "GET $route" "$card: $name — the first commit's file is missing from stat: the base was dropped" ;;
+    esac
+  done || exit 1
+  pass "the first commit's files are in stat" \
+    "$card: $(printf '%s\n' "$asked" | sed -n '2,$p' | wc -l | tr -d ' ') file(s) from $(printf %s "$asked" | sed -n 2p)"
+done
 
 printf '\nall green — %s, board %s\n' "$HOST" "$BOARD"

{taskops_cli-0.5.2 → taskops_cli-0.5.4}/src/taskops/_version.py

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

{taskops_cli-0.5.2 → taskops_cli-0.5.4}/src/taskops/http/stale.py

@@ -49,12 +49,12 @@ that reader and must not drift toward the host's."""
 HOSTED = (
     "{refs} not in this board's own repository on this host. Nothing was "
     "pruned to make that true — this host keeps every branch pushed to it "
-    "forever — so {them} was never pushed here: a card worked before this host "
-    "became the board's remote, or a worktree whose commits have not left it. "
+    "forever — so {subject} never pushed here: {cause}. "
     "A commit reaches this repository the moment it is made in a worktree "
     "joined to the board; the declared forge is a copy of what is here, never "
     "the other way round, so there is nowhere else this pane could look."
 )
+
 """The HOST's words — a reader with no clone, who can run nothing. No command
 is named because there is none they could run, and no forge is named because
 the forge is no longer a source: under the reversal it is a projection of this
@@ -62,6 +62,21 @@ repository, so "not here" is not "look over there". What replaced the mirror's
 "a pruned branch is normal" is the stronger fact — this host prunes nothing —
 and therefore a different diagnosis: the commits never arrived."""
 
+SINGLE = (
+    "a card worked before this host became the board's remote, or a "
+    "worktree whose commits have not left it"
+)
+SEVERAL = (
+    "cards worked before this host became the board's remote, or "
+    "worktrees whose commits have not left them"
+)
+"""The DIAGNOSIS, in the number of the refs it explains. It is an apposition
+to the missing refs themselves — "they were never pushed here: cards worked
+before …" — so it declines with them, subject and possessive both: one ref
+missing is one card or one worktree, several are cards or worktrees. 0.5.2
+shipped "so them was never pushed here" with this clause frozen singular; a
+sentence a reader is meant to trust cannot ask them to forgive its grammar."""
+
 SHA = "0123456789abcdef"
 
 
@@ -82,7 +97,11 @@ def sentence(*refs: str, hosted: bool = False) -> str:
     listed = f"{' and '.join(names)} {'are' if many else 'is'}"
     them = "them" if many else "it"
     if hosted:
-        return HOSTED.format(refs=listed, them=them)
+        return HOSTED.format(
+            refs=listed,
+            subject="they were" if many else "it was",
+            cause=SEVERAL if many else SINGLE,
+        )
     branches = [ref for ref in names if not _looks_like_a_sha(ref)]
     return STALE.format(
         refs=listed,