refactor: rename executed to applied

Author: dieppa

LICENSE.md

@@ -132,7 +132,7 @@ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
    by You to the Licensor shall be under the terms and conditions of
    this License, without any additional terms or conditions.
    Notwithstanding the above, nothing herein shall supersede or modify
-   the terms of any separate license agreement you may have executed
+   the terms of any separate license agreement you may have applied
    with Licensor regarding such Contributions.
 
 6. Trademarks. This License does not grant permission to use the trade

README.md

@@ -4,7 +4,7 @@
 
 
 <h3 align="center">Auditable, versioned changes across distributed systems.</h3>
-<p align="center">Evolve queues, DBs, APIs, configs, resources and more — governed, auditable, executed at startup in lockstep.</p>
+<p align="center">Evolve queues, DBs, APIs, configs, resources and more — governed, auditable, applied at startup in lockstep.</p>
 
 <p align="center"><small><a href="https://github.com/flamingock/mongock-legacy?tab=readme-ov-file#%EF%B8%8F-mongock-is-deprecated">Coming from Mongock?</a></small></p>
 <br />
@@ -35,7 +35,7 @@
 
 With Flamingock, your application and the systems it interacts with — including databases, message queues, feature flags, configurations, APIs, and cloud resources — evolve together, in lockstep.
 
-**All changes are versioned, auditable**, and executed as part of the same deployment lifecycle.
+**All changes are versioned, auditable**, and applied as part of the same deployment lifecycle.
 
 No more post-deploy scripts or manual tweaks: every change is declared alongside your code and applied safely during application startup.
 

cli/flamingock-cli/CLI-README.md

@@ -24,7 +24,7 @@ A lightweight command-line interface for Flamingock audit operations in communit
 # List conflicted audit entries
 ./flamingock-cli-dist/flamingock audit list
 
-# Mark change unit as executed
+# Mark change unit as applied
 ./flamingock-cli-dist/flamingock audit mark --change-id ch1 --state APPLIED
 
 # Mark change unit as rolled back
@@ -163,7 +163,7 @@ Lists all conflicted audit entries showing:
 
 ### `flamingock audit mark`
 Marks a change unit with a specific state:
-- **`--state APPLIED`** - Marks as successfully executed
+- **`--state APPLIED`** - Marks as successfully applied
 - **`--state ROLLED_BACK`** - Marks as rolled back
 - **`--change-id <id>`** - Required change unit identifier
 

cli/flamingock-cli/src/test/java/io/flamingock/cli/integration/CLIMongoIntegrationTest.java

@@ -72,7 +72,7 @@ void shouldRunAuditListCommandWithMongoDB() throws Exception {
             System.out.println("MongoDB container is running: " + mongoContainer.isRunning());
             System.out.println("MongoDB connection string: " + mongoContainer.getConnectionString());
 
-            // The fact that we got here means TestContainers worked and CLI executed
+            // The fact that we got here means TestContainers worked and CLI applied
             assertThat(mongoContainer.isRunning()).isTrue();
 
         } finally {

cloud/flamingock-cloud/src/main/java/io/flamingock/cloud/audit/HtttpAuditWriter.java

@@ -84,12 +84,12 @@ public Result writeEntry(AuditEntry auditEntry) {
 
 
     private AuditEntryRequest buildRequest(AuditEntry auditEntry) {
-        long executedAtEpochMillis = ZonedDateTime.of(auditEntry.getCreatedAt(), ZoneId.systemDefault()).toInstant().toEpochMilli();
+        long appliedAtEpochMillis = ZonedDateTime.of(auditEntry.getCreatedAt(), ZoneId.systemDefault()).toInstant().toEpochMilli();
         return new AuditEntryRequest(
                 auditEntry.getStageId(),
                 auditEntry.getTaskId(),
                 auditEntry.getAuthor(),
-                executedAtEpochMillis,
+                appliedAtEpochMillis,
                 auditEntry.getState().toRequestStatus(),
                 auditEntry.getType().toRequestExecutionType(),
                 auditEntry.getClassName(),

cloud/flamingock-cloud/src/main/java/io/flamingock/cloud/planner/CloudExecutionPlanMapper.java

@@ -114,7 +114,7 @@ private static ChangeActionMap getChangeActionMap(AbstractLoadedStage loadedStag
             String taskId = task.getId();
             CloudChangeAction cloudAction = actionsMapByChangeId.get(taskId);
 
-            // If task not in response, assume it's already executed (cloud orchestrator decision)
+            // If task not in response, assume it's already applied (cloud orchestrator decision)
             if (cloudAction == null) {
                 actionMap.put(taskId, ChangeAction.SKIP);
             } else {

cloud/flamingock-cloud/src/test/java/io/flamingock/core/utils/TaskExecutionChecker.java

@@ -31,7 +31,7 @@ public void reset() {
         history.clear();
     }
 
-    public boolean isExecuted() {
+    public boolean isApplied() {
         return history.contains(TestTaskExecution.EXECUTION);
     }
 
@@ -47,7 +47,7 @@ public void markRollBackExecution() {
         history.add(TestTaskExecution.ROLLBACK_EXECUTION);
     }
 
-    public boolean isBeforeExecuted() {
+    public boolean isBeforeApplied() {
         return history.contains(TestTaskExecution.BEFORE_EXECUTION);
     }
 

community/flamingock-auditstore-dynamodb/src/test/java/io/flamingock/community/dynamodb/DynamoDBAuditStoreTest.java

@@ -165,7 +165,7 @@ void happyPathWithTransaction() {
     }
 
     @Test
-    @DisplayName("When standalone runs the driver and execution fails should persist only the executed audit logs")
+    @DisplayName("When standalone runs the driver and execution fails should persist only the applied audit logs")
     void failedWithTransaction() {
         // Given-When-Then - Test failure scenario with audit verification
         AuditTestSupport.withTestKit(testKit)

community/flamingock-auditstore-mongodb-sync/src/test/java/io/flamingock/community/mongodb/sync/MongoSyncAuditStoreTest.java

@@ -166,7 +166,7 @@ void happyPathWithTransaction() {
     }
 
     @Test
-    @DisplayName("When standalone runs the driver with transactions enabled and execution fails should persist only the executed audit logs")
+    @DisplayName("When standalone runs the driver with transactions enabled and execution fails should persist only the applied audit logs")
     void failedWithTransaction() {
         //Given-When-Then
         AuditTestSupport.withTestKit(testKit)

community/flamingock-auditstore-mongodb-sync/src/test/java/io/flamingock/community/mongodb/sync/MongoSyncCoreStrategiesE2ETest.java

@@ -195,8 +195,8 @@ void testFailingTransactionalChangeWithRollback() {
     }
 
     @Test
-    @DisplayName("Should handle already-executed changes correctly on second run with MongoDB persistence")
-    void testAlreadyExecutedChangesSkipping() {
+    @DisplayName("Should handle already-applied changes correctly on second run with MongoDB persistence")
+    void testAlreadyAppliedChangesSkipping() {
         // Given - Create MongoDB test kit with persistent storage
         TestKit testKit = MongoDBSyncTestKit.create(new MongoDBSyncAuditStore(mongoClient, "test"), mongoClient, database);
         AuditTestHelper auditHelper = testKit.getAuditHelper();