1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
//! Built-in agent workers that start themselves.
//!
//! A first-time installer who deploys a document whose `worker` block carries a
//! `harness` section, and then runs it, must have the worker stood up BY THE
//! SERVER — zero worker commands typed. That is what this module is: the server
//! reading the launch the document already declares, writing the managed-worker
//! record that replays it, and converging its own supervisor onto it.
//!
//! # 🔴 WHAT THE DEPLOY GRANT NOW MEANS
//!
//! Before this, a deploy-granted caller could only make the server run the
//! server's OWN executable: `PUT /worker-deployments` names a `builtin`
//! artifact and nothing else. That is no longer the whole reachable set.
//!
//! A deployed document's `harness` section is the complete launch of an agent
//! subprocess, and an `acp` section names an absolute `command` with its own
//! `args`, `cwd` and `env_pass`. So a single `POST /deploy/packages` from a
//! deploy-granted subject is now sufficient to have this server execute an
//! operator-chosen binary, unattended, with a restart policy behind it.
//!
//! That is the ruling, not an oversight — "the worker starts itself" cannot
//! mean anything else, and the launch has always been the document's rather
//! than a flag's. But it MUST be stated: the deploy grant is now equivalent to
//! local process execution as the server's user, and `[deploy].enabled` is the
//! switch that decides whether anybody holds it. The first-run config already
//! says deploying is running code on this server; this widens what "code"
//! covers, and an operator on a shared box should read it that way.
//!
//! # What a minted worker serves, and what it does NOT
//!
//! One record, one namespace: the server's own `default_namespace`. Namespace
//! and task queue are independent axes, and the deploy catalog is
//! namespace-blind, so a workflow of this type STARTED in another namespace is
//! not dispatched to this worker. Every minted outcome's detail says so, rather
//! than leaving the operator to discover it as a run that never progresses.
pub use ;
pub use ;
pub use ;
pub use ;
pub use provision;
pub use ;
pub use ;
pub use refresh_dial_addresses;