fix(evlog): respect status/statusCode on Error instances

[benhid]

🔗 Linked issue

Resolves #217

📚 Description

parseError() has three branches for determining the HTTP status of an error:

1. Objects with a data property → extracts status from the data (covers EvlogError, FetchError)
2. Error instances → hardcoded 500
3. Everything else → hardcoded 500

Branch 2 is ignoring any .status or .statusCode property sitting on the error object. This is a problem for frameworks that attach HTTP status to their native error classes, such as NestJS: when adding ValidationPipe with a class-validator DTO, NestJS throws BadRequestException (HTTP 400). BadRequestException extends HttpException extends Error: it has no data property, so it falls through to Branch 2 and gets hardcoded as 500.

Fix

The library already has extractErrorStatus() in shared/errors.ts (used by the middleware layer) which does exactly what was needed. The fix is a one-line change in Branch 2 to call extractErrorStatus(error) instead of hardcoding 500.

Tests

Added 5 new test cases under describe('Error instances with status properties'):

• .status on Error → respected (NestJS HttpException pattern)
• .statusCode on Error → respected (H3/Nitro pattern)
• .status preferred over .statusCode when both exist
• Plain Error without status → still returns 500 (backward compat)
• Non-numeric .status → falls back to 500

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[vercel]

@benhid is attempting to deploy a commit to the HRCD Projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for following the naming conventions! 🙏

[pkg-pr-new]

npm i https://pkg.pr.new/evlog@218

npm i https://pkg.pr.new/@evlog/nuxthub@218

commit: d2042df