078: The calls to the vault server, as a tab: what each one is, and what it carried

What is asked

The pane listed every call ("PUT /api/vault/write/… → 200"). The owner: interesting, but show what they are, a file, a commit, something else, and let me expand one and see its contents; "worth becoming a UI itself".

Scenario

Given the pane has made calls to the vault server on this page
When I open the Calls tab
Then each call is listed with its time, a badge for what it touched (object, ref, working ref, branch index, append lane), the vault by name (your reader vault, your master vault, your door, your lane), its status, size and time taken
When I open a call
Then what it carried is decrypted here with the key of its vault, when that vault is open in this page, and named: a commit with its message, time, tree and parents; a tree with its entries; a ref with the commit it points at; a file with its text
And the master's and the door's file contents open only behind Reveal
And an append-lane call shows its body with tokens and keys masked
And calls of a vault not open here say they stay sealed

Outcome

Shipped in v0.12.88: assets/vault-pane/calls.js (pure: the address named, a batch split into its operations, the plaintext classified, credentials masked) and the Calls tab in vault-pane.js, which keeps the bytes of this page's calls in memory and the earlier pages' calls, without bytes, in session storage; Wider widens the pane. Nothing is fetched to decode: the bytes are the call's own. Checked by test_vault_open.mjs (a commit, a tree and a ref decoded from the calls of an update).

Screenshots