ace-task 0.31.4 → 0.31.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5e477e2c198c576ab07f7a50eb6756e04448bc1c42e5f5fc17beec674be15527
-  data.tar.gz: ea40e22f1e761cc6fa7bc3ba9cba138af6047272c3941a39a325f36de5dd527e
+  metadata.gz: 911b91460493816a3936af599bfd074c9e4bbfa62fa09704aadd27bfa276096e
+  data.tar.gz: be75ba2c8f40cd8f3999914688ce4eab99b844e88b510bd3bd2e36843bb1f1ff
 SHA512:
-  metadata.gz: 5dc208ea23a98741cda9b2a65230688dd5fd705e31979d517eb8fa5a9749f9ffa8fc19ca3efa3b52fe5bd4fbc66a915838141098f371ad9eb179c81ad40fc035
-  data.tar.gz: e0f63752e0a24626c1ffdd27e0c371eee92ed68288f5904f7a7b9d094f035b7dab4b6f35d9c10076bc4c99faf04ff1bc028319f06a3ed0376e24355b9168c1ca
+  metadata.gz: 7dd8f6f2a16245332c5cb972f835b917663532f1002957bc113d7225ffa796ac1b66fcc786f458e1b488e8f019a289ff60d9cb631acf3b2288442430c0607e7a
+  data.tar.gz: 682b0bcb44391cdf8adc8ef67243c95adc695ebdcad57c5fe98666f259f6c5b264dcc1a425eb2cce8195eadb83029db70ca15f0d31f5b166b0cae54bd5b9d75e

data/CHANGELOG.md

@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.31.6] - 2026-03-29
+
+### Fixed
+- `task/review` and `task/update`: replaced split same-task promotion examples with a combined `ace-task update <ref> --set status=pending,needs_review=false` pattern and explicitly banned parallel updates against the same task ref.
+
+### Technical
+- Added command coverage for combined scalar updates including `needs_review=false`.
+
+## [0.31.5] - 2026-03-29
+
+### Fixed
+- **ace-task v0.31.5**: Bumped dependency constraints to currently available `~>` ranges on RubyGems and updated release metadata after dependency synchronization.
+
 ## [0.31.4] - 2026-03-26
 
 ### Added

data/handbook/workflow-instructions/task/review.wf.md

@@ -139,19 +139,19 @@ Validate draft behavioral specifications and promote to pending when ready. This
 
    **If Ready (all readiness criteria met):**
    - **Orchestrator rule:** If the task is an orchestrator, only promote the parent after all draft child subtasks have been reviewed and promoted successfully.
+   - **Same-task mutation rule:** Do not run multiple `ace-task update` commands in parallel against the same task ref. Prefer one combined `--set` call when clearing or setting multiple scalar fields on the same task.
    - **Recursive promotion for orchestrators:**
      - Review each draft child subtask using the same checklist
      - Promote each child subtask that passes:
        ```bash
-       ace-task update <child-ref> --set status=pending
-       ace-task update <child-ref> --set needs_review=false
+       ace-task update <child-ref> --set status=pending,needs_review=false
        ```
      - For any child subtask that fails, keep it in `draft`, set `needs_review=true`, and do not promote the parent
    - Promote the task status and clear any existing `needs_review` flag:
      ```bash
-     ace-task update <ref> --set status=pending
-     ace-task update <ref> --set needs_review=false
+     ace-task update <ref> --set status=pending,needs_review=false
      ```
+   - Validate immediately after each promotion with `ace-task show <ref>` before proceeding to the next same-task mutation or parent promotion.
    - Report promotion:
      ```
      Task <ref> promoted from draft to pending.
@@ -348,4 +348,4 @@ This approach enables:
 
 ---
 
-This workflow ensures draft tasks are validated and promoted to pending when ready, or blocked with clear questions when not, serving as the quality gate between behavioral specification and implementation planning.
+This workflow ensures draft tasks are validated and promoted to pending when ready, or blocked with clear questions when not, serving as the quality gate between behavioral specification and implementation planning.

data/handbook/workflow-instructions/task/update.wf.md

@@ -46,10 +46,14 @@ Load and follow:
    ace-task update <ref> --set status=in-progress
    ace-task update <ref> --set status=done
    ace-task update <ref> --set status=done,priority=high
+   ace-task update <ref> --set status=pending,needs_review=false
    ace-task update <ref> --add tags=shipped
    ace-task update <ref> --remove tags=wip
    ```
 
+   - When multiple scalar fields on the same task must change together, prefer one combined `--set a=x,b=y` command.
+   - Do not run multiple `ace-task update` commands in parallel against the same task ref.
+
 3. **Apply hierarchy updates via `--move-as-child-of`**
 
    - Promote a subtask to standalone
@@ -90,6 +94,7 @@ Load and follow:
 
    - Re-open target task: `ace-task show <ref>`
    - Confirm metadata, location, parent/child relationship, and position
+   - If you combined multiple field updates, confirm all fields persisted before issuing another same-task mutation
    - Verify dry-run output before executing non-idempotent moves
 
 ## Error Handling
@@ -115,4 +120,4 @@ Load and follow:
 - Reparenting operations produce the intended hierarchy state
 - Sort position changes place the task at the requested location
 - Location moves place the task in the intended folder/release
-- Final `ace-task show <ref>` output matches expected target state
+- Final `ace-task show <ref>` output matches expected target state

data/lib/ace/task/version.rb

@@ -2,6 +2,6 @@
 
 module Ace
   module Task
-    VERSION = "0.31.4"
+    VERSION = '0.31.6'
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ace-task
 version: !ruby/object:Gem::Version
-  version: 0.31.4
+  version: 0.31.6
 platform: ruby
 authors:
 - Michal Czyz
@@ -15,84 +15,84 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.25'
+        version: '0.29'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.25'
+        version: '0.29'
 - !ruby/object:Gem::Dependency
   name: ace-support-fs
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.2'
+        version: '0.3'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.2'
+        version: '0.3'
 - !ruby/object:Gem::Dependency
   name: ace-support-items
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.3'
+        version: '0.15'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.3'
+        version: '0.15'
 - !ruby/object:Gem::Dependency
   name: ace-support-markdown
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.2'
+        version: '0.3'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.2'
+        version: '0.3'
 - !ruby/object:Gem::Dependency
   name: ace-b36ts
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.7'
+        version: '0.13'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.7'
+        version: '0.13'
 - !ruby/object:Gem::Dependency
   name: ace-support-cli
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.3'
+        version: '0.6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.3'
+        version: '0.6'
 description: Behavioral spec-based task management with compact IDs, subtask trees,
   AI-powered implementation plans, and automated health checks. Same CLI for developers
   and coding agents.