chore: Remove state references

Signed-off-by: Javier Aliaga <[email protected]>

Author: javier-aliaga

20250523-RS-workflow-activity-context.md

@@ -6,14 +6,15 @@
 
 ## Overview
 
-This is a proposal to enrich workflow activity context by introducing new fields. This will make it easier for users to control the workflow's state within activities. They are particularly useful for:
+This is a proposal to enrich workflow activity context by introducing new fields. This will make it easier for users to control the retries within activities. They are particularly useful for:
 
 1. **Idempotency**: Ensuring activities are not executed multiple times for the same task
-2. **State Management**: Tracking the state of activity execution
 
 ## Background
 
-Workflow users have raised concerns about controlling and preventing an activity from being invoked more than once or tracking the state of the execution. Input parameters can be used to control the workflow's state, but certain scenarios do not have enough data to do it. Some examples are:
+Workflow users have raised concerns about controlling and preventing an activity from being invoked more than once.
+Input parameters can be used to control the workflow's state, but certain scenarios do not have enough data to do it.
+Some examples are:
 
 - A notification activity where the message content alone isn't enough to determine uniqueness
 - An external service call where idempotency can't be guaranteed by the input parameters
@@ -68,9 +69,6 @@ message ActivityRequest {
 }
 ```
 
-- RetryAttempt: This field will contain the current retry count for the activity execution.  
-
-
 ### Feature lifecycle outline
 
 * Expectations