feat: pinned agents and probes only accept peers carrying the operator's proof; the panel ships the signed operator chain with the rosters [CI SKIP]

backend/shared/MoShiro.Protocol/Tasks/TaskSet.cs

@@ -40,6 +40,10 @@ public sealed class PeerSpec
     /// <summary>Probe 的身份公钥（SPKI，base64）。</summary>
     [JsonPropertyName("pubkey")]
     public string PublicKey { get; set; } = "";
+
+    /// <summary>操作员批准这个 Probe 的证明（passkey 签的委托加码的私钥签的绑定）。固定了创世的 Agent 没有它就不接纳。</summary>
+    [JsonPropertyName("proof")]
+    public MemberProofDto? Proof { get; set; }
 }
 
 /// <summary>期望状态文档（Fleet state type = <c>task_set</c>）：Backend 为每个 Agent 计算的有效任务集。</summary>
@@ -56,6 +60,10 @@ public sealed class TaskSet
     /// <summary>允许连接到这个 Agent 的 Probe 公钥。</summary>
     [JsonPropertyName("peers")]
     public List<PeerSpec> Peers { get; set; } = [];
+
+    /// <summary>操作员集合的链（passkey 签的，创世在前）：节点从固定的创世指纹验过才采用。</summary>
+    [JsonPropertyName("trust_chain")]
+    public List<SignedStatementDto>? TrustChain { get; set; }
 }
 
 public static class TaskSchedule