Bump version to 0.2.28: remove subject-activate from workflow phases

The subject-activate command phase fails when the ao binary isn't in
the workflow-runner's PATH (e.g. after machine reboot). Remove it from
all bundled task workflows to prevent cascading failures. Task status
transitions are handled by the daemon tick executor instead.

Author: Shooksie

crates/orchestrator-cli/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "orchestrator-cli"
-version = "0.2.27"
+version = "0.2.28"
 edition = "2021"
 
 [[bin]]

crates/orchestrator-config/config/bundled-packs/ao.task/workflows/task-pack.yaml

@@ -30,7 +30,6 @@ workflows:
     name: AO Task Standard
     description: Canonical pack-qualified task workflow ref.
     phases:
-      - subject-activate
       - requirements
       - implementation
       - workflow_ref: ao.review/cycle
@@ -39,7 +38,6 @@ workflows:
     name: AO Task UI UX
     description: Canonical pack-qualified frontend task workflow ref.
     phases:
-      - subject-activate
       - requirements
       - ux-research
       - wireframe
@@ -51,15 +49,13 @@ workflows:
     name: AO Task Quick Fix
     description: Canonical pack-qualified quick-fix workflow ref.
     phases:
-      - subject-activate
       - implementation
       - testing
 
   - id: ao.task/gated
     name: AO Task Gated
     description: Canonical pack-qualified gated workflow ref.
     phases:
-      - subject-activate
       - requirements
       - implementation
       - unit-test: