adopt-workflow 0.4.0__tar.gz

adopt_workflow-0.4.0/.gitignore

@@ -0,0 +1,42 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.hypothesis/
+build/
+dist/
+
+# Environments
+.venv/
+.env
+.env.local
+.env.*
+!.env.example
+*.key
+*.p12
+*.pfx
+
+# Local store and scratch
+.adopt/
+/tmp/
+
+# Never commit a private-repo artifact into the Apache-2.0 repository.
+# `adopt-plane` is a separate repository (handoff index CR-03) and is never
+# vendored here. If this pattern ever matches something, that is the
+# boundary violation the pattern exists to catch.
+adopt-plane/
+plane_*/
+
+# The exported locked runtime closure the release job derives the SBOM from.
+# `release.yml` generates it in an ephemeral checkout, so CI never sees this
+# file; a local release rehearsal does, in the repository root, and a generated
+# artefact one `git add -A` away from the first public commit is worth one line.
+runtime-constraints.txt
+
+# CI metrics, written per run and uploaded as an artefact (PRD §6)
+ci-metrics.jsonl
+.coverage
+cov.json

adopt_workflow-0.4.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

adopt_workflow-0.4.0/NOTICE

@@ -0,0 +1,39 @@
+Adopt — Adoption-Phase Platform, shared substrate (`adopt-core`)
+Copyright 2026 The Adopt Authors
+
+This product includes software developed by The Adopt Authors.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+--------------------------------------------------------------------------------
+Attribution note
+--------------------------------------------------------------------------------
+
+The copyright holder is recorded here as "The Adopt Authors" pending the legal
+entity name. The owner must settle that attribution before the 0.3.0 tag,
+because published package metadata cannot be changed retroactively for a
+release that has already left the machine. The product name itself is settled:
+handoff-index CR-50 keeps `Adopt` distinct from the `onboard` URI namespace.
+
+--------------------------------------------------------------------------------
+Third-party dependencies
+--------------------------------------------------------------------------------
+
+Every third-party dependency linked into this distribution is permissively
+licensed. The complete list, with licence hash, security status, usage mode,
+owner and re-verification date, is maintained in `licence-verifications.md` and
+enforced by `scripts/licence_gate.py`.
+
+Copyleft-licensed tools are invoked as subprocesses only and are never linked
+into this distribution. They are declared in `subprocess-deps.toml` together
+with their invocation sites.

adopt_workflow-0.4.0/PKG-INFO

@@ -0,0 +1,13 @@
+Metadata-Version: 2.5
+Name: adopt-workflow
+Version: 0.4.0
+Summary: The Workflow facade, the in-process test backend, the purity checker.
+Project-URL: Homepage, https://github.com/onboardux/onboard-core
+Project-URL: Source, https://github.com/onboardux/onboard-core
+Project-URL: Issues, https://github.com/onboardux/onboard-core/issues
+Author: The Adopt Authors
+License-Expression: Apache-2.0
+Requires-Python: >=3.12
+Requires-Dist: adopt-const
+Requires-Dist: adopt-obs
+Requires-Dist: pydantic<3,>=2.7

adopt_workflow-0.4.0/pyproject.toml

@@ -0,0 +1,40 @@
+[project]
+name = "adopt-workflow"
+version = "0.4.0"
+description = "The Workflow facade, the in-process test backend, the purity checker."
+requires-python = ">=3.12"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "The Adopt Authors" }]
+# `no-dbos` import contract: no DBOS symbol appears in this package. The only
+# DBOS importer in the programme is `plane_workflow.dbos_backend`, in the closed
+# repository.
+#
+# `no-raw-sqlite` also names this package a source module and follows indirect
+# chains, which is why the in-process backend persists to a file journal rather
+# than to a database -- see `inproc/journal.py`.
+dependencies = [
+    "adopt-const",
+    "adopt-obs",
+    "pydantic>=2.7,<3",
+]
+
+[project.urls]
+Homepage = "https://github.com/onboardux/onboard-core"
+Source = "https://github.com/onboardux/onboard-core"
+Issues = "https://github.com/onboardux/onboard-core/issues"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/adopt_workflow"]
+
+# Apache-2.0 4(a) and 4(d): the licence and the NOTICE travel with every
+# redistribution. `uv build` builds the wheel from the sdist, so placing the
+# repository root's single authored copy here puts it in both artefacts and
+# leaves nothing to drift.
+[tool.hatch.build.targets.sdist.force-include]
+"../../LICENSE" = "LICENSE"
+"../../NOTICE" = "NOTICE"

adopt_workflow-0.4.0/src/adopt_workflow/__init__.py

@@ -0,0 +1,63 @@
+"""The Workflow facade, the in-process test backend, the purity checker.
+
+Contracts §10.2 · implementation spec §4.14 · PRD F14.
+
+Invariants this package carries: **no DBOS symbol appears here** -- the only
+importer in the programme is `plane_workflow.dbos_backend`, in the closed
+repository -- workflow bodies are pure, checked at decoration time by
+`assert_pure` and across the tree by the `workflow-body-purity` contract, and
+**no Build 0 OSS-side command uses durable workflows**, so the OSS CLI never
+requires Postgres.
+"""
+
+from adopt_workflow.api import (
+    TERMINAL_STATUSES,
+    Backoff,
+    RetryPolicy,
+    StepContext,
+    WorkflowClient,
+    WorkflowContext,
+    WorkflowHandle,
+    WorkflowStatus,
+    backoff_delays_ms,
+    validate_idempotency_key,
+)
+from adopt_workflow.decorators import (
+    REGISTRY,
+    ScheduledDefinition,
+    StepDefinition,
+    WorkflowDefinition,
+    clear_registry,
+    resolve,
+    scheduled,
+    step,
+    workflow,
+)
+from adopt_workflow.inproc import InProcessWorkflowClient, Journal
+from adopt_workflow.purity import assert_pure, find_impure_workflow_bodies
+
+__all__ = [
+    "REGISTRY",
+    "TERMINAL_STATUSES",
+    "Backoff",
+    "InProcessWorkflowClient",
+    "Journal",
+    "RetryPolicy",
+    "ScheduledDefinition",
+    "StepContext",
+    "StepDefinition",
+    "WorkflowClient",
+    "WorkflowContext",
+    "WorkflowDefinition",
+    "WorkflowHandle",
+    "WorkflowStatus",
+    "assert_pure",
+    "backoff_delays_ms",
+    "clear_registry",
+    "find_impure_workflow_bodies",
+    "resolve",
+    "scheduled",
+    "step",
+    "validate_idempotency_key",
+    "workflow",
+]

adopt_workflow-0.4.0/src/adopt_workflow/api.py

@@ -0,0 +1,262 @@
+"""The `Workflow` facade: contracts §10.2, and nothing a backend can widen.
+
+**Why a facade at all.** Implementation spec §1.1 locks DBOS for durable
+execution and source spec §13 requires that the documented Temporal migration
+stay a migration. That is only true if no DBOS symbol appears outside one module,
+which means every caller in the programme talks to the shapes declared here.
+`no-dbos` enforces the second half; this file is the first.
+
+**What the seam owns and what a backend owns.** The seam owns the vocabulary --
+status values, the retry policy and its caps, the handle, the two contexts. A
+backend owns *when* things run and *where* they are persisted, and nothing else.
+A backend that could add a status value or lift a retry cap would make the
+facade advisory, and the two backends would then differ in ways only production
+discovers.
+
+**`run_id` needs no new prefix.** Contracts §1.1 registers `run_` for "one CLI
+invocation or one unit of work" and §10.2 names every keyed parameter `run_id`.
+A workflow run is one unit of work, so it is a `run_` id -- adding a `wf_` prefix
+would have been a §1.1 change made to avoid reusing the entry that already
+describes this.
+"""
+
+from collections.abc import Callable, Mapping
+from typing import Any, Final, Literal, Protocol, runtime_checkable
+
+from pydantic import BaseModel, ConfigDict, Field, field_validator, model_validator
+
+from adopt_const import (
+    IDEMPOTENCY_KEY_MAX_CHARS,
+    WORKFLOW_STEP_BACKOFF_BASE_MS,
+    WORKFLOW_STEP_BACKOFF_MAX_MS,
+    WORKFLOW_STEP_MAX_ATTEMPTS,
+)
+from adopt_obs import AdoptError, ErrorCode
+
+__all__ = [
+    "TERMINAL_STATUSES",
+    "Backoff",
+    "RetryPolicy",
+    "StepContext",
+    "WorkflowClient",
+    "WorkflowContext",
+    "WorkflowHandle",
+    "WorkflowStatus",
+    "backoff_delays_ms",
+    "validate_idempotency_key",
+]
+
+#: The run lifecycle. `completed`, `failed` and `cancelled` are terminal; the
+#: kill-and-resume drill asserts `completed` after a resume, so a resumed run
+#: must reach the same value a run that never died would.
+WorkflowStatus = Literal["pending", "running", "completed", "failed", "cancelled"]
+
+#: A run in one of these states will not change again. Both backends are asked
+#: for this set rather than each deciding which of their states are final.
+TERMINAL_STATUSES: Final[frozenset[str]] = frozenset({"completed", "failed", "cancelled"})
+
+#: Contracts §10.2 shows `backoff="exponential"`. `none` exists for a step whose
+#: failure is not worth waiting on; there is deliberately no `linear`, because a
+#: third curve is a third thing to reason about at 3 a.m. for no stated need.
+Backoff = Literal["exponential", "none"]
+
+
+class RetryPolicy(BaseModel):
+    """How many times a step is retried, and how long between attempts.
+
+    `max_attempts` is **capped**, not defaulted, by `WORKFLOW_STEP_MAX_ATTEMPTS`.
+    A caller asking for more is refused rather than silently clamped: a step
+    declared with 50 attempts was written against an expectation the platform
+    does not meet, and clamping hides that until someone reads a log.
+    """
+
+    model_config = ConfigDict(extra="forbid", frozen=True)
+
+    max_attempts: int = Field(default=WORKFLOW_STEP_MAX_ATTEMPTS, ge=1)
+    backoff: Backoff = "exponential"
+    base_ms: int = Field(default=WORKFLOW_STEP_BACKOFF_BASE_MS, ge=0)
+    max_ms: int = Field(default=WORKFLOW_STEP_BACKOFF_MAX_MS, ge=0)
+
+    @field_validator("max_attempts")
+    @classmethod
+    def _within_cap(cls, value: int) -> int:
+        if value > WORKFLOW_STEP_MAX_ATTEMPTS:
+            raise ValueError(
+                f"max_attempts={value} exceeds WORKFLOW_STEP_MAX_ATTEMPTS="
+                f"{WORKFLOW_STEP_MAX_ATTEMPTS}. The cap is the platform's, not the "
+                f"step's; raise it in implementation spec §2.2 and adopt_const together."
+            )
+        return value
+
+    # A cross-field rule, so it runs after the model is built rather than as a
+    # `field_validator` taking `ValidationInfo` -- that parameter is generic in
+    # `Any`, and `mypy.ini` sets `disallow_any_decorated`.
+    @model_validator(mode="after")
+    def _max_not_below_base(self) -> "RetryPolicy":
+        if self.max_ms < self.base_ms:
+            raise ValueError(
+                f"max_ms={self.max_ms} is below base_ms={self.base_ms}, so the first "
+                f"delay would already exceed the ceiling and every later one would be "
+                f"clamped to it."
+            )
+        return self
+
+
+def backoff_delays_ms(policy: RetryPolicy) -> tuple[int, ...]:
+    """The delay before each retry, in order. Length is `max_attempts - 1`.
+
+    A pure function of the policy, so the schedule can be asserted without
+    running a workflow and without either backend reproducing it independently.
+    There is no jitter: this is a per-run schedule for a single-writer local
+    backend and a DBOS queue, not a thundering herd of clients against one
+    service. Adding jitter would also make the sequence untestable by equality,
+    which is the property that keeps the two backends honest about the cap.
+    """
+    if policy.backoff == "none":
+        return tuple(0 for _ in range(policy.max_attempts - 1))
+    delays: list[int] = []
+    delay = policy.base_ms
+    for _ in range(policy.max_attempts - 1):
+        delays.append(min(delay, policy.max_ms))
+        delay *= 2
+    return tuple(delays)
+
+
+def validate_idempotency_key(key: str) -> str:
+    """Contracts §1.5: opaque, non-empty, at most `IDEMPOTENCY_KEY_MAX_CHARS`.
+
+    Refused at the seam rather than at a backend, so both backends refuse the
+    same keys. A key silently truncated by a column width is two different runs
+    that look like a replay of each other.
+    """
+    if not key:
+        raise AdoptError(
+            ErrorCode.WORKFLOW_DUPLICATE_START,
+            message="an idempotency key is required to start a workflow",
+            hint=(
+                "Contracts §1.5: every retriable operation takes a key, because "
+                "every message is assumed to be delivered twice."
+            ),
+        )
+    if len(key) > IDEMPOTENCY_KEY_MAX_CHARS:
+        raise AdoptError(
+            ErrorCode.WORKFLOW_DUPLICATE_START,
+            message=f"idempotency key is {len(key)} characters, over the "
+            f"{IDEMPOTENCY_KEY_MAX_CHARS}-character limit",
+            hint="Hash the caller's key rather than truncating it; a truncated key collides.",
+        )
+    return key
+
+
+class WorkflowHandle(BaseModel):
+    """What `start` returns, and what a replayed `start` returns unchanged."""
+
+    model_config = ConfigDict(extra="forbid", frozen=True)
+
+    run_id: str
+    name: str
+    version: int
+    idempotency_key: str
+    status: WorkflowStatus
+
+
+@runtime_checkable
+class StepContext(Protocol):
+    """Contracts §10.2, verbatim: `run_id`, `attempt`, and `dedupe`."""
+
+    run_id: str
+    attempt: int
+
+    def dedupe(self, key: str) -> bool:
+        """`True` when this is the first commit for `key`; `False` on a replay.
+
+        The exactly-once boundary. Steps run at least once, so the effect and
+        its dedupe record must commit **together** -- a backend that writes the
+        record after the effect has a window in which a crash duplicates the
+        effect, and that window is exactly what the durability drill opens.
+        """
+        ...
+
+
+@runtime_checkable
+class WorkflowContext(Protocol):
+    """What a workflow body is handed.
+
+    Deliberately tiny. Everything non-deterministic reaches the body through
+    `step`, because a body is **replayed**: on resume the engine re-executes it
+    and expects the same decisions. `workflow-body-purity` enforces the
+    negative half of that at lint and import time; this Protocol is the positive
+    half -- the only door out of a body.
+    """
+
+    run_id: str
+
+    def step(self, fn: Callable[..., Any], /, *args: Any, **kwargs: Any) -> Any:
+        """Execute `fn` as a durable step, or replay its recorded result."""
+        ...
+
+
+@runtime_checkable
+class WorkflowClient(Protocol):
+    """Contracts §10.2, plus `list` *(CR-42)*.
+
+    `list` is named by PRD F14.1 and omitted from §10.2's Protocol, and
+    implementation spec §7.4's rollback surface needs it: flipping
+    `ADOPT_FEATURE_DBOS_BACKEND` off requires in-flight runs to drain first, and
+    "drain" is unobservable without a way to enumerate them.
+    """
+
+    def start(
+        self,
+        fn: Callable[..., Any],
+        args: Mapping[str, Any],
+        *,
+        idempotency_key: str,
+    ) -> WorkflowHandle: ...
+
+    def signal(self, run_id: str, name: str, payload: Mapping[str, Any]) -> None: ...
+
+    def status(self, run_id: str) -> WorkflowStatus: ...
+
+    def result(self, run_id: str, *, timeout_s: int) -> Any: ...
+
+    def cancel(self, run_id: str) -> None: ...
+
+    def close(self) -> None:
+        """Stop executing work and release what the client holds *(CR-43)*.
+
+        **A backend that can start workers must be able to stop them**, and
+        §10.2 declared no way to. That is not a test convenience: implementation
+        spec §7.4's rollback flips `ADOPT_FEATURE_DBOS_BACKEND` off after
+        in-flight runs drain, and "drained" followed by a process that is still
+        dequeuing is not drained.
+
+        The durability drill is where the omission became visible. Its parent
+        process holds a client across three tests while each test spawns a child
+        that is meant to be the *only* executor -- and a queue is shared by every
+        worker pointed at it, so the parent silently dequeued the child's run and
+        executed it in the wrong process. That is DBOS behaving correctly and the
+        seam giving the caller no way to say "I am no longer a worker".
+
+        Closing is **idempotent** and does not cancel or roll back running
+        work: durable runs outlive the client by design, and the next process to
+        recover them picks them up. A backend holding nothing may do nothing.
+        """
+        ...
+
+    def recover(self) -> list[WorkflowHandle]:
+        """Re-drive every non-terminal run; return what was resumed.
+
+        Also CR-42. Implementation spec §4.14 says a crash between two step
+        records "replays the step", which presumes an entry point where the
+        replay begins -- DBOS reaches it at launch, and the in-process backend
+        has to be told. Declaring it here is what lets **one** durability suite
+        drive both: a drill that called `recover()` on one backend and relied on
+        a constructor side effect on the other would be two drills wearing one
+        name.
+        """
+        ...
+
+    # `list` is declared last: it shadows the builtin for every annotation after
+    # it in the class body, and the contract fixes the method name.
+    def list(self, *, status: WorkflowStatus | None = None) -> list[WorkflowHandle]: ...