refactor: Couchbase CE edition implementation refactor (#65)

Author: osantana85

docs/community-edition/Introduction.md

@@ -27,7 +27,7 @@ Below is a summary of the available editions in the Flamingock Community Edition
 | MongoDB   | MongoDB          | >=4.0              | ✅ Yes        | ✅ Yes           | Flamingock provides support for both low-level native drivers and high-level abstractions through Spring Data integration. |
 | DynamoDB  | AWS DynamoDB     | >=2.25.29          | ✅ Yes        | ✅ Yes           |                                                                                                                            |
 | CosmosDB  | Azure Cosmos DB  | Mongo API 3.6/4.0  | ✅ Yes        | ✅ Yes           |                                                                                                                            |
-| Couchbase | Couchbase Server | >=3.4.3            | ❌ No         | ✅ Yes           |                                                                                                                            |
+| Couchbase | Couchbase Server | >=3.6.0            | ❌ No         | ✅ Yes           |                                                                                                                            |
 
 ---
 ## Features

docs/community-edition/ce-couchbase.md

@@ -25,7 +25,7 @@ This edition supports Couchbase through a dedicated artifact:
 
 | Edition Name              | Java SDK                           | Couchbase Compatibility |
 |---------------------------|------------------------------------|-------------------------|
-| `flamingock-ce-couchbase` | `com.couchbase.client:java-client` | >= `3.4.3`              |
+| `flamingock-ce-couchbase` | `com.couchbase.client:java-client` (>= `3.6.0`) | >= `7.0`              |
 
 ---
 
@@ -66,13 +66,17 @@ implementation("com.couchbase.client:java-client:3.x.x")
 
 ### 2. Enable Flamingock runner
 
-At minimum, you must provide a `Cluster` instance (as a **dependency**):
+At minimum, you must provide:
+- A Cluster instance (as a **dependency**)
+- A Bucket instance (as a **dependency**)
 
 ```java
 Cluster cluster = Cluster.connect("localhost", "username", "password");
+Bucket bucket = cluster.bucket("YOUR_BUCKET");
 
 Runner runner = Flamingock.builder()
     .addDependency(cluster)
+    .addDependency(bucket)
     .build();
 ```
 
@@ -88,26 +92,27 @@ runner.execute();
 
 ## Configuration overview
 
-Flamingock’s Couchbase Community Edition requires both:
-
-- A `Cluster` dependency
-- A set of configuration properties
+Flamingock requires both dependencies and configuration properties, set via the builder.
 
 ### Dependencies
 
 These must be registered using `.addDependency(...)`
 
 | Type                                | Required | Description                                        |
 |-------------------------------------|:--------:|----------------------------------------------------|
-| `com.couchbase.client.java.Cluster` |   Yes    | Required to connect and execute against Couchbase. |
+| `com.couchbase.client.java.Cluster` |   Yes    | Required to connect and execute against Couchbase cluster. |
+| `com.couchbase.client.java.Bucket` |   Yes    | Required to connect and execute against Couchbase bucket. |
 
 ### Properties
 
 These must be set using `.setProperty(...)`
 
 | Property      | Type      | Required | Default Value | Description                                                              |
 |---------------|-----------|:--------:|---------------|--------------------------------------------------------------------------|
-| `autoCreate`  | `boolean` |    No    | `true`        | Whether Flamingock should auto-create required buckets and indexes.      |
+| `couchbase.autoCreate`  | `boolean` |    No    | `true`        | Whether Flamingock should auto-create required collections and indexes.      |
+| `couchbase.scopeName`  | `String` |    No    | `"_default"`        | Name of the Couchbase scope where the collections exist or will be created.       |
+| `couchbase.auditRepositoryName`   | `String`               |   No    | `"flamingockAuditLogs"`        | Name of the collection for storing the audit log. Overrides the default. Most users should keep the default value.    |
+| `couchbase.lockRepositoryName`    | `String`               |    No    | `"flamingockLocks"`             | Name of the collection used for distributed locking. Overrides the default. Most users should keep the default value. |
 
 :::warning
 In production environments, we strongly recommend keeping the default configuration values unless you fully understand the implications.  
@@ -122,12 +127,15 @@ The following example shows how to configure Flamingock with both required and o
 
 ```java
 Cluster cluster = Cluster.connect("localhost", "username", "password");
+Bucket bucket = cluster.bucket("YOUR_BUCKET");
 
 FlamingockBuilder builder = Flamingock.builder()
     // mandatory dependency
     .addDependency(cluster)
+    .addDependency(bucket)
     // optional configuration
-    .setProperty("autoCreate", true);
+    .setProperty("autoCreate", true)
+    .setProperty("couchbase.scopeName", "YOUR_SCOPE");
 ```
 
 > You can add additional dependencies and properties based on your custom setup (e.g., metrics, listeners, or cloud-specific settings).

docs/community-edition/ce-dynamodb.md

@@ -120,8 +120,8 @@ These must be set using `.setProperty(...)`
 | `dynamodb. readCapacityUnits`   | `Long`    |    No    | `5L`                  | Read capacity units (for **PROVISIONED** billing mode only).                 |
 | `dynamodb. writeCapacityUnits`  | `Long`    |    No    | `5L`                  | Write capacity units (for **PROVISIONED** billing mode only).                |
 | `dynamodb.autoCreate`           | `Boolean` |    No    | `true`                | Automatically creates the required tables if they do not exist.              |
-| `dynamodb. auditRepositoryName` | `String`  |    No    | `flamingockAuditLogs` | Table used to store audit records. Most users should keep the default name.  |
-| `dynamodb. lockRepositoryName`  | `String`  |    No    | `flamingockLock`      | Table used for distributed locking. Most users should keep the default name. |
+| `dynamodb. auditRepositoryName` | `String`  |    No    | `"flamingockAuditLogs"` | Table used to store audit records. Most users should keep the default name.  |
+| `dynamodb. lockRepositoryName`  | `String`  |    No    | `"flamingockLocks"`      | Table used for distributed locking. Most users should keep the default name. |
 
 :::warning
 In production environments, we strongly recommend keeping the default configuration values unless you fully understand the implications.  

docs/community-edition/ce-mongodb-java-driver.md

@@ -116,7 +116,7 @@ These must be set using `.setProperty(...)`
 | `mongodb. writeConcern.wTimeout` | `Duration`             | `Duration .ofSeconds(1)`       |    No    | Maximum time to wait for the write concern to be fulfilled.                                                           |
 | `mongodb. readPreference`        | `ReadPreference Level` | `ReadPreferenceLevel .PRIMARY` |    No    | Defines which MongoDB node to read from.                                                                              |
 | `mongodb. auditRepositoryName`   | `String`               | `"flamingockAuditLogs"`        |    No    | Name of the collection for storing the audit log. Overrides the default. Most users should keep the default value.    |
-| `mongodb. lockRepositoryName`    | `String`               | `"flamingockLock"`             |    No    | Name of the collection used for distributed locking. Overrides the default. Most users should keep the default value. |
+| `mongodb. lockRepositoryName`    | `String`               | `"flamingockLocks"`             |    No    | Name of the collection used for distributed locking. Overrides the default. Most users should keep the default value. |
 
 :::warning
 We strongly recommend keeping the default configuration values in production environments. They are optimized for **consistency, durability, and safety**, ensuring Flamingock’s audit and rollback guarantees.
@@ -172,7 +172,7 @@ You can find practical examples in the official GitHub repository:
 - **Use Flamingock’s default consistency settings (`writeConcern`, `readConcern`, `readPreference`) in production**  
   These values guarantee strong consistency, durability, and fault tolerance. Overriding them is discouraged unless absolutely necessary.
 
-- **Use the default collection names (`flamingockAuditLogs`, `flamingockLock`)**  
+- **Use the default collection names (`flamingockAuditLogs`, `flamingockLocks`)**  
   These help avoid collisions and simplify debugging.
 
 - **Enable automatic index creation unless your environment prohibits it**  

docs/community-edition/ce-mongodb-springdata.md

@@ -169,7 +169,7 @@ Spring Boot will typically auto-configure `MongoTemplate` for you.
 | `mongodb. writeConcern.wTimeout` | `Duration`             | `Duration. ofSeconds(1)`       |    No    | Maximum time to wait for the write concern to be fulfilled.                                     |
 | `mongodb. readPreference`        | `ReadPreference Level` | `ReadPreferenceLevel. PRIMARY` |    No    | Specifies which MongoDB node to read from.                                                      |
 | `mongodb. auditRepositoryName`   | `String`               | `"flamingockAuditLogs"`        |    No    | Name of the collection used to store applied changes. Most users should keep the default value. |
-| `mongodb. lockRepositoryName`    | `String`               | `"flamingockLock"`             |    No    | Name of the collection used for distributed locking. Most users should keep the default value.  |                                                    |
+| `mongodb. lockRepositoryName`    | `String`               | `"flamingockLocks"`             |    No    | Name of the collection used for distributed locking. Most users should keep the default value.  |                                                    |
 
 :::warning
 It's **strongly recommended keeping the default MongoDB configuration values provided by Flamingock** — especially in production environments. These defaults are carefully chosen to guarantee **maximum consistency, durability, and safety**, which are fundamental to Flamingock’s audit and rollback guarantees.
@@ -252,7 +252,7 @@ You can find practical examples in the official GitHub repository:
   These defaults are **strictly selected to guarantee strong consistency, durability, and fault-tolerance**, which are fundamental to Flamingock’s execution guarantees.  
   Overriding them is **strongly discouraged in production environments**, as it can compromise the integrity of audit logs and distributed coordination.
 
-- **Use the default repository names (`flamingockAuditLogs`, `flamingockLock`) unless you have a strong reason to change them**  
+- **Use the default repository names (`flamingockAuditLogs`, `flamingockLocks`) unless you have a strong reason to change them**  
   The default names are chosen to avoid collisions and clearly identify Flamingock-managed collections. Overriding them is supported but rarely necessary.
 
 - **Keep `indexCreation` enabled unless your deployment restricts index creation at runtime**  

docs/testing/springboot-integration-testing.md

@@ -134,7 +134,7 @@ static void overrideProperties(DynamicPropertyRegistry registry) {
   registry.add("flamingock.dynamodb.writeCapacityUnits", () -> 5L);
   registry.add("flamingock.dynamodb.autoCreate", () -> true);
   registry.add("flamingock.dynamodb.auditRepositoryName", () -> "flamingockAuditLogs");
-  registry.add("flamingock.dynamodb.lockRepositoryName", () -> "flamingockLock");
+  registry.add("flamingock.dynamodb.lockRepositoryName", () -> "flamingockLocks");
 }
 ```