mirror of https://github.com/azaion/ai-training.git synced 2026-04-23 10:36:36 +00:00

Files

T

Oleksandr Bezdieniezhnykh 243b69656b Update test results directory structure and enhance Docker configurations

- Modified `.gitignore` to reflect the new path for test results.
- Updated `docker-compose.test.yml` to mount the correct test results directory.
- Adjusted `Dockerfile.test` to set the `PYTHONPATH` and ensure test results are saved in the updated location.
- Added `boto3` and `netron` to `requirements-test.txt` to support new functionalities.
- Updated `pytest.ini` to include the new `pythonpath` for test discovery.

These changes streamline the testing process and ensure compatibility with the updated directory structure.

2026-03-28 00:13:08 +02:00

2.6 KiB

Raw Blame History

Phase 4: Execution

Role: Orchestrator Goal: Execute all refactoring tasks by delegating to the implement skill Constraints: No inline code changes — all implementation goes through the implement skill's batching and review pipeline

4a. Pre-Flight Checks

Verify refactoring task files exist in TASKS_DIR (created during Phase 2d):
- All [JIRA-ID]_refactor_*.md files are present
- Each task file has valid header fields (Task, Name, Description, Complexity, Dependencies)
Verify TASKS_DIR/_dependencies_table.md includes the refactoring tasks
Verify all tests pass (safety net from Phase 3 is green)
If any check fails, go back to the relevant phase to fix

4b. Delegate to Implement Skill

Read and execute .cursor/skills/implement/SKILL.md.

The implement skill will:

Parse task files and dependency graph from TASKS_DIR
Detect already-completed tasks (skip non-refactoring tasks from prior workflow steps)
Compute execution batches for the refactoring tasks
Launch implementer subagents (up to 4 in parallel)
Run code review after each batch
Commit and push per batch
Update Jira/ADO ticket status

Do NOT modify, skip, or abbreviate any part of the implement skill's workflow. The refactor skill is delegating execution, not optimizing it.

4c. Capture Results

After the implement skill completes:

Read batch reports from _docs/03_implementation/batch_*_report.md
Read _docs/03_implementation/FINAL_implementation_report.md
Write RUN_DIR/execution_log.md summarizing:
- Total tasks executed
- Batches completed
- Code review verdicts per batch
- Files modified (aggregate list)
- Any blocked or failed tasks
- Links to batch reports

4d. Update Task Statuses

For each successfully completed refactoring task:

Transition the Jira/ADO ticket status to Done via the configured tracker MCP
If tracker unavailable, note the pending status transitions in RUN_DIR/execution_log.md

For any failed or blocked tasks, leave their status as-is (the implement skill already set them to In Testing or blocked).

Self-verification:

All refactoring tasks show as completed in batch reports
All completed tasks have Jira/ADO status set to Done
All tests still pass after execution
No tasks remain in blocked or failed state (or user has acknowledged them)
RUN_DIR/execution_log.md written with links to batch reports

Save action: Write RUN_DIR/execution_log.md

GATE: All refactoring tasks must be implemented. If any tasks failed, present the failures to the user and ask for guidance before proceeding to Phase 5.

2.6 KiB Raw Blame History