The status line said the proxy does not apply rules yet. Replace it with
the request and response phases, what exchange_rewrites records and how
the hashes are formed (plain SHA-256, keyed HMAC for sensitive actions),
the SSE and WebSocket behaviour, the 5 MiB response pass-through, the
snapshot limits (live slots are never deleted by the TTL), and the fact
that replays go through the proxy and are rewritten like captures.
It now says that traffic_get shows the originals of a rewritten exchange
and that traffic_search never finds a value a rewrite rule wrote. As for
traffic_search, only the original built-in text is replaced.
The sink runs the request phase in the Request hook and the response phase
at the start of the Response hook; at SSEStart only status and header
actions apply. WebSocketStart comes after the client is upgraded, so the
handshake is traced "not rewritten: stream" and recorded as sent.
Exchanges keep what the client sent and what the target answered. The
original of a rewritten request lives in a per-flow snapshot slot (entry or
tombstone, 1024 entries / 64 MiB, 4096 tombstones), reserved before the
request is changed, released on Response, RequestError, SSEStart, a 5 MiB
response, or by a sweep of finished flows (ClientDisconnected, 1 s
debounce, 1 min period). Under pressure an entry older than 15 minutes is
turned into a tombstone in place, only when that frees room for the new
reservation; its exchange is recorded "original request unavailable".
record(), recordStreamStart() and insertExchange() clear any trace under
the id before INSERT OR REPLACE; the trace (exchange_rewrites, created
with CREATE TABLE IF NOT EXISTS) is written in the exchange's transaction,
its spilled values registered in blob_refs, and purged with the exchange.
The full-text index covers the originals only. Logs of a rewritten flow
name the host, the step or error class and the rule ids, never the URL or
the error text. A rewritten request's transport error never switches its
host to passthrough. traffic_get shows the rewritten flag and rule ids.
Without a rule that applies, what is recorded is unchanged byte for byte.
The request phase can fail after the engine is done: the rewritten request
does not reach the target. NoteError records that as the rule's last error,
under the new class transport_error.
A handler that installs its own MaxBytesReader and then calls decode lost the 413: decode converted the error to a plain one and the middleware's limitedBody had been replaced. Return the original *http.MaxBytesError and update the cap test to errors.As.
The listener closes before Wait, and a shutdown refuses new task operations. Wait also stays until detached runs finish. The activity insert and the outbox delete commit together, and a row that keeps failing is dropped after five attempts so it cannot block the rest.
The outbox migration is 0006 because 0005 is already traffic rewrite rules. A shutdown cancel leaves an in-flight intent claim running, so the next start can reset it to open instead of recording the interrupt as done or blocked.
The profile drawer's API Key input is a masked field with no autocomplete
hint, so browsers and password managers treat it as this site's login
password: they fill it when the drawer opens and Save then persists the
wrong secret over the key already stored in the profile. Mark the field
new-password and add the 1Password/Bitwarden ignore hints, matching the
setup page's convention.
The loaded model list can hold several hundred entries (OpenRouter: 470),
which is unusable without filtering. Add a search input above the list
with a case-insensitive substring match, a "no model matches" state, and
reset it whenever the list is reloaded or the popover closes.
The plaintext-substring guard encoded one encoder's output shape: it only held
while a small input compressed to fewer bytes than it started with, and Go
1.27 stores instead. Comparing sizes states the same invariant without
assuming how flate picks between stored and compressed blocks: a stored block
is larger than its input by construction, so "output is under half the input"
is true for any working encoder on a repetitive body and false for a body that
was never compressed.
Checked against the old 60-byte fixture on go1.27.4: it fails with "fixture is
not compressed: 60 bytes in, 85 bytes out", so the guard still catches the
case it was written for.
The go job tests only the toolchain go.mod pins, so a newer Go can break the
suite without a repository change: Go 1.27's compress/flate started emitting a
stored block for a 60-byte input, and TestDecodeEvidenceBodyGzipQuoteFound
failed on its own "fixture is not compressed" guard (#276).
go-stable runs the same build, vet and -p 1 test commands against whatever
release is current, with the same postgres service. It is continue-on-error
because a toolchain release is not a change to this repository and should not
block an unrelated merge on the day it lands; the log still carries the
failure, and dropping that line makes it a required check once the pinned
floor moves.
TestDecodeEvidenceBodyGzipQuoteFound built its body from the 60-byte
decodeHTML constant and guarded with "the stream must not contain admin".
That assumes the encoder always deflates, and Go 1.27's flate does not: for
this input it emits a stored block, the stream is 85 bytes, and the raw bytes
are the plaintext the guard rejects. The test then fails on the encoder's
choice rather than on the decode it is meant to cover.
Repeat the body so it has something to compress, and assert the decoded
output equals it, so the guard measures the round trip instead of one
encoder's block selection. The quote and the body's content are unchanged,
and the sibling truncated/deflate tests already use repeated input.