Publish an Issue-branch Process through Delivery and remove the Claim

GLOSSARY.md

@@ -116,15 +116,15 @@ One invocation of the factory with no **Issue URL**: a **Security audit** of the
 _Avoid_: Fencing (former name), Secure run (it reads as a run that is secure), audit run, security pass
 
 **Pass**:
-An **Architect run**, a **Pickup run**, a **Security run**, or a **Custom process** started with no issue: a **Command** started with no **Issue URL**, which decides before any work whether it is skipped. A Custom process started with no issue is skipped while another Pass on the same repository is still running on the machine, its Spec run or Ticket run included, and it does not take an Architect run's Ready-issue or Architect-idea gates. A Custom process started with an issue is not a Pass.
+An **Architect run**, a **Pickup run**, a **Security run**, or a **Custom process** started with no issue and no Issue-branch worktree: a **Command** started with no **Issue URL**, which decides before any work whether it is skipped. A Custom process started with no issue and no Issue-branch worktree is skipped while another Pass on the same repository is still running on the machine, its Spec run or Ticket run included, and it does not take an Architect run's Ready-issue or Architect-idea gates. A file that declares an Issue-branch worktree is refused when no issue is given, before any session, and is not a Pass. A Custom process started with an issue is not a Pass.
 _Avoid_: tick, cycle
 
 **Process**:
 A named sequence of **Steps** that a **Command** carries out. The one a person writes is a **Custom process**.
 _Avoid_: workflow, pipeline, recipe
 
 **Custom process**:
-A **Process** a person defines on their own machine and starts by name. Started with no issue, it is a **Pass**. Started with an issue, it is not.
+A **Process** a person defines on their own machine and starts by name. Started with no issue and no Issue-branch worktree, it is a **Pass**. A file that declares an Issue-branch worktree is refused when no issue is given. Started with an issue, it is not a Pass.
 _Avoid_: workflow, pipeline
 
 **Step**:

README.md

@@ -55,7 +55,7 @@ Use `thirdshift help` for the command reference, or read [Ticket run behavior](d
 | A security audit | `thirdshift secure` | A [Security run](docs/guide.md#security-runs) records findings privately; fixing a reproduced finding is optional. |
 | Merged factory work | `thirdshift score` | A [Scoring run](docs/guide.md#scoring-runs) samples and grades it, and proposes Bug origins; `thirdshift scores --json` lists samples, five criterion Scores, calibration and proposals by week; `thirdshift scores <pull request> --mine` records yours before revealing the model's. |
 | One skill | `thirdshift skill <skill> [issue <issue>]` | A [standalone skill](docs/guide.md#standalone-skills) runs headlessly and prints its final message. |
-| A Custom process | `thirdshift process <name> [issue <issue>]` | An experimental [Custom process](docs/guide.md#custom-processes) runs skill, command or catalogue Steps from `~/.thirdshift/processes/<name>.toml`, in named throwaway worktrees when the file declares them. The catalogue Step `run-published-issue` starts a Ticket run or a Spec run on the issue the session Step before it published. An optional Step can fail without stopping the process. `issue <issue>` gives every session Step that issue. With no issue it is a Pass and skips while another Pass on the repository is running. Status, the Console and the Activity log list it as Process `<name>`. A failed one is in Needs you, and it sends a Run notification under the same email rules as a Ticket run. A skipped Process sends none. |
+| A Custom process | `thirdshift process <name> [issue <issue>]` | An experimental [Custom process](docs/guide.md#custom-processes) runs skill, command or catalogue Steps from `~/.thirdshift/processes/<name>.toml`, in named throwaway worktrees when the file declares them. The catalogue Step `run-published-issue` starts a Ticket run or a Spec run on the issue the session Step before it published. An optional Step can fail without stopping the process. `issue <issue>` gives every session Step that issue. One Issue-branch worktree plus a `delivery` Step publishes a ready-for-review pull request from that Issue branch and then removes the Claim. With no issue, and no Issue-branch worktree, it is a Pass and skips while another Pass on the repository is running. Status, the Console and the Activity log list it as Process `<name>`. A failed one is in Needs you, and it sends a Run notification under the same email rules as a Ticket run. A skipped Process sends none. |
 
 Each Architect, Pickup or Security run makes one pass. Use cron or another operating system scheduler to repeat it. See [scheduling](docs/guide.md#on-a-schedule), [Architect runs every few minutes](docs/guide.md#architect-runs-every-few-minutes) and [Security runs on a schedule](docs/guide.md#security-runs-on-a-schedule-with-fixing-allowed).
 

docs/code-navigation.md

@@ -70,7 +70,7 @@ Start with the issue's terms in `GLOSSARY.md`, then use this index to find their
 | Bug-origin proposal | `src/scoring/origins.rs` — bounded history session and proposed attribution; `src/github/scoring/origins.rs` — closed bugs and commit-to-PR associations; `src/logs/reading.rs` — retained Run lookup; `src/session/private.rs` — shared sandboxed analysis with native quota observation | `tests/bug_origins.rs` |
 | Bug-origin settlement, confirmed Run count | `src/scoring/origins/settlement.rs` — CLI decisions saved through retained handles before superseded Eval proposals are withdrawn; `src/scoring/store/confirmed.rs` — narrow confirmed-origin projection and normalized Bug-origin supersession over shared ordered storage, exposed by `scoring::read_confirmed_origins`; `src/logs/metrics/bug_origins.rs` — confirmed PR attribution and counts against the captured metrics Snapshot; `src/github/scoring/origins/review.rs` — historical PR head and issue evidence; `src/evals/bug_origin.rs` — private proposed Eval tasks; `src/logs/reading/selection.rs` — Run details | `src/scoring/store/confirmed/tests.rs`, `tests/metrics.rs`, `tests/bug_origins/settlement.rs`, `tests/bug_origins/regressions.py`, `tests/console/metrics.rs` |
 | Architecture review, Architect run | `src/architect.rs` | `tests/architect_run.rs` |
-| Custom process, run-published-issue | `src/processes.rs` — `execute`, `run_published` | `tests/process.rs` |
+| Custom process, Issue branch, delivery, run-published-issue | `src/processes.rs` — `execute`, `run_delivery`, `run_published` | `tests/process.rs` |
 | Security audit, Security review, Security run | `src/security.rs` and `src/security/`; which Ticket runs run a Security review, and what every child Ticket run is handed: `src/child_run/asks.rs` — `ChildAsks` | Inline tests; `tests/security_review.rs`, `tests/security_run.rs` |
 
 Eval task manifests, suite dependency selection and repository preparation live in