9 and 10 November: stricter checks between accounts
Several releases tighten what one account can reach of another, and add automated tests that fail if those boundaries ever loosen.
Everyone using ZeroLog benefits in the background: one account can reach less of another, and a disabled account's container webhooks stop. Only webhook callers of a disabled account see a new 403 answer. No action is needed.
Recipe addresses. A prompt recipe made from a goal run used to take its web address from the raw task text. If that text contained an access key, part of the key could end up in the public address once the recipe was published. The address is now built from the cleaned text, the same way the recipe page already was. No published recipe was affected.
Container webhooks. An inbound webhook kept delivering events into its container after the account was disabled or lost container access. It now stops and answers with status 403. The API reference lists the new answer.
Connections and container keys. Connections to private addresses accept only the plain written form of an address, and link-local addresses are refused. The key a container uses to reach the API now accepts only a whole number as its container ID.
Tests. New automated tests check that security scans, webhooks, editor access, recipes and the ZeroLog Link relay stay within one account. They were checked by deliberately removing each safeguard: every removal turns a test red.