Add Roles and Responsibilities documentation to Key Concepts

[Copilot]

Adds documentation defining roles, activities, and responsibilities within the RDK HAL ecosystem, clarifying the distinction between Vendor (OEM), Vendor Layer Owner, Ingestion Owner, and Test Delivery Team.

Changes

• New document: docs/halif/key_concepts/hal/roles_and_responsibilities.md defines five key roles:

  • The Vendor (OEM): SoC/Board integration and delivery
  • Vendor Layer Owner: Single point of contact for layer quality
  • Vendor Layer Ingestion: Process for integrating vendor layers into Comcast products
  • Vendor Layer Ingestion Owner: Responsible for ingestion quality gates
  • Vendor Test Delivery Team: HAL governance and test infrastructure

• Navigation update: Added entry under Hardware Abstraction Layer → Key Concepts in mkdocs.yml

Each role definition includes specific responsibilities and clarifies when roles may overlap (e.g., internal vs. third-party vendors).

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Task: Add resoles and responsbilities</issue_title>
<issue_description>### Goal

Need to create a new document under Key Concepts documentation area to define the roles and respsonbilities and what we mean by vendor

Notes (Optional)

This is the draft I have

Roles and responsibilities

Definitions of roles,  activities and responsibilities.

Where "Comcast" is used it can mean either a Sky or Comcast team. We are all in it together...

    The Vendor (may be better understood as the OEM)
        Integrator responsible delivering an integrated and tested SoC and Board SW delivery
        Integrates 3rd party SW and RDKe SW components that have a SoC or Board related configuration/build
        The Vendor can be a 3rd party or internal to Comcast when integrating a “home grown product”
    Vendor Layer Owner (Comcast and 3rd party)
        Single point of contact for the delivery and quality of a Vendor Layer
        Expected to ensure VTS is executed and passes where appropriate
        The Vendor Layer Owner can be both the 3rd party or internal to Comcast when integrating a “home grown product”
        The Vendor Owner can be responsible for one or more Vendor Layers
    Vendor Layer Ingestion (Comcast specific)
        The process of ingesting a new or changed Vendor Layer into a Comcast Product (or product Comcast is responsible for)
    Vendor Layer Ingestion Owner (Comcast specific)
        Single point of contact and total responsibility for the ingestion of a new or changed Vendor Layer into a Comcast Product
        Responsible for ensuring that all quality requirements have been passed before wider use
        Expected to ensure VTS is executed and passes where appropriate
        Where the Vendor Layer Owner is internal, the Vendor Layer and Ingestion Owner are one and the same and from a Comcast perspective the Ingestion Owner IS the Vendor Layer Owner
    Vendor Test Delivery Team (Comcast HAL police)
        Responsible for the management and delivery of the HAL Test Infrastructure
        Ensuring HAL governance is enforced
        Coordinate with other testing teams
```</issue_description>

<agent_instructions>create a new document for roles and responsilbilties</agent_instructions>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes Task: Add resoles and responsbilities #306

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.