* feat(runtime): export a render method

* fix unit tests

* add missing export

Co-authored-by: christian-bromann <731337+christian-bromann@users.noreply.github.com>

… behaviour (#6249)

* fix(docs): add overwriteExisting option for flexible README overwrite behaviour

On the `docs-readme` output target, a new `overwriteExisting` option allows developers to
control how existing README files are handled when writing to a custom path.

This adds flexibility to either:

- Always overwrite the full README (`true`),
- Only write the full README if no file exists (`'if-missing'`), or
- Preserve existing custom content (**default** `false`).

Now, `docs-readme` treats the component `readme.md` files as the canonical source for
manually-entered custom content when overwriting READMEs. This ensures that custom content
is preserved unless explicitly overwritten.

For example, when using the `'if-missing'` flag, a project that writes component readmes
into a documentation library folder can maintain consistent, idempotent output across
local builds and CI environments. Custom edits to the destination files will be maintained,
while files without customisation will be fully exported.

Fixes #6248

* test(docs-readme): add coverage for overwriteExisting behaviours

Adds tests covering all `overwriteExisting` modes on the `docs-readme` output target:

- Always overwrite (`true`)
- Overwrite if missing (`'if-missing'`) with and without a destination file
- Never overwrite (`false`)
- Default behaviour (`undefined`), which treats missing values as `false`

Tests confirm that manual content is preserved when appropriate, new files are correctly
generated when missing, and behaviour matches the original fix for #5400.

Also validates idempotent output across multiple overwriting scenarios.

Related to the fix for #6248.

* test(docs-readme): revamp overwrite test for consistent test state

Added `copy-readme.js` to copy the supplemental README over the known README result to
ensure the file is in a consistent state before the test begins.

This approach verifies whether the `docs-readme` output target correctly overwrites the
file as expected during the test process.

* refactor(copy-readme): normalize formatting with Prettier

* fix(build): fix build after dependency updates

* more build improvements

* prettier

* v4.31.0

* update changelog

---------

Co-authored-by: christian-bromann <731337+christian-bromann@users.noreply.github.com>
Co-authored-by: Christian Bromann <git@bromann.dev>