Unsafe errorTaming and consoleTaming needs other adjustments

[erights]

Using consoleTaming: 'unsafe' will preserve the original platform console. However, due to #636 the Node console is confused by constructor properties that have been turned into accessors. Note that we do not recommend this setting. But if you need to use it, it is best used with overrideTaming: 'min' which avoids turning any constructor properties into accessors.

The errorTaming: 'unsafe' option will avoid redacting the information normally hidden from error instances: the call stack and the detailed error message created by the assert.details template literal tag. lockdown suppresses the redaction of the details by replacing the global assert object with one whose assert.details does not redact. Thus, if you use errorTaming: 'unsafe' be sure to sample the assert object and its details field only after lockdown.

lockdown({ `errorTaming: 'unsafe'` });

// Grab `details` only after lockdown
const { details: X, quote: q } = assert;

[kumavis]

delightful