RubyGems - ace-handbook - Versions diffs - 0.35.0 → 0.36.0 - Mend

ace-handbook 0.35.0 → 0.36.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (7) hide show

checksums.yaml +4 -4
data/CHANGELOG.md +2 -689
data/handbook/skills/as-release-rubygems-publish/SKILL.md +4 -2
data/handbook/workflow-instructions/handbook/manage-overrides.wf.md +10 -7
data/handbook/workflow-instructions/handbook/perform-delivery.wf.md +40 -210
data/lib/ace/handbook/version.rb +1 -1
metadata +2 -2

checksums.yaml CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 363ae1e6cd89c714512860b8ca79d36d845dfe197b039b2bcedcf60c77548000
-  data.tar.gz: 077205f8a16622b6972759fa7038cf4fca5a8dcd866ba048f5aebc5bcd2d2ba1
+  metadata.gz: cac18c57b00e46385b7f258503503282b9d5bd31949d76a168438c168bd23b76
+  data.tar.gz: 5f06acc867427e2642d24060af02d07f1feede570043eaebb85b3dd0d54887d9
 SHA512:
-  metadata.gz: 8b32ee617623055b732bb731531d5039f6f1da1ea5a413cf3828e02ab38c08b93f6ce5bb18a97cfbbe29c9dc041adae39f3a370a205749ae791e404ed8266b19
-  data.tar.gz: 1de4da539f049133b9672cedb3575679b26089b6d3cbb2fb126aa9ddb4639391313e4bc4964a70699f7ae89df5e4cd5633c19d835c7c94e6b88bf38a2e66e1d0
+  metadata.gz: c21f87773ce724a9fb852d99a6b09d48531a626bb8c2f65596e19418db4a5b98112cd6b27684d1a634926a45de3b08bfe4ec4e6210ed56fa0fd8437a8e136948
+  data.tar.gz: bbcba1e96230949433396d2e51b7d5740f240baceda031c5993cac2acaba42eecbc50c5c92c2de5991dadccaf72a53c6e28ba438ea12dd0e189600b26b005de0

data/CHANGELOG.md CHANGED Viewed

@@ -7,697 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
-## [0.35.0] - 2026-10-08
-### Changed
-- Document standalone and protected delivery, current canonical campaign round/result handoff and scoped publication prerequisites. Keep source verification separate from installed Lab acceptance.
-- Route unavailable publication prerequisites through the original assignment failure/status owners without claiming protected publication or retry authority.
-- Route protected delivery through original worker merge request, canonical status and exact result consumption while preserving ordinary delivery and unresolved protected PR policy.
-## [0.34.0] - 2026-10-05
-### Changed
-- Canonical delivery consumes neutral attempt-bound PR operations, current executed test/independent review receipts and exact authorized merge evidence; optional release preparation remains separate from publication.
-## [0.33.0] - 2026-09-28
-### Added
-- Provider manifests may declare an optional `extensions_dir`; `ace-handbook sync` now projects extension assets from `ace-handbook-integration-*` packages (`handbook/extensions/**`) into that directory (idempotent copies; prunes only stale paths recorded in the `.ace-handbook-projection.json` receipt, leaving user-authored extensions untouched). Destinations are validated before anything is written; a failed projection rolls back overwritten **and** pruned assets so the previous installation stays complete and loadable, and the retry needs no manual cleanup. Sync summary output gains a `; extensions <dir> (N files, U updated, R removed)` segment when a provider projects extensions. `ProviderRegistry` exposes `extensions_dir(provider)` and `package_root(provider)`.
-## [0.32.0] - 2026-09-27
-### Added
-- Provider manifests may declare an optional `prompts_dir`; `ace-handbook sync` now projects canonical prompt templates from `ace-handbook-integration-*` packages (`handbook/prompts/*.md`) into that directory (idempotent writes; prunes only stale files carrying an `ace-handbook-integration-*` provenance marker, leaving user-authored templates untouched). Sync summary output gains a `; prompts <dir> (N prompts, U updated, R removed)` segment when a provider projects prompts.
-- Shipped `wfi://handbook/manage-overrides` (with paired skill `as-handbook-manage-overrides`): canonical override documentation covering all overridable surfaces (workflows, cookbooks, guides), the source-priority resolution rule, skills' non-overridability ("override the workflow the skill calls"), the `.agents/` sync-projection status, and planted-competitor verification probes.
-### Changed
-- Tightened `wfi://release/rubygems-publish` baseline guidance with an OTP-burst publication contract (build all artifacts before OTP; push in ≤5 concurrent waves; defer metadata verification) for project overlays.
-## [0.31.1] - 2026-09-02
-### Technical
-- Included in the coordinated all-package patch release preparation for ACE monorepo review.
-## [0.31.0] - 2026-08-12
-### Added
-- Shipped generic baseline `wfi://release/*` workflows (`local`, `bump-version`, `update-changelog`, `publish`, `rubygems-publish`) under `handbook/workflow-instructions/release/` so plain installs resolve release skills without monorepo overlays; defaults stay non-publishing until a project publication contract exists.
-## [0.30.3] - 2026-08-12
-### Technical
-- Raised the `ace-support-core` dependency floor to `~> 0.31` after the principles-first bootstrap guidance release.
-## [0.30.2] - 2026-08-12
-### Technical
-- Aligned gemspec dependency floors with current ACE package minor release lines and safe external minor dependency bumps (no major version jumps).
-## [0.30.1] - 2026-07-15
-### Fixed
-- Made the neutral `agents` projection recognize canonical skills targeting the full legacy provider set before
-  filtering unavailable provider manifests, so agents-only projects receive common workflows such as `as-git-commit`.
-## [0.30.0] - 2026-07-15
-### Added
-- Added agents projection coverage fields to `ace-handbook status` JSON and table output, including projection policy,
-  excluded skill count, and the reason for curated projections.
-### Technical
-- Added fast and E2E regression coverage for the neutral agents projection status contract.
-## [0.29.1] - 2026-06-30
-### Fixed
-- Treated skills targeting the legacy full provider set (`claude`, `codex`, `gemini`, `opencode`, `pi`) as compatible
-  with the default `agents` projection, so installed common ACE workflow skills such as `as-git-commit` are written to
-  `.agents/skills/` by plain `ace-handbook sync`.
-## [0.29.0] - 2026-06-30
-### Added
-- Added the built-in `agents` skill projection target, generating `.agents/skills/` for default handbook sync.
-### Changed
-- Changed plain `ace-handbook sync` and `ace-handbook status` to use the default/enabled projection set, with `agents` as the default when no providers are configured.
-- Allowed explicit provider sync, such as `ace-handbook sync --provider codex`, even when the provider is not part of the default enabled set unless it is explicitly disabled.
-### Technical
-- Added regression coverage for default `.agents/skills` projection, explicit Codex projection, disabled-provider blocking, and default status filtering.
-## [0.28.1] - 2026-04-23
-### Changed
-- Updated the monorepo setup cookbook to use `ace-config sync ace-llm-providers-cli` before handbook sync.
-## [0.28.0] - 2026-04-22
-### Changed
-- **ace-handbook v0.28.0**: Added the local release workflow (`release/local`) and switched the package release workflow to a local-only preparation flow.
-### Technical
-- **ace-handbook v0.28.0**: Kept `as-release` behavior focused on local release prep without publishing to RubyGems.
-## [0.27.4] - 2026-04-16
-### Technical
-- Updated `TS-HANDBOOK-001` sandbox setup to source `mise.toml` from `${ACE_E2E_SOURCE_ROOT:-$PROJECT_ROOT_PATH}` so handbook smoke flows stay aligned with the shared read-only source-root contract.
-## [0.27.3] - 2026-04-15
-### Fixed
-- Corrected `TS-HANDBOOK-002` setup to copy `mise.toml` from `${ACE_E2E_SOURCE_ROOT:-$PROJECT_ROOT_PATH}` so sandboxed E2E runs load source-root tooling consistently.
-### Changed
-- Corrected release-proof command references to use positional `ace-test-e2e ace-monorepo-e2e TS-MONO-001` invocation.
-## [0.27.2] - 2026-04-15
-### Changed
-- Updated RubyGems propagation proof docs to use the supported positional `ace-test-e2e ace-monorepo-e2e TS-MONO-001` invocation and current scenario path.
-## [0.27.0] - 2026-04-14
-### Changed
-- Rewrote `ace-handbook` E2E coverage to public-surface goal style by retaining the CLI smoke flow and adding `TS-HANDBOOK-002` sync/provider-error behavior scenarios.
-- Tightened `TS-HANDBOOK-001` verifier contracts to prioritize user-visible output and enforce stronger status JSON shape expectations.
-### Technical
-- Updated usage guidance with explicit `sync --provider` and unknown-provider error-path examples aligned to the E2E public contract.
-## [0.26.2] - 2026-04-13
-### Changed
-- Documented `cookbook://` wildcard deduplication semantics in usage guidance, including canonical-path behavior and priority-preserving source selection notes.
-## [0.26.1] - 2026-04-13
-### Changed
-- Completed the batch i05 migration follow-through for this package and aligned it with the restarted `fast` / `feat` / `e2e` verification model.
-### Technical
-- Included in the coordinated assignment-driven patch release for batch i05 package updates.
-## [0.26.0] - 2026-04-12
-### Changed
-- Migrated `ace-handbook` package tests to the `fast` / `feat` / `e2e` contract by moving deterministic suites under `test/fast`, retaining workflow-value CLI smoke E2E coverage, and aligning scenario metadata with the new deterministic paths.
-- Updated package docs (`README`, getting-started, usage) to teach the `ace-test ace-handbook`, optional `ace-test ace-handbook feat`, `ace-test ace-handbook all`, and `ace-test-e2e ace-handbook` verification contract.
-## [0.25.4] - 2026-04-10
-### Technical
-- Updated handbook docs and cookbook guidance to point at the restarted E2E testing flows and current release-proof references.
-## [0.25.3] - 2026-04-05
-### Fixed
-- Scoped canonical skill inventory discovery to in-project defaults and explicitly registered external sources so status and sync no longer pick up ambient installed gems.
-## [0.25.2] - 2026-04-01
-### Changed
-- Updated cookbook management/review workflows to embed canonical cookbook standards and storage-path guidance directly, keeping the workflows self-contained.
-- Clarified cookbook path standards by explicitly distinguishing package-owned cookbooks (`ace-handbook/handbook/cookbooks/`) from project-local overlays (`.ace-handbook/cookbooks/`) in workflow/docs references.
-## [0.25.1] - 2026-04-01
-### Fixed
-- Corrected Astro cookbook setup commands to reference supported `ace-handbook` CLI behavior (`sync` / `status` flow), removing obsolete `ace-handbook init` guidance.
-### Changed
-- Added `.ace-handbook/cookbooks` to usage docs and standardized cookbook-review skill `argument-hint` metadata formatting.
-## [0.25.0] - 2026-04-01
-### Added
-- Added cookbook-first handbook surface with `wfi://handbook/manage-cookbooks` and `wfi://handbook/review-cookbooks` workflows plus canonical cookbook skills (`as-handbook-manage-cookbooks`, `as-handbook-review-cookbooks`) and provider projections.
-- Added canonical handbook-owned cookbook examples for Astro project setup and multi-ruby-gem monorepo setup, including explicit provenance and downstream propagation guidance.
-### Changed
-- Updated README, handbook/usage references, and cookbook template standards to treat `.cookbook.md` as a first-class handbook asset with explicit provenance and concise propagation guidance.
-## [0.23.5] - 2026-03-31
-### Changed
-- Replaced `wfi://release/rubygems-verify-install` workflow with E2E scenario `TS-MONO-001-rubygems-install` in `ace-monorepo-e2e/`. Updated all skill and doc references to use `ace-test-e2e ace-monorepo-e2e TS-MONO-001`.
-## [0.23.4] - 2026-03-31
-### Changed
-- Shipped default sync config with no providers pre-enabled so users choose their own agent integrations.
-- Reorganized install instructions across README, quick-start, and DEVELOPMENT docs by toolkit building blocks (Plan, Build, Context, QA, Git) with all gems in `development, test` group.
-## [0.23.3] - 2026-03-31
-### Changed
-- Extracted RubyGems installation verification into standalone `wfi://release/rubygems-verify-install` workflow with mise-based sandbox isolation.
-- Updated `as-release-rubygems-publish` skill to recommend the standalone verification workflow instead of requiring inline proof classification.
-## [0.23.2] - 2026-03-30
-### Technical
-- Added edge-case regression coverage for `ProviderSyncer#summarize_sources`, including empty inventory handling and nil/blank source normalization.
-## [0.23.1] - 2026-03-30
-### Fixed
-- Restored `Bash(gem:*)` permissions in the canonical `as-release-rubygems-publish` skill so release workflows can invoke gem commands directly.
-### Technical
-- Added regression coverage for projected release skill permissions to prevent permission drift.
-## [0.23.0] - 2026-03-30
-### Changed
-- Clarified `ace-handbook sync` output by adding inventory source counts and explicit rerun guidance when only one source is discovered.
-- Expanded `ace-handbook` docs to define `.ace-handbook/` as the canonical project-level handbook root for workflows, guides, templates, and skills in normal projects.
-### Technical
-- Added CLI sync command regression coverage for inventory-source summary and single-source guidance output.
-## [0.22.0] - 2026-03-29
-### Changed
-- Added a deterministic RubyGems propagation proof gate to coordinated release workflows with explicit `SAFE`, `LAG_DETECTED`, and `METADATA_BROKEN` classification outcomes.
-### Technical
-- Added operator-facing proof contract documentation and synchronized `as-release-rubygems-publish` skill guidance with the updated release workflow expectations.
-## [0.21.4] - 2026-03-29
-### Technical
-- Normalized published gem metadata so RubyGems and Ruby Toolbox use current release information instead of the 1980 fallback date.
-## [0.21.3] - 2026-03-29
-### Changed
-- Updated the coordinated release workflow so packages pulled in only by internal dependency constraint bumps are auto-added as follower releases and default to a patch bump with full version/changelog metadata.
-- Updated projected `as-release` skill guidance to make the new follower-package patch-release policy explicit across provider integrations.
-## [0.21.2] - 2026-03-29
-### Technical
-- Register package-level `.ace-defaults` skill-sources for ace-handbook to enable canonical skill discovery in fresh installs.
-## [0.21.1] - 2026-03-29
-### Fixed
-- **ace-handbook v0.21.1**: Bumped dependency constraints to currently available `~>` ranges on RubyGems and updated release metadata after dependency synchronization.
-## [0.21.0] - 2026-03-28
-### Changed
-- Migrated most RubyGems publish decision logic into `wfi://release/rubygems-publish`, keeping `as-release-rubygems-publish` as a thin workflow wrapper.
-### Technical
-- Removed skill-local pending-release-discovery preference logic and aligned the workflow with build-first + single-OTP publish behavior.
-## [0.20.0] - 2026-03-28
-### Added
-- Added `bin/ace-rubygems-needs-release` to derive pending ACE RubyGems releases from a single remote snapshot instead of querying each gem individually.
-### Changed
-- Updated the RubyGems publish workflow to prefer the helper script when available and corrected the fallback `gem search --exact` guidance.
-- Updated `as-release-rubygems-publish` skill instructions to prefer the helper script for pending-release discovery.
-## [0.19.0] - 2026-03-23
-### Added
-- New use case in README documenting `ace-handbook sync` and `ace-handbook status` CLI commands.
-- Added `as-release`, `as-release-bump-version`, `as-release-rubygems-publish`, and `as-release-update-changelog` to the handbook skills reference table.
-- Re-recorded getting-started demo GIF showcasing provider status and sync workflows.
-### Fixed
-- Fixed broken `[ace-nav](../ace-nav)` cross-link in README -- corrected to `[ace-nav](../ace-support-nav)`.
-- Fixed incorrect `ace-integration-*` package reference in README -- corrected to `ace-handbook-integration-*`.
-### Changed
-- Aligned gemspec description wording with summary for consistency.
-- Removed stale `mise` prerequisite from `docs/getting-started.md`.
-- Rewrote demo tape to focus on `ace-handbook status` and `ace-handbook sync --provider pi`.
-## [0.18.3] - 2026-03-23
-### Changed
-- Refreshed `README.md` to the current package layout pattern with quick-link navigation, use-case framing, and normalized section order.
-## [0.18.2] - 2026-03-22
-### Changed
-- Updated `docs/getting-started.md` to remove contradictory `mise exec --` prose and align onboarding guidance with direct `ace-*` command usage.
-- Documented intentional retirement of projected provider `as-idea-capture` and `as-idea-capture-features` skill files after canonical source removal.
-## [0.18.1] - 2026-03-22
-### Changed
-- Remove `mise exec --` wrapper from test fixture strings and canonical skill docs.
-- Document intentional retirement of projected provider `as-idea-capture` and `as-idea-capture-features` skill files after canonical source removal.
-## [0.18.0] - 2026-03-22
-### Changed
-- Reworked `ace-handbook` documentation into a landing-page README with package-focused messaging and links to dedicated docs.
-- Added `docs/getting-started.md`, `docs/usage.md`, and `docs/handbook.md` with tutorial and workflow/skill reference coverage.
-- Added demo assets under `docs/demo/` and aligned examples to the current `ace-nav resolve/list` command pattern.
-- Updated gem metadata summary/description to match the new README tagline and documentation positioning.
-## [0.17.1] - 2026-03-21
-### Added
-- Add RubyGems publish workflow (`wfi://release/rubygems-publish`) for publishing ACE gems in dependency order with credential verification, conflict detection, and dry-run support.
-- Add `as-release-rubygems-publish` skill for invoking the RubyGems publish workflow.
-## [0.17.0] - 2026-03-21
-### Changed
-- Added initial `TS-HANDBOOK-001` value-gated smoke E2E coverage for `ace-handbook` CLI help and status command contracts.
-## [0.16.1] - 2026-03-18
-### Changed
-- Migrated CLI namespace from `Ace::Core::CLI::*` to `Ace::Support::Cli::*` (ace-support-cli is now the canonical home for CLI infrastructure).
-## [0.16.0] - 2026-03-18
-### Changed
-- Removed legacy backward-compatibility behavior as part of the 0.10 cleanup release.
-## [0.15.9] - 2026-03-18
-### Fixed
-- Updated `cli-support-cli.g.md` guide to remove stale `DryCli::` namespace prefix from `VersionCommand` and `HelpCommand` class references.
-## [0.15.8] - 2026-03-17
+## [0.36.0] - 2026-10-20
 ### Changed
-- Updated `cli-support-cli.g.md` examples to the current `ace-support-cli` API (`RegistryDsl`, `Runner`, and `coerce_types`).
-- Updated review workflow docs to reflect 15-minute timeout guidance for long PR review runs.
-## [0.15.7] - 2026-03-15
-### Changed
-- Migrated CLI framework from dry-cli to ace-support-cli
-## [0.15.6] - 2026-03-13
-### Changed
-- Updated handbook-owned canonical skills to explicitly run bundled workflows in the current project and execute them end-to-end.
-### Technical
-- Refreshed provider sync and status collector regression coverage for the new compact canonical skill execution template.
-## [0.15.5] - 2026-03-13
-### Changed
-- Removed provider-specific skill body rendering so projected provider skills once again apply frontmatter overrides while preserving the canonical skill body unchanged.
-- Updated the canonical `as-release` skill to use the unified arguments / variables / execution structure with explicit workflow-execution guidance.
-- Limited provider-specific forking for `as-release` to Claude frontmatter only.
-### Technical
-- Simplified handbook projection coverage to validate frontmatter override projection and canonical body preservation instead of provider-specific body rendering.
-## [0.15.4] - 2026-03-13
-### Changed
-- Strengthened projected workflow skill instructions for Codex delegated execution and forked provider contexts so generated provider skills explicitly load and execute workflows in the current project instead of only reading or summarizing them.
-### Technical
-- Added projection regression coverage for strong workflow-execution rendering in both Codex `context: ace-llm` mode and provider `context: fork` mode.
-## [0.15.3] - 2026-03-13
-### Changed
-- Render Codex `ace-llm` skills from canonical frontmatter by deriving uppercase variables from `argument-hint` and generating `## Variables` / `## Instructions` sections for projected Codex skills.
-### Technical
-- Added projection regression coverage for `context: ace-llm` rendering and argument-hint-derived Codex variable generation.
-## [0.15.2] - 2026-03-12
-### Fixed
-- Preserved conditional `--sandbox` workflow routing in provider-synced skill projections so generated Claude and Codex skills keep the canonical E2E execute path.
-### Technical
-- Added provider-sync regression coverage for conditional workflow bodies in projected skills.
-## [0.15.1] - 2026-03-12
-### Changed
-- Updated handbook README, workflow docs, and guidance to document bundle-first workflow usage and the current handbook structure.
-## [0.15.0] - 2026-03-12
-### Added
-- Added Codex-specific delegated execution metadata to the canonical `as-release-bump-version` and `as-release-update-changelog` skills so the generated Codex skills run in fork context on `gpt-5.3-codex-spark`.
-## [0.14.1] - 2026-03-12
-### Technical
-- Updated provider sync regression coverage to verify provider-specific `context` and `model` overrides on projected git-commit skills and to keep generated provider output free of canonical `integration` metadata.
-## [0.14.0] - 2026-03-12
-### Changed
-- Changed canonical handbook skill inventory to load from registered `skill://` sources via `ace-support-nav` instead of scanning monorepo package directories directly.
-### Technical
-- Added nav-backed inventory regression coverage and explicit skill-source registration fixtures for handbook sync/status tests.
-## [0.13.1] - 2026-03-12
-### Technical
-- Added regression coverage for the `.agent/skills` retirement so handbook sync/status changes are exercised against provider-native skill trees only.
-## [0.13.0] - 2026-03-12
-### Added
-- Added canonical skill inventory counts by `source` to `ace-handbook status` output and JSON responses.
-### Changed
-- Expanded provider status reporting to show expected, installed, in-sync, outdated, missing, and extra skill counts, including comparisons through symlinked provider directories.
-## [0.12.0] - 2026-03-10
-### Added
-- Added a public `ace-handbook` CLI with `sync` and `status` commands for projecting canonical package skills into provider-native folders.
-- Added provider manifest discovery and sync/status coverage for handbook integrations, including replacement of legacy provider skill symlinks with real provider directories.
-### Changed
-- Moved handbook integration execution to `ace-handbook` while provider packages now supply thin provider manifests for projection targets.
-## [0.11.0] - 2026-03-10
-### Added
-- Added canonical handbook-owned skills for handbook management, release workflows, and research/delivery orchestration.
-## [0.10.0] - 2026-03-08
-### Added
-- New `release/publish` workflow for coordinated multi-package releases that auto-detect modified packages, update package and root changelogs, and finish with one release commit.
-### Changed
-- `/as-release` now loads `wfi://release/publish`, and release documentation now points to the canonical workflow path.
-## [0.9.9] - 2026-03-04
-### Changed
-- Update `perform-delivery` workflow PR skill references from `/ace-git-create-pr` to `/ace-github-pr-create`
-## [0.9.8] - 2026-02-25
-### Changed
-- Update `perform-delivery` workflow task lookup guidance to use `ace-task show <ref>` for explicit task selection.
-## [0.9.7] - 2026-02-22
-### Technical
-- Update `ace-bundle project` → `ace-bundle load project` in update-docs workflow
-## [0.9.6] - 2026-02-22
-### Changed
-- Migrate skill naming and invocation references to hyphenated `ace-*` format (no underscores).
-## [0.9.5] - 2026-02-21
-### Added
-- "Redundant computation" root cause category in selfimprove workflow with fix template showing compute-once-pass-explicitly pattern
-## [0.9.4] - 2026-02-20
-### Technical
-- Update /ace:create-pr to /ace:git-create-pr in perform-delivery workflow
-## [0.9.3] - 2026-02-20
-### Technical
-- Update stale wfi:// references in workflow definition guide
-## [0.9.2] - 2026-02-19
-### Technical
-- Namespace workflow instructions into handbook/ subdirectory with updated wfi:// URIs
-- Update skill name references to use namespaced ace:handbook-action format
-## [0.9.1] - 2026-02-04
-### Added
-- Preference hierarchy for search targets in selfimprove workflow (workflows/guides preferred over skills)
-## [0.9.0] - 2026-02-03
-### Added
-- Self-improve workflow (`selfimprove.wf.md`) for transforming agent mistakes into system improvements
-## [0.8.0] - 2026-01-31
-### Added
-- Multi-agent research synthesis capabilities (Task 254):
-  - `multi-agent-research.g.md` guide explaining when/how to use parallel agents
-  - `research-comparison.template.md` for structured synthesis comparison
-  - `parallel-research.wf.md` workflow for setting up parallel agent research
-  - `synthesize-research.wf.md` workflow for combining agent outputs
-  - `research.wf.md` with single/multi-agent decision criteria
-- Template protocol source configuration for ace-handbook templates
-## [0.7.1] - 2026-01-29
-### Fixed
-- Refine exit code handling documentation for dry-cli framework with exception-based pattern
-## [0.7.0] - 2026-01-22
-### Added
-- New guides extracted from ace-gems.g.md for better discoverability:
-  - `prompt-caching.g.md` - PromptCacheManager patterns for LLM prompt generation
-  - `cli-dry-cli.g.md` - Complete dry-cli framework reference
-  - `mono-repo-patterns.g.md` - Mono-repo development patterns and binstubs
-- Document IO isolation and testing pyramid patterns
-### Technical
-- Lower Ruby version requirement to >= 3.2.0
-## [0.6.0] - 2026-01-18
-### Added
-- Add perform-delivery workflow for multi-step delivery tracking with automatic TodoWrite externalization
-### Technical
-- Update guides for bundle terminology
-## [0.5.2] - 2026-01-16
-### Changed
-- Rename context: to bundle: keys in configuration files
-## [0.5.1] - 2026-01-08
-### Fixed
-- Fixed `guide://` protocol links in ace-test-runner guides (added `.g` suffix for `.g.md` files)
-- Cross-gem guide:// links now properly resolve to resources with `.g` extension
-## [0.5.0] - 2026-01-08
-### Added
-- Migrated 10 generic guides from dev-handbook to handbook/guides/
-  - ai-agent-integration.g.md, atom-pattern.g.md, changelog.g.md
-  - coding-standards.g.md, debug-troubleshooting.g.md, error-handling.g.md
-  - performance.g.md, quality-assurance.g.md, strategic-planning.g.md
-- Migrated 5 meta-guides to handbook/guides/meta/
-  - agents-definition.g.md, guides-definition.g.md, markdown-definition.g.md
-  - tools-definition.g.md, workflow-instructions-definition.g.md
-- Guide subdirectories with language-specific content (ruby, rust, typescript)
-- initialize-project-structure.wf.md workflow for project setup
-- Templates: cookbooks/cookbook.template.md, completed-work-documentation.md
-- Template discovery protocol (.ace-defaults/nav/protocols/tmpl-sources/)
-### Changed
-- Consolidates dev-handbook content into ace-handbook gem
-- All development guides now distributed with gem installation
-## [0.4.0] - 2026-01-03
-### Added
-- Guides support with handbook/guides/ directory
-- workflow-context-embedding.g.md guide for embed_document_source pattern
-- Guide discovery protocol (.ace-defaults/nav/protocols/guide-sources/ace-handbook.yml)
-## [0.3.0] - 2026-01-03
-### Changed
-- **BREAKING**: Minimum Ruby version raised to 3.3.0 (was 3.1.0)
-- Standardized gemspec file patterns with deterministic Dir.glob
-- Added MIT LICENSE file
-## [0.2.0] - 2025-12-30
-### Changed
-* Rename `.ace.example/` to `.ace-defaults/` for gem defaults directory
-## [0.1.0] - 2025-11-05
-### Added
-- Initial release of ace-handbook gem as pure workflow package
-- 6 handbook management workflows accessible via wfi:// protocol:
-  - `wfi://manage-guides` - Create and update development guides
-  - `wfi://review-guides` - Review guides for quality and consistency
-  - `wfi://manage-workflow-instructions` - Create and validate workflow files
-  - `wfi://review-workflows` - Review workflow instructions
-  - `wfi://manage-agents` - Create and update agent definitions
-  - `wfi://update-handbook-docs` - Update handbook README and structure
-- Path references updated for project-relative usage
-- Complete gem structure following ACE patterns
-- Comprehensive documentation and usage examples
-- Auto-discovery support through ace-nav gem
-### Changed
-- Migrated workflows from dev-handbook/.meta/wfi/ to installable gem
-- Updated path references to be project-root relative
-- Removed dev-handbook specific dependencies
-### Removed
-- Moved `update-tools-docs.wf.md` to ace-docs package (tools documentation management)
-- Moved `update-integration-claude.wf.md` to ace-integration-claude package (Claude Code integration)
-### Fixed
-- Added ace-nav protocol registration (.ace.example/nav/protocols/wfi-sources/ace-handbook.yml)
-- Updated gemspec to include protocol registration files for proper discovery
-### Technical Details
+- Remove the attempt/authority requirement from `wfi://handbook/perform-delivery`: record actual artifacts, executed checks and the independent reviewer verdict in the assignment report instead of attempt receipts; managed delivery remains planned for L5.5.
-- Pure workflow package with no Ruby runtime dependencies
-- Auto-discovery via ace-nav through handbook/workflow-instructions/ directory
-- Protocol registration enables ace-nav to discover workflows from installed gem
-- Template embedding framework ready for ADR-002 compliance
-- Standard ACE gem structure with lib/, handbook/, gemspec, README, CHANGELOG

data/handbook/skills/as-release-rubygems-publish/SKILL.md CHANGED Viewed

@@ -9,8 +9,8 @@ allowed-tools:
   - Bash(gem:*)
   - Bash(ace-bundle:*)
   - Read
-argument-hint: "[gem-name...] [--dry-run]"
-last_modified: 2026-08-12
+argument-hint: "[gem-name...] [--dry-run|--prepare]"
+last_modified: 2026-10-17
 source: ace-handbook
 integration:
   targets:
@@ -47,5 +47,7 @@ None
 - Do the work described by the workflow instead of only summarizing it.
 - When the workflow requires edits, tests, or commits, perform them in this project.
 - OTP timing: build every pending `.gem` first, then ask for one OTP (~30–45s), then push in ≤5-concurrent dependency waves aiming to finish within ~30s; verify metadata only after the burst.
+- Last-mile handoff: the agent shell is not the operator shell. Missing `GEM_HOST_API_KEY` / `~/.gem/credentials` (or no TTY) in the agent's subprocesses never means the operator is unconfigured — do not request credential setup. Finish the dry-run, state the wave plan, and hand off exactly `.ace-bin/ace-rubygems-publish --interactive` for the operator terminal (`--prepare` is optional; the live run re-resolves a stale prepared queue). If the operator explicitly authorizes agent-driven publishing, request one fresh OTP via `ace-hitl`/chat, wait for it, then run the publisher with `GEM_HOST_OTP_CODE` in the environment and never persist the OTP.
+- Never re-run the publisher to confirm a completed release, and never replace the `TS-MONO-001` propagation proof with hand-rolled `bundle install` runs; if the agent runner is unavailable, report the blocked command and hand it off.
 - After live publishing, recommend running `ace-test-e2e ace-monorepo-e2e TS-MONO-001` for installation verification.

data/handbook/workflow-instructions/handbook/manage-overrides.wf.md CHANGED Viewed

@@ -34,7 +34,7 @@ per URI.
 | Surface | Protocol | Project-local location | Overridable? | Winner of duplicates (shipped defaults) |
 |---------|----------|------------------------|--------------|------------------------------------------|
-| Workflows | `wfi://` | `.ace-handbook/workflow-instructions/<ns>/<name>.wf.md` | Yes | Project-local, when its source priority is lower than the gem source's (e.g. the shipped `local` source at priority 5 vs gem at 10) |
+| Workflows | `wfi://` | `.ace-handbook/workflow-instructions/<ns>/<name>.wf.md` | Yes | Project-local, when its source priority is lower than the gem source's (e.g. this monorepo's checked-in `local` source at priority 5 vs gem at 10) |
 | Cookbooks | `cookbook://` | `.ace-handbook/cookbooks/<name>.cookbook.md` | Yes | The candidate from the source with the lower priority number. The shipped project-local default registers priority 20 and the gem source 10, so **the gem wins by default**; register a project cookbook source with priority < 10 to make project-local win |
 | Guides | `guide://` | `handbook/guides/<name>.g.md` | Yes, with registration | Requires a project source registration (`.ace/nav/protocols/guide-sources/local.yml` → `handbook/guides`); with priority < 10 the project-local guide wins. Without registration the gem wins |
 | Skills | `skill://` | none | **No** | Always the gem. Skills are thin layers; override the workflow the skill calls instead |
@@ -44,9 +44,9 @@ per URI.
 Sources for a protocol are scanned in ascending priority order (lower number = higher precedence); the first source
 containing the resource wins and remaining duplicates are ignored. Registration defaults: project sources 10, user
-sources 50, gem defaults 100 — an individual source registration may pin another value (this is why the shipped
-`local` workflow source at priority 5 beats the gem at 10, while the shipped project-local cookbook source at 20 loses
-to the gem at 10).
+sources 50, gem defaults 100 — an individual source registration may pin another value. In this monorepo, the checked-in
+`.ace/nav/protocols/wfi-sources/local.yml` sets priority 5 and beats the gem at 10; downstream projects must register
+their own local workflow source. The shipped project-local cookbook source at 20 loses to the gem at 10.
 To answer "why did this candidate win?" for a concrete URI without planting probe files:
@@ -73,7 +73,8 @@ are ignored and resolution always returns the gem file. The design rule is: **ov
 2. **Create the project-local file** at the surface's project-local location (see table), keeping the canonical
    frontmatter and structure so tools keep resolving it.
 3. **Ensure the source registration makes your file win:**
-   - workflows: keep `.ace/nav/protocols/wfi-sources/local.yml` priority below the gem source (shipped default: 5).
+   - workflows: register `.ace/nav/protocols/wfi-sources/local.yml` with priority below the gem source; this monorepo's
+     checked-in registration uses 5, but downstream projects do not receive that project-local source by default.
    - cookbooks: register `.ace/nav/protocols/cookbook-sources/local.yml` with priority < 10 (the shipped
      project-local default of 20 loses to the gem's 10).
    - guides: register `.ace/nav/protocols/guide-sources/local.yml` pointing at `handbook/guides` with priority < 10;
@@ -135,8 +136,10 @@ ace-handbook sync                                      # regenerates .agents/ski
 - **Override silently loses:** inspect `ace-nav resolve <uri> --why`; the losing candidate's source priority is too
   high — lower it in the source registration.
-- **Guide override not discovered at all:** no project guide source is registered; add
-  `.ace/nav/protocols/guide-sources/local.yml` (see Process Step 3).
+- **Guide override does not win:** a planted guide may be discovered as a losing candidate through the
+  `@ace-support-nav` gem-default example source (`./handbook/guides`, priority 100), or it may be absent from the
+  candidates, depending on source registration. Register `.ace/nav/protocols/guide-sources/local.yml` with priority
+  below the gem source (see Process Step 3), then confirm the project candidate wins with `ace-nav resolve --why`.
 - **Skill edit appears to do nothing:** skills are not overridable; override the workflow the skill calls.
 - **`.agents/skills/` edits keep disappearing:** expected — `ace-handbook sync` regenerates the projection and prunes
   stale entries; edit canonical skills in the owning gem.

data/handbook/workflow-instructions/handbook/perform-delivery.wf.md CHANGED Viewed

@@ -1,42 +1,35 @@
 ---
 doc-type: workflow
-title: Perform attempt-bound delivery
+title: Perform delivery
 purpose: Coordinate implementation, exact-head review and authorized delivery on the selected forge
 ---
-# Perform attempt-bound delivery
+# Perform delivery
 ## Goal
-Deliver one committed candidate in explicit standalone or managed mode, using
-the selected forge and current executed tests and independent review.
+Deliver one committed candidate, using the selected forge and current executed
+tests and independent review.
 ## Prerequisites
 - A reviewed task or an explicit implementation scope and project.
-- For managed delivery, a managed assignment and an active scoped attempt for each
-  delivery action; use the actual assignment and
-  attempt IDs from the execution boundary, never caller-invented actor identity.
 - For remote delivery, a pushed candidate and explicit fork/canonical provenance:
   mode, head_repository_url, head_ref, base_repository_url and base_ref.
 - An applicable authorization for each effect. Transport credentials do not grant
   permission to merge, publish, deploy or synchronize.
 Choose standalone mode for ordinary local task/inline implementation, tests, review
-and optional requested version/changelog preparation without a managed assignment.
-Choose managed mode when the request supplies an assignment or requires its
-canonical attempt/receipt boundary. Standalone output cannot satisfy managed or
-protected acceptance. Local-only implementation needs no forge selection or
-scoped attempt. If remote delivery is requested,
+and optional requested version/changelog preparation. Local-only implementation
+needs no forge selection or assignment scope. If remote delivery is requested,
 use forge_server or forge_default: true, mutually exclusive; otherwise use the
 repository remote. Preserve the first resolved server/repository/PR identity
-throughout the assignment. Missing service or authorization yields a specific
-blocker; this workflow does not invent grants or impersonate an integrator.
+throughout the work. Managed delivery and its role handoff land in L5.5; this workflow does not invent grants or impersonate an integrator.
 ## Project context loading
-Read the task or inline scope and actual committed diff. In managed mode also
-read assignment status, current attempt and retained delivery parameters. If a PR
+Read the task or inline scope and actual committed diff. When the work belongs to
+an assignment, also read assignment status and its step reports. If a PR
 is recorded, inspect it with
 `ace-git pr show IDENTIFIER --format json --server NAME` using the retained selection
 (or `--default-server`, otherwise remote resolution). Inside ACE use source
@@ -63,8 +56,8 @@ and test it on the combined candidate before declaring that result delivered.
 Implement and commit the requested local task/inline scope using existing task
 and Git tools. Execute appropriate tests and independent review, retain their
 actual artifact references and candidate SHA, and record unfinished criteria.
-No managed assignment, protected service receipt or canonical qjl acceptance is
-claimed by this route. Local scope may end here.
+No managed assignment boundary is claimed by this route.
+Local scope may end here.
 For an explicitly authorized standalone remote scope, use existing neutral
 primitives on the chosen base repository/forge. Record actual head/base
@@ -84,7 +77,6 @@ the low-level PR command does not establish these gates itself. Readiness uses
 `ace-git pr ready IDENTIFIER --server NAME --expected-head CANDIDATE-SHA --format json`.
 Only an actually authorized standalone integrator may call
 `ace-git pr merge IDENTIFIER --server NAME --expected-head CANDIDATE-SHA --method METHOD --format json`.
-This is not a worker fallback when a managed/protected service is unavailable.
 Remote errors or uncertain effects remain explicit unresolved outcomes; use
 authoritative reads and existing provider reconciliation, never blind replay.
@@ -93,213 +85,51 @@ and merge evidence is accepted. Preparation after a completed delivery is a
 separate follow-up candidate/scope and must obtain its own required evidence.
 Publication remains separately authorized and gated, including OTP when required.
-## Protected worker PR operations and status
+## Managed delivery (planned L5.5)
-An installed protected worker uses its original prepared assignment, attempt,
-mapping and hierarchical scope. A role charter or selector is not an authority
-capability: the public owners authenticate the actual worker descendant and
-original birth. Other installed participants must delegate to the provisioned
-worker/executor; they cannot select local delivery. Do not run the ordinary
-managed delivery commands below from this protected route. Draft create/update
-may precede independent review, through the same configured receiver. Ready and
-merge require executed checks, current accepted independent review and the exact
-operation authorization. See `wfi://git/pr/create` and `wfi://git/pr/update` for
-the bounded draft input; credentials do not grant those operations.
-1. Retain the exact accepted candidate head and candidate generation, original
-   assignment/attempt/mapping/scope, configured receiver ID, authorization and
-   request ID. Use the reviewed retained delivery parameters, explicit authorized
-   merge method and exact PR URL. Accepted independent review for this candidate
-   remains a canonical authority gate; local report files cannot replace it.
-2. Before the first claim, read
-   `ace-assign authority status --mapping MAPPING --assignment ID --attempt ATTEMPT`.
-   Its `generation` is the current authority generation and
-   `result_candidate_generation` is the candidate generation. They are distinct;
-   never increment or substitute one for the other. Verify the candidate generation
-   matches the accepted candidate. Unavailable or changed selection blocks the
-   request. Keep the exact returned generation for this invocation; a conflict
-   is not permission to refresh it and resend.
-3. Select `create`, `update`, `ready` or `merge`. Save one nonsecret input file:
-   create/update contain exactly `target`, `delivery`, `title`, `body`; ready
-   contains `target`, `delivery`; merge contains `target`, `delivery`, `method`.
-   A create target is the selected base repository URL; other operations use
-   the exact PR URL. Target contains that URL as `resource` and nullable
-   `artifact_digest`; delivery is the retained `forge_server`/`forge_default` and
-   complete `pr_provenance` mapping. Method is explicitly squash, merge or rebase.
-   The maintained owner reads one unchanged bounded regular file and computes its
-   canonical input digest. It does not accept a caller-supplied digest for request.
-   ```json
-   {"target":{"resource":"https://forge.example/team/repo/pulls/25","artifact_digest":null},"delivery":{"forge_server":"forge-lab","forge_default":false,"pr_provenance":{"mode":"canonical","head_repository_url":"https://forge.example/team/repo","head_ref":"work","base_repository_url":"https://forge.example/team/repo","base_ref":"main"}},"method":"squash"}
-   ```
-4. Invoke the existing configured receiver through
-   `ace-lab service request --project PROJECT --assignment ID --attempt ATTEMPT --mapping MAPPING --scope SCOPE --service SERVICE --candidate-head SHA --candidate-generation CANDIDATE-GENERATION --expected-generation AUTHORITY-GENERATION --operation OPERATION --authorization AUTHORIZATION --request-id REQUEST --input INPUT.json`.
-   No dry-run or standalone fallback exists here. Retain the returned original
-   `selection` from either `data` or `error`: it includes input_digest and target.
-   `service_claim_accepted` acknowledges a durable claim, not operation completion.
-   `service_claim_unconfirmed` requires inspection of this original request;
-   neither uncertainty nor a timeout authorizes automatic resubmission.
-5. Read exact canonical status without an effect:
-   `ace-lab service status --request REQUEST --project PROJECT --assignment ID --attempt ATTEMPT --mapping MAPPING --scope SCOPE --candidate-head SHA --candidate-generation CANDIDATE-GENERATION --input-digest INPUT-DIGEST --target ORIGINAL-TARGET`.
-   Use the original returned selection; omit `--artifact-digest` for null, or
-   supply its exact original SHA256 when present. Status does not use a refreshed
-   expected generation and never repairs or restarts an uncertain service.
-   Missing receiver, review, authorization or installed owner stays a routed
-   blocker. A caller-local journal or remote PR observation is not canonical proof.
-6. Only after canonical succeeded status, consume the exact completed result:
-   `ace-assign delivery --assignment ID --attempt ATTEMPT --mapping MAPPING --scope SCOPE --operation OPERATION --service-request REQUEST --candidate-head SHA --candidate-generation CANDIDATE-GENERATION --input-digest INPUT-DIGEST --target ORIGINAL-TARGET`.
-   Apply the same nullable artifact flag rule. Do not supply local `--tests`,
-   `--review`, title/body or parameters. The authority has already verified the
-   original review, completion receipt/import and exact input association, and
-   atomically published the delivery event. Worker consumption verifies that
-   event; it neither appends evidence nor invokes the provider again.
-7. Preserve the original request and result references on resume. Exact read-only
-   status is safe; an explicit identical request may only return its retained
-   canonical claim/result and must not refresh selectors. Never retry an unknown
-   effect to obtain a receipt. Publication, deployment and synchronization still
-   require their separate authorization, evidence and OTP where applicable.
-## Protected campaign result before readiness or merge
-When the original protected parent registers `review_campaign`, finish the existing
-R1/R2/R3 review policy through its linked, canonically settled collection/check/
-approval children. Follow the protected handoff in `wfi://review/pr`; ordinary
-`ace-review campaign` output and `ace-assign attempt finish` are not substitutes.
-Draft create/update above may run before independent review. Ready and merge wait
-for the current canonical parent campaign result, executed checks and independent
-review acceptance.
-1. Upload the documented R1 round input using the closed envelope
-   `{"version":1,"round":ROUND_OBJECT,"artifacts":[{"path":"report.md","sha256":"SHA256"}]}`.
-   Keep the original parent selectors, pinned head/base/scopes and registered
-   campaign/requirements/policy. The round attempt_id equals its stable mutation.
-   `ace-assign campaign-record-round --mapping MAPPING --assignment ID --attempt ATTEMPT --head SHA --candidate-generation N --mutation ROUND-ATTEMPT --input ROUND-ENVELOPE.json --artifact REPORT-BYTES`
-   supplies ordered immutable artifact bytes, not authority-readable worker paths.
-   Repeat the artifact flag in envelope order; settled child receipts establish
-   execution and approval, not editable reports alone.
-2. After policy acceptance, download its verified exact bytes:
-   `ace-assign campaign-export-result --mapping MAPPING --assignment ID --attempt ATTEMPT --head SHA --candidate-generation N --output RESULT.json`.
-   Retain exported sha256/result_identity/journal_commit. The authority owns the
-   campaign store and validates the accepted immutable candidate; the output file
-   is a transfer artifact, not permission to change or bypass policy.
-3. Keep the original parent's succeeded review receipt, independent actors and
-   executed checks. Add `campaign: {id: REGISTERED-CAMPAIGN, result: {path:
-   RESULT.json, sha256: EXPORTED-SHA256}}` and the identical reference in its
-   ordered artifacts. Upload exact exported bytes in that artifact slot with
-   `ace-assign submit-result --mapping MAPPING --assignment ID --attempt ATTEMPT --head SHA --candidate-generation N --expected-generation G --mutation RESULT-MUTATION --receipt PARENT-RECEIPT.json --artifact RESULT.json`.
-   Supply any other receipt artifacts in their declared order. Submission imports
-   evidence; the original reviewer/finish owner still owns acceptance and release.
-   G is persisted authority generation; N is candidate generation, never G.
-Restart retains original mutations, envelope/receipt bytes, ordered artifacts and
-selectors. Exact replay preserves the existing round/result; re-export only accepts
-an identical existing file. Changed candidate, policy or missing canonical child
-settlement rejects current acceptance without erasing history. Ready/merge service
-admission rechecks the canonical parent campaign result. Route a missing producer
-to its owner, keeping delivery unfinished; do not build a new receipt generator,
-refresh conflicting generations or use ordinary commands as a protected fallback.
-## Ordinary managed delivery steps
-These steps retain the existing nonprotected managed workflow. They are not a
-fallback for an installed protected participant or a blocked protected operation.
-1. Record the requested delivery steps and their owners before implementation.
-   Follow the existing task-work plan. Commit the implementation and run appropriate
-   package tests. If requested, perform local version/changelog preparation with
-   `ace-bundle wfi://release/local` before final evidence and merge; it does not
-   publish. Keep unfinished task criteria open; a bounded source checkpoint
-   cannot mark an entire installed task done.
-2. For remote delivery, prepare a concrete title and description from the changes
-   and executed validation. Load `ace-bundle wfi://git/pr/create` and use the actual
-   managed assignment and active delivery attempt. The executable operation is
-   `ace-assign delivery --assignment ID --attempt ATTEMPT --operation create --title TITLE --body-file DESCRIPTION`.
-   Provide `--parameters FILE` if required for the assignment's explicit delivery
-   mapping. Creation defaults to a draft. Record its returned server, repositories,
-   refs, PR number/URL and exact candidate_head.
-3. Execute the independent review workflow `ace-bundle wfi://review/pr` against that
-   exact PR and retained forge selection. Preserve its actual round completion rule,
-   findings and reviewer identities. Fix confirmed blocking findings and rerun
-   affected tests. Every new committed candidate, including task-only edits,
-   invalidates prior ready/merge evidence. Historical approval remains history.
-4. Obtain coordinator-accepted current-head test and independent review receipts
-   through the existing assignment boundary. File existence, fabricated approval,
-   exit zero or a worker claim cannot replace acceptance. Distinguish base_head,
-   candidate_head, evidence_git_ref and journal_commit; evidence commits do not
-   advance the deliverable branch. CI status is visible and advisory; failed
-   executed tests, stale evidence or unresolved review findings still block.
-5. Prepare the final PR body with the concrete behavior, executed checks,
-   independent verdict and remaining limitations. Load
-   `ace-bundle wfi://git/pr/update` and execute
-   `ace-assign delivery --assignment ID --attempt ATTEMPT --operation update --body-file DESCRIPTION`.
-   Mark ready only with accepted exact-head reference files:
-   `ace-assign delivery --assignment ID --attempt ATTEMPT --operation ready --tests TEST-REF --review REVIEW-REF`.
-   Each reference file contains only attempt_id and receipt_digest.
-6. Hand off merge only to the existing authorized integrator/service for the exact
-   PR, candidate and operation. Its executor uses the neutral provider merge with
-   both required values:
-   `ace-git pr merge IDENTIFIER --server NAME --expected-head CANDIDATE-SHA --method METHOD --format json`.
-   METHOD is the authorized squash, merge or rebase choice, never an implicit
-   default. The assignment worker consumes a completed verified service receipt:
-   `ace-assign delivery --assignment ID --attempt ATTEMPT --operation merge --tests TEST-REF --review REVIEW-REF --service-request REQUEST`.
-   This command does not dispatch or execute its own pending merge. If no actual
-   configured executor or valid receipt is available, retain the routed blocker.
-7. Local version/changelog preparation is optional requested work from step1.
-   It must be included before final exact-head evidence and merge. Preparation
-   requested after a completed merge starts a separate follow-up candidate/scope;
-   the old merge does not accept its amended content.
-   Publication, deployment and synchronization are distinct operations with their
-   own valid authorization, executed technical evidence and any required OTP.
-   Authorized merge does not authorize them. Do not add an unnecessary proposal
-   for an already authorized operation or fabricate an unavailable proposal API.
-8. Record the exact delivered scope, candidate, receipt references, review verdict
-   and remaining gates. A requested delivery-only scope can finish after its
-   authorized merge; publication is not mandatory. Keep the task in progress until
-   all of its actual acceptance criteria are satisfied.
+Managed delivery — assignment-scoped evidence and the reviewer/integrator
+role handoff — lands with the role workflow in L5.5. Until then, standalone
+delivery above is the active path. When the work belongs to an assignment, record
+actual artifacts, executed checks and the independent reviewer verdict for the
+exact head in the assignment step report (or the project task folder). Never
+substitute a written report or exit code for evidence that was not produced.
 ## Unavailable publication prerequisite
 Requested publication is a separate step, never a consequence of merge success.
-Use the existing configured service policy and publisher prerequisites; an absent
-publisher or unavailable required OTP is a routed blocker, not permission to run
-an alternate command/account. The ordinary tested publisher's precondition
-failure is ordinary source evidence only; it does not supply a protected
-publication receipt or positive scoped OTP capability.
+Use the existing configured publisher prerequisites; an absent publisher or
+unavailable required OTP is a routed blocker, not permission to run an alternate
+command or account.
 If the requested step cannot proceed, record its value-free cause through the
 existing assignment failure owner:
-`ace-assign fail --assignment ID@SCOPE --attempt ATTEMPT --mapping MAPPING --message "publication blocked: prerequisite unavailable"`.
-Use the actual original protected selectors; ordinary assignments omit protected
-selectors and use their existing target. Read `ace-assign status` for that same
-scope afterward. The step remains failed/unfinished, with no publication receipt
-or task completion. Preserve an uncertain service request separately: a failure
-report must not claim a definitive denial or effect absence from a lost reply.
-Protected recovery requires the reviewed new prepared version/attempt; never
-finish the failed step or retry publication to manufacture success.
+`ace-assign fail --assignment ID@SCOPE --message "publication blocked: prerequisite unavailable"`.
+Use the actual assignment selectors; standalone work omits them and uses its
+existing target. Read `ace-assign status` for that same scope afterward. The step
+remains failed/unfinished, with no publication evidence or task completion. Preserve
+an uncertain effect separately: a failure report must not claim a definitive denial
+or effect absence from a lost reply.
 ## Uncertainty and resume
-In managed mode, read assignment status and retained qjl delivery events before
-resuming. Repeat read/check operations safely. On interrupted create, update or readiness, use the
-same delivery command for exact-selector reconciliation. One matching draft may
-be adopted; zero remains unresolved and multiple matches conflict. A different
-requested effect cannot be reported complete merely because an earlier effect
-was recovered.
+When the work belongs to an assignment, read assignment status and its step
+reports before resuming. Repeat read/check operations safely. On an interrupted
+create, update or readiness, use the same forge command for exact-selector
+reconciliation. One matching draft may be adopted; zero remains unresolved and
+multiple matches conflict. A different requested effect cannot be reported complete
+merely because an earlier effect was recovered.
 Unknown merge/publication remains unknown pending its existing owner's
-reconciliation. Never blindly replay an effect, substitute a generic PR result
-for a service receipt or translate a blocker into direct gh/fj commands.
+reconciliation. Never blindly replay an effect or translate a blocker into
+unverified direct provider commands.
 ## Success criteria
 - The requested scope has real artifact, current test and independent review
   evidence for its exact candidate.
 - Remote identity and explicit provenance remain fixed with honest unresolved
-  outcomes preserved; managed mode records them in the existing attempt journal.
-- Readiness and authorized integration consume current evidence; managed merge
-  additionally consumes exact service receipts. Standalone output cannot satisfy
-  managed/protected acceptance. CI alone neither grants nor vetoes acceptance.
-- Optional publication remains separately authorized and unfinished installed
-  criteria remain visible.
+  outcomes preserved; assignment-backed work records them in its step report.
+- Readiness and authorized integration consume current evidence. CI alone neither
+  grants nor vetoes acceptance.
+- Optional publication remains separately authorized and unfinished criteria
+  remain visible.

data/lib/ace/handbook/version.rb CHANGED Viewed

@@ -2,6 +2,6 @@
 module Ace
   module Handbook
-    VERSION = "0.35.0"
+    VERSION = "0.36.0"
   end
 end

metadata CHANGED Viewed

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: ace-handbook
 version: !ruby/object:Gem::Version
-  version: 0.35.0
+  version: 0.36.0
 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