Dnm test upmerge

.clang-format

@@ -82,6 +82,7 @@ ForEachMacros:
   - 'HTTP_SERVICE_FOREACH_RESOURCE'
   - 'I3C_BUS_FOR_EACH_I3CDEV'
   - 'I3C_BUS_FOR_EACH_I2CDEV'
+  - 'MIN_HEAP_FOREACH'
 IfMacros:
   - 'CHECKIF'
 # Disabled for now, see bug https://github.com/zephyrproject-rtos/zephyr/issues/48520

.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

.github/ISSUE_TEMPLATE/004_feature_request.yml

@@ -0,0 +1,29 @@
+name: Feature Request
+description: Suggest a new feature or enhancement
+labels: ["Feature Request"]
+type: Feature
+assignees: []
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is.
+      placeholder: e.g., I'm frustrated when I need to do X manually because Y is missing.
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+      placeholder: e.g., It would be great if the system could automatically handle X by doing Y.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Describe alternatives you've considered
+      description: Include any alternative solutions or features

.github/ISSUE_TEMPLATE/006_nomination.yml

@@ -0,0 +1,57 @@
+name: Contributor Nomination
+description: Nominate a GitHub user for the Contributor role with triage permissions
+labels: [Role Nomination]
+assignees: ['nashif']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Background
+
+        The [TSC Project Roles](https://docs.zephyrproject.org/latest/project/project_roles.html) defines the main roles for the Zephyr Project, including Maintainer, Collaborator, and Contributor.
+
+        By default, anyone who contributes code or documentation is a Contributor, but with the lowest [GitHub Permission Level](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization) of **Read**.
+
+        Use this form to nominate a user for the **Contributor** role with **Triage** permission, which allows the user to:
+        - Add reviewers to pull requests
+        - Be added as a reviewer by others
+
+  - type: input
+    id: full-name
+    attributes:
+      label: Full Name
+      description: Full name of the nominated contributor.
+      placeholder: e.g., Jane Doe
+    validations:
+      required: true
+
+  - type: input
+    id: github-username
+    attributes:
+      label: GitHub Username
+      description: GitHub handle of the nominated contributor.
+      placeholder: e.g., @janedoe
+    validations:
+      required: true
+
+  - type: input
+    id: organization
+    attributes:
+      label: Organization
+      description: Organization the nominee is affiliated with (optional).
+      placeholder: e.g., Acme Corp
+    validations:
+      required: false
+
+  - type: textarea
+    id: supporting-documents
+    attributes:
+      label: Supporting Documents
+      description: Provide links to 3–5 pull requests authored or reviewed by the nominee that demonstrate their dedication to the Zephyr project.
+      placeholder: |
+        e.g.,
+        - https://github.com/zephyrproject-rtos/zephyr/pull/12345
+        - https://github.com/zephyrproject-rtos/zephyr/pull/23456
+        - https://github.com/zephyrproject-rtos/zephyr/pull/34567
+    validations:
+      required: true