Prepare Node.js Core Contribution Commits

Problem Description

A contributor has been working on a fix for a bug in Node.js's fs module: fs.readdir() was not properly handling the recursive option on certain Linux kernel versions when the directory being scanned contained symbolic links pointing outside the scanned tree. Additionally, a follow-up change updates the documentation to clarify the behavior of the recursive option.

The contributor made the changes but is not familiar with Node.js's commit message style requirements and needs the commit messages properly formatted before submitting a pull request. The Node.js project has strict commit message conventions and validates them automatically.

Your task is to prepare properly formatted commit messages for these two changes, validate them, and document the process.

The changes being committed are:

Change 1 (Bug fix): Modified lib/fs.js and src/node_file.cc to correctly handle symbolic links when recursive: true is used with fs.readdir() on Linux. The fix avoids following symlinks that resolve outside the original directory tree. This closes GitHub issue #52341.

Change 2 (Documentation): Updated doc/api/fs.md to document that fs.readdir() with recursive: true does not follow symbolic links that point outside the scanned directory on any platform, and added a note about the behavior difference with fs.readdirSync(). This is related to pull request #52342.

Output Specification

Produce the following files:

• commit-messages.txt — Contains both properly formatted commit messages, separated by a blank line and a --- divider between them.
• validation-output.txt — The output from running the commit message validator on each message. Run the validator on each message and save all output to this file.
• process-notes.md — A brief explanation of the commit message format you used and how you validated the messages.