Component Requirements Inspection - filesystem

### Component Name

filesystem

### Description

This issue tracks the formal Component Requirements Inspection for the component specified above, according to the S-CORE process.

The inspection validates that the component's requirements meet quality, completeness, and testability criteria before the work product is marked as `valid(inspected)`.

References:
- [S-CORE Inspection Conduct](https://eclipse-score.github.io/process_description/main/general_concepts/score_review_concept.html#inspection-conduct)
- [Inspection Checklist Template](https://eclipse-score.github.io/module_template/main/score/component_example/docs/requirements/chklst_req_inspection.html)

### Checklist

#### Moderator (Safety Manager)
- [ ] Create the inspection PR in `eclipse-score/baselibs` with the inspection checklist and link it to this issue via `Fixes #` in the PR description
- [ ] Assign Reviewer(s) and Test Expert; communicate scope and deadline
- [ ] Incorporate reviewer findings as commits into the inspection PR
- [ ] Ensure all checklist items are documented with pass/fail verdicts
- [ ] After all reviewers approve, merge the PR
- [ ] Set work product status to `valid(inspected)`

#### Reviewer(s)
- [ ] Review all component requirements against each inspection checklist item
- [ ] For each failing item, open a GitHub issue in `eclipse-score/baselibs` to track the required correction; link it in the PR comment
- [ ] Add findings as PR comments (pass or fail, with rationale and link to correction issue where applicable)
- [ ] Set PR to "Request Changes" if findings exist
- [ ] Re-review after the author addresses findings; update verdict accordingly

#### Test Expert
- [ ] Review requirements from a testability perspective (focus: REQ_08_01 checklist item)
- [ ] Verify that test cases can be derived from each requirement and that verification criteria are clear
- [ ] Add testability findings as PR comments
- [ ] Re-review after author addresses findings; update verdict accordingly

#### Content Responsible (Author)
- [ ] Analyze all findings and linked correction issues documented in the PR
- [ ] Respond to each finding with an explanation or a proposed correction
- [ ] Commit corrections to address all findings
- [ ] Request re-review from the Reviewer(s) and Test Expert
- [ ] Address any follow-up comments until all reviewers approve

> **Note:** Eclipse contributors cannot push to the inspection branch directly. Findings must be added as PR comments; the Moderator incorporates them as commits.

Start with the linked S-CORE Inspection Conduct and Inspection Checklist Template, then identify the filesystem component requirements in eclipse-score/baselibs. Review each requirement against the checklist, record pass/fail findings and testability comments in the inspection PR, and consider the work done when all findings are addressed, reviewers approve, the PR is merged, and the status is valid(inspected).

Written by the indexing model from the issue text.