Tags give the ability to mark specific points in history as being important
-
payload-capture-hardened
bd59fe79 · ·Payload capture is trustworthy Four defects in what the recorder does with a real application's values, all found by pointing the tool at real code rather than at payloads written to suit it, and all verified by reading journey_events.input_payload out of PostgreSQL. ADR-035 - the built-in secret list reached the top level of a payload and one level below it, and nothing inside an array. config.headers.authorization, the shape every axios error carries, was stored as plaintext in every capture mode and at both redaction points. Secret names now match wherever they are filed. ADR-036 - Map, Set, Error, RegExp, Headers and URLSearchParams keep their data in internal slots, so the rebuild that makes redaction possible emptied them all to {}. An Error lost the two fields that say what went wrong. They are rendered inside the walk now, shallowly and under their own keys, so redaction reaches into them and the size guard can measure them. ADR-034 - a cycle or a BigInt was reported as payload_too_large and the whole payload discarded, sending operators to a setting that could not have helped. And a __proto__ key in a payload was silently destroyed, along with the promise that the timeline shows what actually arrived. 395 unit, 130 integration, 7 acceptance, each on a clean clone.