docs: update implementation status for 7 already-implemented tool requirements

[FScholPer]

📌 Description

Updates docs/internals/requirements/requirements.rst to reflect that 7 tool requirements previously marked as NO or PARTIAL are already enforced in the codebase. Each updated requirement now links to the corresponding implementation file.

Requirements updated (NO/PARTIAL → YES):

Requirement ID	What it enforces	Implementation location
tool_req__docs_saf_attrs_content	Non-empty content on safety analysis needs	metamodel.yaml — content: ^[\s\S]+$ as mandatory_options
tool_req__docs_saf_attrs_violates	violates link to architecture diagrams	metamodel.yaml — mandatory_links on all safety types
tool_req__docs_saf_attr_fmea_fault_id	fault_id on FMEA needs	metamodel.yaml — mandatory_options on feat_saf_fmea, comp_saf_fmea
tool_req__docs_saf_attr_dfa_failure_id	failure_id on DFA needs	metamodel.yaml — mandatory_options on feat_saf_dfa, comp_saf_dfa
tool_req__docs_req_attr_validity_correctness	Milestone format regex	metamodel.yaml — optional_options regex on stkh_req, feat_req
tool_req__docs_req_attr_validity_consistency	valid_from < valid_until	check_options.py — check_validity_consistency local check
tool_req__docs_doc_generic_mandatory	status, safety, security, realizes	metamodel.yaml — mandatory_options + mandatory_links on document type

Motivation

The requirements documentation was outdated — these checks have been implemented in metamodel.yaml and check_options.py but the :implemented: field was never updated. This reduces the apparent open-issue count by ~37% (from 35 to ~22 real gaps).

🚨 Impact Analysis

• This change does not violate any tool requirements and is covered by existing tool requirements
• This change does not violate any design decisions
• Otherwise I have created a ticket for new tool qualification

✅ Checklist

• Added/updated documentation for new or changed features
• Added/updated tests to cover the changes
• Followed project coding standards and guidelines

Note: This is a documentation-only change (updating :implemented: status fields and adding implementation notes). No code or test changes are needed.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //src:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: 6c6bb360-9e3b-4be0-854b-6a7f7c47a484
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: src
WARNING: Target pattern parsing failed.
ERROR: Skipping '//src:license-check': no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
ERROR: no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
INFO: Elapsed time: 5.693s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

[github-actions]

The created documentation from the pull request is available at: docu-html