ace-git 0.30.0 → 0.30.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ecccf931f808308fde6ab00654e43fdcbe7b90e0f0c929ade43a25a427302756
-  data.tar.gz: 03af540433b453863a3d399a67565724c68288c0a4a2b283462f613293a4a6a0
+  metadata.gz: c03430c6a212d4bb6c51a3cb4bbf8f884051fe37b55581f9ea3d5d14048c83fa
+  data.tar.gz: e4da9c0fc2ae249ff7459973be3bfa42679395a68cb184e49446ea049aa5074f
 SHA512:
-  metadata.gz: c999f3855347dda4bfac0ce490ec94666f1e9e2cf00b2907d0ad72fa5c083e00495e0f4296036770d106bb1decddca02a37b495e71d87552344899a4321cba08
-  data.tar.gz: 0decf0ad84220579f16b3606d9c6ee3d6193e0a4dfbee22474cd4ee8008b5a75c6fc4bfc9f77bb8d27ae14fbdf65a3c95c957644ac318e08caffe03f7d0e768c
+  metadata.gz: 60ade30b905d89e860b44636d5520f7b5365612cbf4182692c3c06ca73a157b0d5811b4a3a8710a6b382180276ec4c8d488c4a156833af455d4baebcfd8a7797
+  data.tar.gz: e3dbbf14e495ac5bc6389079dd62d4c04a19f59ef4bc7d8d4a04507a63af5e52bc4ed734cadea17d6824d1cde353002bd4717bc9b4270282a670d42b72340983

data/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.30.1] - 2026-10-17
+
+### Changed
+
+- Document the ordinary local PR create/update/ready path; remove the protected worker boundary and `ace-lab service request/status` requirements from the git PR workflows and guide.
+- Document explicit remote read/compare reconciliation for an interrupted PR update instead of claiming the command compares and accepts the remote description; an interrupted create adopts one exact-head draft but does not compare or rewrite remote title/body.
+- Drop the `attempt-bound`/`execution-attempt` wording from the `as-git-pr-create` and `as-git-pr-update` skills; they wrap the same forge-neutral PR workflows.
+
+### Removed
+
+- Remove the protected merge boundary feature test and its fixture, which exercised the removed protected authority model.
+
 ## [0.30.0] - 2026-10-08
 
 ### Added

data/docs/handbook.md

@@ -9,6 +9,11 @@ ace-docs:
 
 # ace-git Handbook Catalog
 
+> **Planned (L5.5):** role rules, independent review rounds, and the
+> attempt-bound forge delivery workflow are not available yet. The PR
+> create/update skills below are projections of that planned workflow; the
+> ordinary `ace-git pr` CLI commands remain the supported local path.
+
 Reference for package-owned handbook resources in `ace-git/handbook/`.
 
 ## Skills

data/docs/usage.md

@@ -86,6 +86,7 @@ ace-git diff --raw
 ```
 
 **Options:**
+
 - `--format, -f` - Output format: `diff` (default), `summary`, `grouped-stats`
 - `--since, -s` - Changes since date/duration (e.g., "7d", "1 week ago")
 - `--paths, -p` - Include only these glob patterns
@@ -118,12 +119,14 @@ ace-git status --with-diff
 ```
 
 **Options:**
+
 - `--format, -f` - Output format: `markdown` (default), `json`
 - `--no-pr, -n` - Skip PR metadata and activity lookups (faster)
 - `--commits N` - Number of recent commits to show (default: 3 from config)
 - `--with-diff` - Include PR diff in output
 
 **Output includes:**
+
 - Current branch name with git status -sb output
 - Remote tracking status (ahead/behind)
 - Detected task pattern (from branch name)
@@ -153,6 +156,7 @@ ace-git branch --format json
 ```
 
 **Options:**
+
 - `--format, -f` - Output format: `text` (default), `json`
 
 ### `ace-git pr`
@@ -191,16 +195,24 @@ ace-git pr merge 25 --expected-head SHA --method squash
 ```
 
 **Behavior guarantees:**
+
 - Create is idempotent: one exact open base/head match returns the existing
+
   PR (`idempotency: existing`); multiple matches are a conflict.
+
 - `merge` requires the provider to enforce `--expected-head` atomically;
+
   providers without that capability return an unsupported-capability failure
   instead of racing.
+
 - A create request whose outcome is unknown (transport failure after send)
+
   reports an unknown outcome with the exact identity to reconcile; it never
   retries automatically.
+
 - With `--format json`, a failed operation prints the classified error as
-  JSON on stdout (`{"error": {"category": ..., "message": ...}}` — e.g.
+
+  JSON on stdout (`{"error": {"category": ..., "message": ...}}` -- e.g.
   `expected_head_conflict`, `unsupported_capability`, `unknown_outcome`)
   before the nonzero exit; text mode explains the same failure on stderr.
 
@@ -256,9 +268,10 @@ diff:
 | `grouped_stats.layers` | Array | `["lib","test","handbook"]` | Preferred layer grouping order |
 | `grouped_stats.collapse_above` | Integer | `5` | Collapse markdown groups above this file count |
 | `grouped_stats.show_full_tree` | String | `collapsible` | Tree rendering strategy hint |
-| `grouped_stats.dotfile_groups` | Array | `[".ace-task",".ace"]` | Dot-directories to prioritize in grouping |
+| `grouped_stats.dotfile_groups` | Array | `[".ace-tasks",".ace"]` | Dot-directories to prioritize in grouping |
 
 **Default exclude_patterns** (from `.ace-defaults/git/config.yml`):
+
 - Lock files: `**/*.lock`, `package-lock.json`, `yarn.lock`, `Gemfile.lock`
 - Vendored deps: `vendor/**/*`, `node_modules/**/*`
 - Build artifacts: `coverage/**/*`, `dist/**/*`, `build/**/*`, `.cache/**/*`
@@ -289,30 +302,24 @@ Note: `test/**/*` and `spec/**/*` are NOT excluded by default - test changes are
 
 ## Provider Packages
 
-`ace-git service create`, `service update`, `service ready` and `service merge`
-are fixed protected receiver handlers. It accepts no
-options; the receiver supplies its claimed JSON envelope on stdin and its
-private materialized candidate directory as the working directory. The handler
-checks the exact input digest, executor, candidate and forge provenance, calls
-the selected neutral operation once, and emits the existing bounded evidence
-response only after verifying the exact PR outcome (and merge commit for merge). An unverified or lost
-outcome emits no success and never retries. This command does not authorize a
-operation or replace the protected worker's canonical receipt acceptance.
-Create/update use an exact `{target,delivery,title,body}` input and remain draft;
-ready uses `{target,delivery}`, merge uses `{target,delivery,method}`. Create targets
-the base repository; all other operations target the exact PR URL. The original
-title remains part of the accepted input; the provider owns its draft encoding
-(Forgejo's WIP prefix). Updating a draft preserves that encoding. Each handler
-publishes the fixed `pr-result.txt` evidence only after its observed content,
-identity, head and draft/merge outcome agree.
+> **Planned (L5.5):** the forge-neutral worker/integrator role rules and the
+> attempt-bound PR delivery workflow are not available yet. The old protected
+> `service create|update|ready|merge` receiver handlers are not part of the
+> file-based flow and are not a requirement for opening or reviewing a PR.
+>
+> Use the ordinary `ace-git pr` commands documented above for now; they create
+> or reconcile a PR for the pushed branch.
 
 `ace-git` is forge-neutral. It defines the server registry (`Ace::Git::ServerRegistry`),
 the provider contract (`Ace::Git::Providers::Base`), and normalized evidence types;
 provider packages own all forge CLI behavior:
 
 - **ace-git-github** - GitHub behavior via the `gh` CLI (PR lookups, diffs, issue
+
   tracking operations). Registers under the `github` provider type.
+
 - **ace-git-forgejo** - Forgejo behavior via the `fj` CLI. Registers under the
+
   `forgejo` provider type.
 
 Both providers implement the same issue-tracking contract (issue lookup, comment

data/handbook/guides/version-control-system-git.g.md

@@ -21,7 +21,7 @@ This project uses a **mono-repo architecture** with all packages at the reposito
 
 - **ace-*/**: Ruby gems for specific functionality (ace-git, ace-task, ace-docs, etc.)
 - **docs/**: Project documentation and architecture decisions
-- **.ace-task/**: Task management and release coordination
+- **.ace-tasks/**: Task management and release coordination
 - **_legacy/**: Archived content from previous multi-repo structure
 
 #### Common Git Commands
@@ -183,18 +183,19 @@ git remote prune origin
    git push -u origin feature/your-feature
    ```
 
-2. **Create an attempt-bound draft on the selected forge**:
+2. **Create a draft on the selected forge**:
 
    ```bash
    ace-bundle wfi://git/pr/create
    ```
 
-   Use the managed assignment and active delivery attempt with explicit
-   fork/canonical repository and ref provenance. The canonical operation is
-   `ace-assign delivery --assignment ID --attempt ATTEMPT --operation create --title TITLE --body-file DESCRIPTION`.
+   Use the actual assignment and active attempt when the work belongs to an
+   assignment, with explicit fork/canonical repository and ref provenance. The
+   forge command is
+   `ace-git pr create --server NAME --head HEAD-REF --base BASE-REF --expected-head CANDIDATE-SHA --title TITLE --body-file DESCRIPTION --format json`.
    Preserve the resolved forge and exact candidate SHA. Continue through
-   `wfi://git/pr/update` only with accepted current test and independent review
-   receipts; CI status remains advisory. Inside ACE use source `bin/ace-*`.
+   `wfi://git/pr/update` only with current exact-head test and independent review
+   evidence; CI status remains advisory. Inside ACE use source `bin/ace-*`.
 
 3. **Link to relevant issues/tasks**:
 
@@ -225,8 +226,8 @@ git push --force-with-lease origin feature/your-feature
 
 #### Fork-Based Workflow
 
-Provider-specific GitHub clone example for external contributors; canonical
-assignment delivery above uses the explicitly selected forge and provenance:
+Provider-specific GitHub clone example for external contributors; the neutral
+draft/update flow above uses the explicitly selected forge and provenance:
 
 ```bash
 # Fork repository on GitHub, then:

data/handbook/skills/as-git-pr-create/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: as-git-pr-create
-description: Create an attempt-bound forge-neutral pull request
+description: Create a forge-neutral pull request
 user-invocable: true
 source: ace-git
 allowed-tools:
@@ -13,7 +13,7 @@ assign:
     - name: create-pr
       description: Create the exact assignment pull request
       produces: [pull-request]
-      consumes: [code-changes, execution-attempt]
+      consumes: [code-changes]
 skill:
   kind: workflow
   execution:

data/handbook/skills/as-git-pr-update/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: as-git-pr-update
-description: Update an attempt-bound forge-neutral pull request
+description: Update a forge-neutral pull request
 user-invocable: true
 source: ace-git
 allowed-tools:
@@ -13,7 +13,7 @@ assign:
     - name: update-pr-desc
       description: Update the exact assignment pull request
       produces: [pull-request]
-      consumes: [code-changes, execution-attempt]
+      consumes: [code-changes]
 skill:
   kind: workflow
   execution:

data/handbook/workflow-instructions/git/pr/create.wf.md

@@ -1,18 +1,18 @@
 ---
 doc-type: workflow
-title: Create an attempt-bound draft pull request
+title: Create a draft pull request
 purpose: Create or reconcile a forge-neutral draft for the exact candidate
 ---
 
-# Create an attempt-bound draft pull request
+# Create a draft pull request
 
 ## Goal
 
-Create one draft PR on the selected forge and retain its exact source/base identity in the assignment attempt journal.
+Create one draft PR on the selected forge and record its exact source/base identity in the assignment report.
 
 ## Prerequisites
 
-A reviewed task, managed assignment, active delivery attempt, committed candidate, and pushed source ref. Credentials permit transport only; they grant no integration authority.
+A reviewed task or explicit implementation scope, a committed candidate, and a pushed source ref. Credentials permit transport only; they grant no integration permission.
 
 ## Inputs
 
@@ -22,49 +22,21 @@ Use `forge_server` or `forge_default: true`, mutually exclusive. Neither means r
 {"forge_server":"forge-lab","pr_provenance":{"mode":"canonical","head_repository_url":"https://forge.example/team/repo","head_ref":"feature","base_repository_url":"https://forge.example/team/repo","base_ref":"main"}}
 ```
 
-## Protected worker boundary
-
-The steps below are ordinary managed delivery only. An installed protected
-participant uses the configured receiver and the original canonical authority,
-with no caller-local journal or direct-provider fallback.
-
-The authenticated worker may create/update a draft before independent review.
-Save a nonsecret input object with exactly `target`, `delivery`, `title`, `body`;
-`delivery` is the normalized original forge/provenance mapping. `target` has
-`resource` and nullable `artifact_digest`: the selected base repository URL for
-create, the exact recorded PR URL for update. Title/body are bounded UTF-8 text.
-Request the installed receiver with:
-
-```sh
-ace-lab service request --project PROJECT --assignment ID --attempt ATTEMPT \
-  --mapping MAPPING --scope SCOPE --service SERVICE --operation OPERATION \
-  --candidate-head SHA --candidate-generation CANDIDATE-GENERATION \
-  --expected-generation AUTHORITY-GENERATION --authorization AUTHORIZATION \
-  --request-id REQUEST --input INPUT.json
-```
-
-Use `create` or `update` as OPERATION; each requires its own exact scoped grant.
-The receiver runs the fixed `ace-git service create` or `service update` handler.
-A claim acknowledges admission, not PR success. Retain its complete selection
-and observe `ace-lab service status` as described in
-`wfi://handbook/perform-delivery`. Lost replies stay uncertain; status does not
-repeat an effect. Only canonical completion supplies the created PR URL.
-
-For ready, use the same request with OPERATION `ready` and input containing only
-`target` and `delivery`. Ready and merge require executed checks, accepted
-independent review for the current revision and the matching authorization.
-Local report/reference files cannot replace those canonical proofs. Draft
-creation/update does not grant readiness, merge or publication.
-
 ## Steps
 
 1. Read the task and actual committed diff; prepare a concrete title and description explaining behavior and executed validation. Save the description as a local file.
-2. Use the existing managed assignment and active delivery attempt IDs. If needed, start the delivery step with `ace-assign attempt start --assignment ID --step STEP --project PROJECT` (numeric step scope). The execution boundary supplies actor identity; do not impersonate a reviewer or integrator.
-3. Supply the assignment source's `delivery` mapping, or save the explicit input JSON and pass `--parameters FILE`. For task-mode creation, `ace-assign create --task TASK --delivery-parameters FILE` retains these inputs in the generated job.
-4. Execute `ace-assign delivery --assignment ID --attempt ATTEMPT --operation create --title TITLE --body-file DESCRIPTION`. Add `--parameters FILE` only when supplying an explicit file. In this repository invoke the source `bin/ace-assign` entrypoint.
-5. Read the structured result. Verify the retained server/provider/base and head repository/ref, draft PR number/URL, candidate SHA, base_head, evidence_git_ref, and separate journal_commit. The pushed ref must equal the candidate; journal commits never advance it.
-6. On interruption or unknown create outcome, repeat the delivery command to perform exact-selector reconciliation reads. One matching draft at the exact head is adopted without a second create. Zero remains unresolved; multiple matches conflict. Never bypass uncertainty with a direct provider command.
+2. When this work belongs to an assignment, use its actual ID and record the PR identity in the assignment report. The execution boundary supplies actor identity; do not impersonate a reviewer or integrator.
+3. Verify the pushed source ref resolves to the candidate SHA. The pushed ref must equal the candidate.
+4. Create the draft with the configured forge command; drafts are the default:
+
+   ```sh
+   ace-git pr create --server NAME --head HEAD-REF --head-repo HEAD-REPOSITORY-URL --base BASE-REF --expected-head CANDIDATE-SHA --title TITLE --body-file DESCRIPTION --format json
+   ```
+
+   Use the retained default/remote selection instead of `--server NAME` when applicable. In this repository invoke the source `bin/ace-git` entrypoint.
+5. Read the structured result. Verify the retained server/provider/base and head repository/ref, draft PR number/URL, candidate SHA and base head. Record the PR identity and observed candidate head in the assignment report.
+6. On interruption or an unknown create outcome, repeat the same command with the same selectors: the implementation re-reads open PRs and adopts one matching draft at the exact head without a second create. Adoption does not compare or rewrite the remote title/body, so verify the remote content explicitly before relying on it, and use `wfi://git/pr/update` if the description differs. Zero matches remain unresolved; multiple matches conflict. Never bypass an uncertain read with a different provider command.
 
 ## Success criteria
 
-The journal records exact identity, intent before the write, and proven draft outcome afterward. A report or shell exit alone proves nothing. Continue with actual tests and independent current-head review; keep the PR draft until those receipts are accepted. CI is visible and advisory. Publication is a separate authorized operation and is not required for delivery.
+The assignment report records exact identity and the proven draft outcome. A report or shell exit alone proves nothing. Continue with actual tests and independent current-head review; keep the PR draft until those results are accepted. CI is visible and advisory. Publication is a separate authorized operation and is not required for delivery.

data/handbook/workflow-instructions/git/pr/update.wf.md

@@ -1,10 +1,10 @@
 ---
 doc-type: workflow
-title: Update an attempt-bound pull request
-purpose: Update the exact forge-neutral PR and consume current delivery evidence
+title: Update a pull request
+purpose: Update the exact forge-neutral PR and record current delivery evidence
 ---
 
-# Update an attempt-bound pull request
+# Update a pull request
 
 ## Goal
 
@@ -12,51 +12,35 @@ Update the recorded PR description for the current candidate and preserve provid
 
 ## Prerequisites
 
-A managed assignment with a recorded PR and active delivery attempt. Reuse the original forge selection and complete fork/canonical provenance; changed configuration or identity is a conflict. A new committed candidate, including task-only changes, requires renewed tests and independent review.
-
-## Protected worker boundary
-
-The steps below are ordinary managed delivery only. An installed protected
-participant uses the configured receiver and the original canonical authority,
-with no caller-local journal or direct-provider fallback.
-
-The authenticated worker may create/update a draft before independent review.
-Save a nonsecret input object with exactly `target`, `delivery`, `title`, `body`;
-`delivery` is the normalized original forge/provenance mapping. `target` has
-`resource` and nullable `artifact_digest`: the selected base repository URL for
-create, the exact recorded PR URL for update. Title/body are bounded UTF-8 text.
-Request the installed receiver with:
-
-```sh
-ace-lab service request --project PROJECT --assignment ID --attempt ATTEMPT \
-  --mapping MAPPING --scope SCOPE --service SERVICE --operation OPERATION \
-  --candidate-head SHA --candidate-generation CANDIDATE-GENERATION \
-  --expected-generation AUTHORITY-GENERATION --authorization AUTHORIZATION \
-  --request-id REQUEST --input INPUT.json
-```
-
-Use `create` or `update` as OPERATION; each requires its own exact scoped grant.
-The receiver runs the fixed `ace-git service create` or `service update` handler.
-A claim acknowledges admission, not PR success. Retain its complete selection
-and observe `ace-lab service status` as described in
-`wfi://handbook/perform-delivery`. Lost replies stay uncertain; status does not
-repeat an effect. Only canonical completion supplies the created PR URL.
-
-For ready, use the same request with OPERATION `ready` and input containing only
-`target` and `delivery`. Ready and merge require executed checks, accepted
-independent review for the current revision and the matching authorization.
-Local report/reference files cannot replace those canonical proofs. Draft
-creation/update does not grant readiness, merge or publication.
+An assignment with a recorded PR, or an explicit local PR scope. Reuse the original forge selection and complete fork/canonical provenance; changed configuration or identity is a conflict. A new committed candidate, including task-only changes, requires renewed tests and independent review.
 
 ## Steps
 
-1. Inspect the committed changes and accepted test/review evidence. Prepare the final description with the concrete behavior, executed test results, independent verdict, and actual limitations. Save it as a local file; do not put credentials or terminal dumps in the attempt journal.
-2. Execute `ace-assign delivery --assignment ID --attempt ATTEMPT --operation update --body-file DESCRIPTION`. Supply `--parameters FILE` only if the assignment source lacks the original `delivery` mapping. In this repository use `bin/ace-assign`.
-3. On interrupted update, repeat the delivery command. It reads the exact remote title/body and compares the requested field digest before accepting; an unmatched or unreadable outcome remains unresolved. Never blindly resend a mutation.
-4. To mark ready, supply two JSON reference files, each containing only `attempt_id` and `receipt_digest`, from coordinator-accepted current-head test and independent review attempts in this assignment/project. Execute `ace-assign delivery --assignment ID --attempt ATTEMPT --operation ready --tests TEST-REF --review REVIEW-REF`. Missing, fabricated, stale, or self-approved evidence cannot authorize readiness. Red CI alone does not veto valid executed tests and review.
-5. Merge is an integrator/service operation under the existing exact qjx authorization policy. The authorized executor calls `ace-git pr merge IDENTIFIER --server NAME --expected-head CANDIDATE-SHA --method METHOD --format json` with the retained selection (or `--default-server`, otherwise remote resolution). Both expected SHA and the authorized squash/merge/rebase method are required; there is no default method. It does not recursively request its own future receipt. The worker consumes the completed, verified service receipt using `ace-assign delivery --assignment ID --attempt ATTEMPT --operation merge --tests TEST-REF --review REVIEW-REF --service-request REQUEST`. The request must bind this assignment, attempt, project, candidate and PR URL. No completed receipt means a routed blocker; credentials or caller assertions grant no authority.
-6. Unknown merge remains pending service reconciliation and is never automatically retried. Inspect the authoritative selected remote and verified executor evidence. Changed head or scope blocks acceptance. Merge does not authorize publication, deployment or synchronization.
+1. Inspect the committed changes and accepted test/review evidence. Prepare the final description with the concrete behavior, executed test results, independent verdict, and actual limitations. Save it as a local file; do not put credentials or terminal dumps in the assignment report.
+2. Update the PR with the configured forge command:
+
+   ```sh
+   ace-git pr update IDENTIFIER --server NAME --expected-head CANDIDATE-SHA --body-file DESCRIPTION --format json
+   ```
+
+   Use the retained default/remote selection instead of `--server NAME` when applicable. In this repository invoke the source `bin/ace-git` entrypoint.
+3. On an interrupted update, do not assume the command reconciles for you: `ace-git pr update` verifies the head and rewrites the title/body, so a retry is a new write. Explicitly read the exact remote title/body (for example `ace-git pr show IDENTIFIER --format json`), compare it with the prepared description; if identical, treat the update as done, otherwise re-run the command. An unreadable or uncertain read stays unresolved. Never blindly resend a mutation.
+4. Mark ready only after tests and independent review pass on the exact head. Record the executed tests and independent review evidence for that head, then run:
+
+   ```sh
+   ace-git pr ready IDENTIFIER --server NAME --expected-head CANDIDATE-SHA --format json
+   ```
+
+   Missing, stale, or self-approved evidence cannot authorize readiness. Red CI alone does not veto valid executed tests and review.
+5. Merge is a separate authorized operation for the exact candidate. The authorized executor runs:
+
+   ```sh
+   ace-git pr merge IDENTIFIER --server NAME --expected-head CANDIDATE-SHA --method METHOD --format json
+   ```
+
+   with the retained selection (or `--default-server`, otherwise remote resolution). Both the expected SHA and the authorized squash/merge/rebase method are required; there is no default method. Credentials or caller assertions grant no permission.
+6. An unknown merge remains an unresolved effect. Inspect the authoritative selected remote and the actual executor evidence; never retry blindly. Changed head or scope blocks acceptance. Merge does not authorize publication, deployment or synchronization.
 
 ## Success criteria
 
-The exact remote outcome and existing qjl evidence agree. Real artifacts, current executed tests, independent verdict and required authorization gate completion. Preserve unresolved history and distinct candidate_head/journal_commit. qkb.1 supplies installed charter/proposal/service adoption; this workflow does not fabricate that acceptance.
+The exact remote outcome and the locally recorded evidence agree. Real artifacts, current executed tests and an independent verdict gate completion. Preserve unresolved history and distinguish the candidate head from evidence commits.

data/lib/ace/git/version.rb

@@ -2,6 +2,6 @@
 
 module Ace
   module Git
-    VERSION = "0.30.0"
+    VERSION = "0.30.1"
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: ace-git
 version: !ruby/object:Gem::Version
-  version: 0.30.0
+  version: 0.30.1
 platform: ruby
 authors:
 - Michal Czyz
 bindir: exe
 cert_chain: []
-date: 2026-10-08 00:00:00.000000000 Z
+date: 2026-10-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ace-support-config