Fix markdown and added release notes related with vistibility Control

## **Release X.0.0**

## **Release 4.0.0**

### **Visibility Control**

Current relase includes the initial implementation (Not complete functional) of Visibility Control API. The complete feature implementation is expected to be relased on next OpenCAPIF version, stay tuned!

### **Technical Debt Solved**

This test case verifies that the **Superadmin** can retrieve the registered rules. In this case, the response is an empty registry because no rules have been provisioned. It validates the basic connectivity and authentication flow for administrative roles.

**Pre-Conditions**:

* The **CAPIF** helper service is deployed and reachable.

* Superadmin credentials (`SUPERADMIN_USERNAME`) are provisioned.

* The database is in a clean state (no rules existing).

**Execution Steps**:

1. Authenticate as **Superadmin**.

2. Send a **GET** request to `{apiRoot}/helper/visibility-control/rules`.

3. Inspect the **JSON** response body.

**Expected Result**:

* **Status**: **200 OK**.

* **Body**: Returns a **JSON** object with a `rules` array. The length of this array must be **0**.

This test case validates the API's logic regarding time-range consistency. A visibility rule must have a logical duration; therefore, the service must reject any attempt to create a rule where the expiration date occurs before the start date.

**Pre-Conditions**:

* The **CAPIF** helper service is deployed and reachable.

* Superadmin credentials (`SUPERADMIN_USERNAME`) are provisioned.

**Execution Steps**:

1. Authenticate as **Superadmin**.

2. Send a **POST** request to `{apiRoot}/helper/visibility-control/rules`.

3. Use a payload where `startsAt` is later than `endsAt` (e.g., Starts: `2026`, Ends: `2025`).

**Expected Result**:

* **Status**: **400 Bad Request**.

* **Body**: Must contain a `ProblemDetails` object with the `detail` field specifying **"endsAt must be later than startsAt"**.

This test verifies that the **Superadmin** can create a rule, obtain its information, and successfully remove it.

**Pre-Conditions**:

* The **CAPIF** helper service is deployed and reachable.

* Superadmin credentials (`SUPERADMIN_USERNAME`) are provisioned.

* A valid `RuleCreateRequest` payload including the mandatory `providerSelector` and `userName`.

**Execution Steps**:

1. Authenticate as **Superadmin**.

2. Send a **POST** request to `{apiRoot}/helper/visibility-control/rules`.

3. Send a **GET** request to `{apiRoot}/helper/visibility-control/rules`.

5. **GET** the rules list again to verify the count returns to zero.

**Expected Result**:

* **Creation**: **201 Created** (Body contains the generated `ruleId`).

* **Listing**: **200 OK** (List length is **1**).

* **Deletion**: **204 No Content**.

This test case validates that an **AMF Provider** can list rules and that the system correctly maps the Provider's certificate (**CN**) to their registered identity to filter the results.

**Pre-Conditions**:

* The **CAPIF** helper service is deployed and reachable.

* A **Provider** has been registered and onboarded at **CCF**.

* The **Provider** possesses a valid certificate (in this case **AMF** certificate).

**Execution Steps**:

1. Authenticate using the **AMF Provider Certificate**.

2. Send a **GET** request to `{apiRoot}/helper/visibility-control/rules`.

**Expected Result**:

* **Status**: **200 OK**.

* **Validation**: The response body must only contain rules where the requester is the owner (`userName`).

This test validates the roles and permissions of **Superadmin** and **Providers** to create, delete, and obtain rules.

**Pre-Conditions**:

* The **CAPIF** helper service is deployed and reachable.

* A **Provider** has been registered and onboarded at **CCF**.

* The **Provider** possesses a valid certificate (in this case **AMF** certificate).

* **Superadmin** has administrative access.

**Execution Steps**:

1. **AMF Provider** creates a rule: **POST** request to `{apiRoot}/helper/visibility-control/rules`.

2. **Superadmin** sends a **GET** request to `{apiRoot}/helper/visibility-control/rules`.

3. **Superadmin** sends a **DELETE** request for that `ruleId`.

**Expected Result**:

* **Provider rule Creation**: **201 Created**.

* **Superadmin Get**: **200 OK**.

* **Superadmin Deletion**: **204 No Content**.

This test validates that the **Providers** can create, delete, and obtain rules, ensuring that the identity-based authorization logic correctly identifies the owner of a resource and allows them to delete it without requiring **Superadmin** intervention.

**Pre-Conditions**:

* The **CAPIF** helper service is deployed and reachable.

* A **Provider** has been registered and onboarded at **CCF**.

* The **Provider** possesses a valid certificate (in this case **AMF** certificate).

**Execution Steps**:

1. **AMF Provider** creates a rule: **POST** request to `{apiRoot}/helper/visibility-control/rules`.

2. **AMF Provider** sends a **DELETE** request for the same rule using the same provider identity and the `ruleId`.

**Expected Result**:

* **Status**: **204 No Content**.

* **Validation**: Subsequent list requests by the provider return an empty set.

This test validates the **PATCH** implementation. It ensures that **Providers** can perform partial updates to their rules and that the system correctly updates metadata like `updatedAt`.

**Pre-Conditions**:

* The **CAPIF** helper service is deployed and reachable.

* A **Provider** has been registered and onboarded at **CCF**.

* The **Provider** possesses a valid certificate (in this case **AMF** certificate).

**Execution Steps**:

1. **AMF Provider** creates a rule: **POST** request to `{apiRoot}/helper/visibility-control/rules`.

2. Send a **PATCH** request to `{apiRoot}/helper/visibility-control/rules/{ruleId}`.

3. **Payload**: Change `default_access` from **"ALLOW"** to **"DENY"**.

5. **AMF Provider** sends a **DELETE** request for the same rule using the same provider identity and the `ruleId`.

**Expected Result**:

* **Status**: **200 OK**.

* **Body**: Returns the updated `Rule` object showing the new `default_access` value and a refreshed `updatedAt` timestamp, and finally the rule is successfully removed.

This test verifies the direct resource addressing logic and the error reporting.

**Pre-Conditions**:

* The **CAPIF** helper service is deployed and reachable.

* Superadmin credentials (`SUPERADMIN_USERNAME`) are provisioned.

**Execution Steps**:

1. **Superadmin** creates a rule: **POST** request to `{apiRoot}/helper/visibility-control/rules`.

2. Send a **GET** request for the specific resource via `{apiRoot}/helper/visibility-control/rules/{ruleId}`.

3. **DELETE** the resource.

4. Perform the same **GET** request as in step 2.

**Expected Result**:

* **Step 2**: **200 OK** (Returns the specific rule object).

* **Step 4**: **404 Not Found** (Ensures the resource no longer exists in the registry).