runner.repository-profile.adopt-source

Adopt a repository's committed execution-profile document as its active universal-runtime profile, without an environment build.

Adopt a repository's own profile document as an active profile.

ONBOARDING WITHOUT A BUILD. The baked path needs an environment build to exist before a profile can be created: the build produces the image digest the profile is bound to, and until it is ready the repository cannot run at all. That is why onboarding a repository meant a build request, a builder claim, an image push and an evidence upload -- a chain whose failures (storage bindings, coupled manifest digests, a group pinned to one image) have nothing to do with the repository being onboarded.

A universal profile has no image to wait for. The repository's committed profile document already says everything the runner needs: which toolchain family, which commands, which files lock its dependencies. This adopts that document directly -- create the version, activate it, retire the previous one -- so onboarding a repository is merging a config file.

The document is validated by the same repository_profile_source_snapshot the build path uses, so a repository cannot describe itself more loosely just because no build is involved.

Overview

Property	Value
Workflow type	Atomic
Library	App-runners
Version	1.0

Input Schema

Field	Type	Required	Default	Description
organization_uuid	uuid	Yes	—	Authenticated organization; injected by the workflow API.
repository_uuid	uuid	Yes	—	—
repository_profile_source	dict	Yes	—	—

Output Schema

Field	Type	Required	Default	Description
organization_uuid	uuid	Yes	—	Authenticated organization; injected by the workflow API.
repository_uuid	uuid	No	—	—
profile_uuid	uuid	No	—	—
version	integer	No	—	—
digest	string	No	—	—
status	string	No	—	—
runtime_family	string	No	—	—
operating_system	string	No	—	—
architecture	string	No	—	—
sandbox_class	string	No	—	—
environment_contract	dict	No	—	—
toolchains	dict	No	—	—
commands	dict	No	—	—
required_capabilities	list	No	—	—
dependency_policy	dict	No	—	—
network_policy	dict	No	—	—
resource_limits	dict	No	—	—
workspace_policy	dict	No	—	—
test_policy	dict	No	—	—
repository_profile_source	dict	No	—	—
created_by_uuid	uuid	No	—	—
activated_at	string	No	—	—
retired_at	string	No	—	—
created_at	string	No	—	—
created	boolean	No	—	—
activated	boolean	No	—	—
retired	boolean	No	—	—
items	list	No	—	—
failure_reason	string	No	—	—
failed_at	string	No	—	—
failed_step	string	No	—	—
failed_layer	string	No	—	—
failed_at_state	string	No	—	—
error	string	No	—	—
error_type	string	No	—	—

States

State	Initial	Terminal	Success	Auto-advance	Description
pending	Yes	No	—	execute	—
completed	No	Yes	Yes	—	—
failed	No	Yes	No	—	—

State Diagram

Transitions

From	Action	To	Description
pending	execute	completed	—
* (any state)	fail	failed	—

API Usage

POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "runner.repository-profile.adopt-source",
  "initial_data": {
    "organization_uuid": "value",
    "repository_uuid": "value",
    "repository_profile_source": "value"
  }
}