Migrate all YAML files to version "1.0" string format

Update all taskflows, personalities, prompts, toolboxes, and configs
to use semver string version format for compatibility with
seclab-taskflow-agent v1.0.

Author: anticomputer

src/seclab_taskflows/configs/model_config.yaml

@@ -2,7 +2,7 @@
 # SPDX-License-Identifier: MIT
 
 seclab-taskflow-agent:
-  version: 1
+  version: "1.0"
   filetype: model_config
 models:
    code_analysis: gpt-5

src/seclab_taskflows/configs/model_config_codeql_python.yaml

@@ -2,7 +2,7 @@
 # SPDX-License-Identifier: MIT
 
 seclab-taskflow-agent:
-  version: 1
+  version: "1.0"
   filetype: model_config
 models:
    code_analysis: gpt-5

src/seclab_taskflows/configs/model_config_lowercost.yaml

@@ -2,7 +2,7 @@
 # SPDX-License-Identifier: MIT
 
 seclab-taskflow-agent:
-  version: 1
+  version: "1.0"
   filetype: model_config
 models:
    code_analysis: gpt-5-mini

src/seclab_taskflows/personalities/action_expert.yaml

@@ -3,8 +3,7 @@
 
 seclab-taskflow-agent:
   filetype: personality
-  version: 1
-
+  version: "1.0"
 personality: |
   You are an expert in GitHub actions and workflows. A GitHub workflow maybe reusuable by other workflows. 
   Here are some important facts about GitHub actions and workflows that you should know and used in your analysis.

src/seclab_taskflows/personalities/auditor.yaml

@@ -2,7 +2,7 @@
 # SPDX-License-Identifier: MIT
 
 seclab-taskflow-agent:
-  version: 1
+  version: "1.0"
   filetype: personality
 
 personality: |

src/seclab_taskflows/personalities/web_application_security_expert.yaml

@@ -3,8 +3,7 @@
 
 seclab-taskflow-agent:
   filetype: personality
-  version: 1
-
+  version: "1.0"
 personality: |
   You are a security expert for web applications and libraries, in multiple programming languages.
   You have the ability to call tools to aid you in your security reviews. You know when libraries are used in an unsafe way.

src/seclab_taskflows/prompts/audit/audit_issue.yaml

@@ -3,8 +3,7 @@
 
 seclab-taskflow-agent:
   filetype: prompt
-  version: 1
-
+  version: "1.0"
 prompt: |
         The issues suggested have not been properly verified and are only suggested because they are common issues in these types of 
         application. Your task is to audit the source code to check if this type of issues is present. 

src/seclab_taskflows/prompts/triage_taskflows/actions_common/check_dismiss_reason.yaml

@@ -3,21 +3,20 @@
 
 seclab-taskflow-agent:
   filetype: prompt
-  version: 1
-
+  version: "1.0"
 prompt: |
-  The key is {{ RESULT_key }}. If it is `repos` or `dismissed_alerts_summary,` then your task is done.
+  The key is {{ result.key }}. If it is `repos` or `dismissed_alerts_summary,` then your task is done.
 
-  The repo and alert id can are encoded in the key {{ RESULT_key }} as follows:
+  The repo and alert id can are encoded in the key {{ result.key }} as follows:
   ```
   <encoded_repo_name>_<alert id>
   ```
   For example, if the key is `my_org/my_repo_123`, the repo name to use is `my_org/my_repo`.
   The alert id is the number after the last `_` in the key, which is `123` in this case.
 
-  Before you start, check if an issue with the alert id already exists in {{ RESULT_repo }}.
+  Before you start, check if an issue with the alert id already exists in {{ result.repo }}.
   If it doesn't, then your task is done. 
-  Otherwise, fetch the issue from {{ RESULT_repo }} using the issue id that you found and inspect its body.
+  Otherwise, fetch the issue from {{ result.repo }} using the issue id that you found and inspect its body.
   Remember the issue id, which you'll need to add label and comment on the issue later. 
   This is usually not the same as the alert id.
 

src/seclab_taskflows/prompts/triage_taskflows/actions_common/dismiss_decision.yaml

@@ -3,8 +3,7 @@
 
 seclab-taskflow-agent:
   filetype: prompt
-  version: 1
-
+  version: "1.0"
 prompt: |
   If you decided that the ANY dismissal reason applies then alert is invalid. In this case, add the `FP` label to the issue.
   But if the None of the dismissal reason applies, then don't add the `FP` label.

src/seclab_taskflows/taskflows/alert_triage_examples/triage_common/check_notes.yaml

@@ -3,8 +3,7 @@
 
 seclab-taskflow-agent:
   filetype: taskflow
-  version: 1
-
+  version: "1.0"
 model_config: seclab_taskflows.configs.model_config
 
 taskflow:
@@ -17,10 +16,10 @@ taskflow:
         - seclab_taskflows.personalities.web_application_security_expert
       async: true
       user_prompt: |
-        The alert_id is {{ RESULT_alert_id }} and the repo is {{ RESULT_repo }}.
+        The alert_id is {{ result.alert_id }} and the repo is {{ result.repo }}.
         The notes from the alert analysis is:        
         ```
-        {{ RESULT_result }}
+        {{ result.result }}
         ```
         Check all results whether they contain next steps that need to be taken. If they do, then take those steps.
         In case code parts (such as methods) were not found previously, look them up and change the notes accordingly.