* fix: clear trailer state when removing all trailers

* Update test/reply-trailers.test.js

Signed-off-by: Manuel Spigolon <behemoth89@gmail.com>

---------

Signed-off-by: Manuel Spigolon <behemoth89@gmail.com>
Co-authored-by: Manuel Spigolon <behemoth89@gmail.com>

Clarify that request.params values are percent-decoded (so encoded
separators like %2f become /) and must not be used as filesystem
paths, template names, or redirect targets without validation.
Point authors at @fastify/static for serving files from a root.

* docs(errors): document what the default error handler sends

The Errors reference described an uncaught error as producing a "generic
500 Internal Server Error" response. The status text is generic, but the
body carries `error.message` verbatim, along with `code` when the error
has one, so messages raised deep in an application reach the client.

Document the response shape, add a security note that unexpected errors
must be masked explicitly, and show a setErrorHandler that does so while
passing deliberate 4xx and validation errors through.

Refs #4513

* docs(errors): scope the stack-trace claim to the built-in serializer

Address review feedback on #6894.

"The stack trace is never included" is only true of Fastify's built-in
error serializer. When a route-level response schema matches the error
status code, fallbackErrorHandler passes Object.create(error, ...) to
the schema serializer, so a schema declaring `stack` serializes it:

  GET /  (500 response schema with `stack`)
  -> {"statusCode":500,"error":"Internal Server Error",
      "message":"kaboom","stack":"Error: kaboom\n    at ..."}

Scope the sentence accordingly and name `stack` in the existing note
about response-schema serialization.

Also soften the setErrorHandler example's comment: a status code below
500 means the error was raised deliberately, not that its message is
safe to expose.

…6837)

* docs(encapsulation): clarify nested plugin scopes

* docs(encapsulation): improve nested scope wording

* docs(encapsulation): use consistent plugin alias

* Update docs/Reference/Encapsulation.md

Co-authored-by: Manuel Spigolon <behemoth89@gmail.com>
Signed-off-by: Jean Michelet <110341611+jean-michelet@users.noreply.github.com>

---------

Signed-off-by: Jean Michelet <110341611+jean-michelet@users.noreply.github.com>
Co-authored-by: Manuel Spigolon <behemoth89@gmail.com>
Co-authored-by: Matteo Pietro Dazzi <matteopietro.dazzi@gmail.com>

Bumps [fastify/workflows/.github/workflows/lock-threads.yml](https://github.com/fastify/workflows) from 6.0.0 to 7.0.0.
- [Release notes](https://github.com/fastify/workflows/releases)
- [Commits](fastify/workflows@2073dc8...ef591e2)

---
updated-dependencies:
- dependency-name: fastify/workflows/.github/workflows/lock-threads.yml
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…6917)

Bumps [fastify/workflows/.github/workflows/nested-quality.yml](https://github.com/fastify/workflows) from 6.0.0 to 7.0.0.
- [Release notes](https://github.com/fastify/workflows/releases)
- [Commits](fastify/workflows@2073dc8...ef591e2)

---
updated-dependencies:
- dependency-name: fastify/workflows/.github/workflows/nested-quality.yml
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…dependencies (#6892)

… parsers (#6846)

A content-type parser registered with a g- or y-flagged RegExp keeps a mutable
lastIndex between calls, so getParser's .test() could skip part of the next
content type and match inconsistently. Reset lastIndex before each test.