updating docs

Author: matheusmra

docs/architecture/core_structures.md

@@ -245,30 +245,31 @@ class PipelineExecution:
     start_time: float               # Execution start timestamp
 ```
 
-### Methods
+### Pipeline Execution Summary
 
-```python
-def get_pipeline_execution_summary() -> dict:
-    """
-    Generate detailed summary for API responses.
-    
-    Returns:
+The `PipelineExecutionSerializer` (`autograder/serializers/pipeline_execution_serializer.py`) handles the conversion of an execution into a dictionary for API responses.
+
+#### `PipelineExecutionSerializer.serialize(execution) -> dict`
+
+Generates detailed summary for API responses.
+
+**Returns:**
+```json
+{
+    "status": "success" | "failed",
+    "failed_at_step": str | None,
+    "total_steps_planned": int,
+    "steps_completed": int,
+    "execution_time_ms": int,
+    "steps": [
         {
-            "status": "success" | "failed",
-            "failed_at_step": str | None,
-            "total_steps_planned": int,
-            "steps_completed": int,
-            "execution_time_ms": int,
-            "steps": [
-                {
-                    "name": "PRE_FLIGHT",
-                    "status": "success" | "fail",
-                    "message": str,
-                    "error_details": dict | None  # Present if step failed
-                }
-            ]
+            "name": "PreFlightStep",
+            "status": "success" | "fail",
+            "message": str,
+            "error_details": dict | None  # Present if step failed
         }
-    """
+    ]
+}
 ```
 
 ### Example Summary (Success)

docs/guides/github_module.md

@@ -17,7 +17,7 @@ In short, the adopted solution consists of running a Docker container with the d
 1. [Action.yml](../../action.yml)
    Defines the inputs received by the action, describes the output as a JSON evaluation, and runs the container with the received data as environment variables.
 
-2. [Dockerfile](../../github_action/Dockerfile.actions)
+2. [Dockerfile](../../Dockerfile.actions)
    Builds the container that installs the Autograder repository and sets [Entrypoint.sh](../../github_action/entrypoint.sh) as the script to be executed when the container starts.
 
 3. [Entrypoint.sh](../../github_action/entrypoint.sh)

docs/pipeline/README.md

@@ -71,7 +71,7 @@ EMPTY ──▶ RUNNING ──▶ SUCCESS
 - `has_step_result(step_name)` — Checks if a step was executed.
 - `get_previous_step()` — Returns the most recently added step result.
 - `finish_execution()` — Assembles the `GradingResult` from the GRADE, FOCUS, and FEEDBACK step results if the pipeline succeeded.
-- `get_pipeline_execution_summary()` — Generates a structured dictionary for API responses with step details, timing, and error information.
+- `PipelineExecutionSerializer.serialize(execution)` — Generates a structured dictionary for API responses with step details, timing, and error information.
 
 ### StepResult
 
@@ -197,7 +197,7 @@ When a step fails:
 
 For unhandled exceptions, the status is set to `INTERRUPTED` and the same cleanup logic applies.
 
-The `PipelineExecution` object provides `get_pipeline_execution_summary()` for structured error reporting in API responses. See [Pipeline Execution Tracking](../architecture/pipeline_execution_tracking.md) for details on how this surfaces in the API.
+The `PipelineExecutionSerializer` provides structured error reporting in API responses. See [Pipeline Execution Tracking](../architecture/core_structures.md#pipeline-execution-summary) for details on how this surfaces in the API.
 
 ---