doc(obj): add note on transition rules minimal duration (#6215)

* doc(obj): add note on transition rules minimal duration

* doc(obj): update

* doc(obj): update

Author: SamyOubouaziz

pages/object-storage/api-cli/lifecycle-rules-api.mdx

@@ -17,17 +17,16 @@ import Requirements from '@macros/iam/requirements.mdx'
 You can configure the lifecycle of a group of objects so that their storage costs can be effectively managed. A lifecycle configuration is a set of rules that defines actions applied to a group of objects stored on Object Storage.
 
 Currently, the **expiration**, **transition**, and **incomplete multipart uploads** actions are supported on the platform:
-  * **Expiration** defines when objects expire. This allows for the automatic deletion of objects on your behalf.
+  * **Expiration** defines when objects expire. Expired objects are automatically deleted.
   * **Transition** defines when objects change storage classes.
   * **Incomplete Multipart Uploads** allows you to stop uploads automatically if they are not completed.
 
 <Message type="important">
-  Lifecycle rules only allow the following transitions:
-  - Standard Multi-AZ -> Standard One Zone
-  - Standard Multi-AZ -> Glacier
-  - Standard One Zone -> Glacier
+- Transition rules created or updated after February 10, 2026 in the Warsaw region, and after February 18, 2026 in the Paris region, must observe the following minimal durations before applying:
+  - Objects must be stored for at least 30 days before transitioning to Standard One Zone.
+  - Objects must be stored for at least 90 days before transitioning to Glacier.
 
-  Refer to our [dedicated documentation](/object-storage/how-to/edit-storage-class/) to manually change the storage class of your objects.
+These minimal durations do not apply to lifecycle rules created before these dates, unless they are updated. The duration requirements above will then apply. They also do not apply to the Amsterdam region.
 </Message>
 
 There might, for example, be a need to store log files for a week or a month, after which they become obsolete. It is possible to set a lifecycle rule to delete them automatically when they become obsolete. If you consider that a 3-month-old object is rarely used but still has a value, you might want to configure a rule to send it automatically to [Scaleway Glacier](/object-storage/faq/#what-is-the-cold-storage-glacier-class), for example.
@@ -133,6 +132,13 @@ This applies the `Prefix` rule *and* the `Tag`.
 **Parent**
 : `Rule`
 
+<Message type="note">
+Lifecycle rules only allow the following transitions:
+- Standard Multi-AZ -> Standard One Zone 
+- Standard Multi-AZ -> Glacier
+- Standard One Zone -> Glacier
+</Message>
+
 ### Day
 
 **Description**