Fimeg/souveraine
Watch
1
0
Fork
You've already forked souveraine
 0
Code Releases Activity

patches: 0007 unblocked — the running server carries f266136

Browse source
This commit is contained in:
Fimeg 2026-08-12 17:39:19 -04:00
commit b9f404cbaf
1 changed files with 17 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

21
surfaces/quickshell/patches/README.md
View file

@ -121,10 +121,14 @@ independent lanes and can go whenever.
password rather than finger until that check widens — one line, and a password rather than finger until that check widens — one line, and a
security decision that is Casey's. security decision that is Casey's.
- **0007 — render context occupancy; stop reading hyprctl errors as cursor.** - **0007 — render context occupancy; stop reading hyprctl errors as cursor.**
**Blocked on the server.** Needs `f266136` running, not merely installed. **Unblocked 2026-08-12 17:30.** It needed `f266136` *running*, not merely
As of 2026-08-12 the box runs `souveraine 0.1.r442.gfb5e9bb80cac-1`, and installed. The box now runs `souveraine 0.1.r463.g715080bbfe45-1`, started
`fb5e9bb` *predates* `f266136` — edge has not rebuilt. Applied early the pill 17:26:45 against a binary installed 17:22, and `git merge-base --is-ancestor
honestly shows `—`, which looks exactly like the patch failing. f266136 715080b` passes — so the named-field fix is in the live server.
Re-verify with that one command before applying; installed is not running.
(Earlier state, kept because the *shape* recurs: the box ran r442 = `fb5e9bb`,
which predates `f266136`, and applying early makes the pill honestly show `—`
— indistinguishable from the patch failing.)
The bug it fixes: `ContextPressure` crossed a module boundary as a The bug it fixes: `ContextPressure` crossed a module boundary as a
**positional tuple**, so every consumer guessed what the second element was. **positional tuple**, so every consumer guessed what the second element was.
The TUI guessed `limit` and was right; the HTTP layer named it `tokens` and The TUI guessed `limit` and was right; the HTTP layer named it `tokens` and
@ -133,6 +137,15 @@ independent lanes and can go whenever.
shim), so it runs under viewtop, fails, and its error text is captured **as shim), so it runs under viewtop, fails, and its error text is captured **as
the cursor position** — the probe tested whether the tool was installed, not the cursor position** — the probe tested whether the tool was installed, not
whether it answered. whether it answered.
**Before building the click-through breakdown on top of this**, read
`tasks/context-accounting-two-counters-2026-08-12.md` in memory. The pill
renders the *payload* (what is in the model's window); the
`/v1/conversations/:id/tokens` endpoint renders the *archive* (what the
transcript weighs). On this conversation they differ by ~3x — 80% against a
clamped 100%. Ship them side by side unlabelled and the Panel shows two
numbers that contradict each other. Group the breakdown by **block kind**,
not by role: 74% of the context is tool traffic, which per-role accounting
files under "assistant" and makes it read as talkativeness.
## Recently closed ## Recently closed