Sync with 4.1.99

.clang-format

@@ -99,6 +99,7 @@ IndentCaseLabels: false
 IndentGotoLabels: false
 IndentWidth: 8
 InsertBraces: true
+InsertNewlineAtEOF: true
 SpaceBeforeInheritanceColon: False
 SpaceBeforeParens: ControlStatementsExceptControlMacros
 SortIncludes: Never

.github/ISSUE_TEMPLATE/001_bug_report.yml

@@ -0,0 +1,85 @@
+name: Bug Report
+description: File a bug report.
+labels: ["bug"]
+type: "Bug"
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Describe the bug
+      description: |
+        A clear and concise description of what the bug is.
+
+      placeholder: |
+        Please also mention any information which could help others to understand
+        the problem you're facing:
+          - What target platform are you using?
+          - What have you tried to diagnose or workaround this issue?
+          - Is this a regression? If yes, have you been able to "git bisect" it to a
+            specific commit?
+    validations:
+      required: true
+  - type: checkboxes
+    id: regression
+    attributes:
+      label: Regression
+      description: |
+        Check this box if this is a regression and provide a SHA if you were able to "git bisect" to a specific commit.
+      options:
+        - label: This is a regression.
+          required: false
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: |
+        Steps to reproduce the behavior.
+
+      placeholder: |
+        Steps to reproduce the behavior:
+          1. mkdir build; cd build
+          2. cmake -DBOARD=board\_xyz
+          3. make
+          4. See error
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: dropdown
+    attributes:
+      label: Impact
+      description: Impact of this bug
+      multiple: false
+      options:
+        - Showstopper – Prevents release or major functionality; system unusable.
+        - Major – Severely degrades functionality; workaround is difficult or unavailable.
+        - Functional Limitation – Some features not working as expected, but system usable.
+        - Annoyance – Minor irritation; no significant impact on usability or functionality.
+        - Intermittent – Occurs occasionally; hard to reproduce.
+        - Not sure
+      default: 3
+    validations:
+      required: true
+  - type: textarea
+    id: env
+    attributes:
+      label: Environment
+      description: please complete the following information
+      placeholder: |
+       - OS: (e.g. Linux, MacOS, Windows)
+       - Toolchain (e.g Zephyr SDK, ...)
+       - Commit SHA or Version used
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Provide other context that could be relevant to the bug, such as pin setting, target configuration,etc.

.github/ISSUE_TEMPLATE/002_enhancement.yml

@@ -0,0 +1,42 @@
+name: Enhancement
+description: Submit an Enhancement
+labels: ["Enhancement"]
+type: "Enhancement"
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this enhancement proposal.
+  - type: textarea
+    id: description
+    attributes:
+      label: Summary
+      description: |
+        Is your enhancement proposal related to a problem? Please describe.
+      placeholder: |
+        A clear and concise description of what the problem is.
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      description: |
+        Describe the solution you'd like
+      placeholder: |
+        A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives
+      description: Describe alternatives you've considered
+      placeholder: |
+        A clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Add any other context or graphics (drag-and-drop an image) about the enhancement here.

.github/ISSUE_TEMPLATE/003_rfc-proposal.yml

@@ -0,0 +1,75 @@
+name: RFC / Proposal
+description: Submit a Proposal (RFC)
+labels: ["RFC"]
+type: RFC
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Introduction
+
+        This section targets end users, TSC members, maintainers and anyone else
+        that might need a quick explanation of your proposed change.
+
+  - type: textarea
+    id: problem-description
+    attributes:
+      label: Problem Description
+      description: Why do we want this change and what problem are we trying to address?
+      placeholder: Explain the problem or limitation this RFC is meant to resolve.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed-change-summary
+    attributes:
+      label: Proposed Change (Summary)
+      description: A high-level summary of the proposed change.
+      placeholder: Brief summary of what will change if this RFC is implemented.
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: |
+        ## Detailed RFC
+
+        This section targets the development team. Upon reading it, each engineer
+        should understand what must be done to implement the proposed feature.
+
+  - type: textarea
+    id: detailed-change
+    attributes:
+      label: Proposed Change (Detailed)
+      description: Describe the change in as much detail as possible. Include context or background info, and reuse of existing components if applicable.
+      placeholder: Explain exactly what you’re planning to change and how.
+    validations:
+      required: true
+
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies
+      description: Highlight how this change may affect the rest of the project or other teams/components.
+      placeholder: List components, modules, or teams affected.
+    validations:
+      required: false
+
+  - type: textarea
+    id: concerns
+    attributes:
+      label: Concerns and Unresolved Questions
+      description: List any concerns, unknowns, or unresolved questions related to this proposal.
+      placeholder: Any areas of uncertainty?
+    validations:
+      required: false
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: What alternative solutions were considered? Why was this proposal chosen?
+      placeholder: List alternatives and explain the rationale behind your choice.
+    validations:
+      required: false