@leaflow/sdk 0.0.0-dev.464.g3357507 → 0.0.0-dev.468.g4f0b484

package/dist/fleet/v1/generated/validators/error.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/errorStatus.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/errorStatus.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/featureState.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/featureState.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/fieldViolation.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/fieldViolation.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/findEnrollmentByPairingCodeParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/findEnrollmentByPairingCodeParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/findEnrollmentResponse.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/findEnrollmentResponse.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/groupList.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/groupList.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/groupResource.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/groupResource.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/iceCandidate.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/iceCandidate.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/iceServer.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/iceServer.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listAccountsParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listAccountsParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listGroupMembersParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listGroupMembersParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listGroupsParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listGroupsParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listMachineEventsParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listMachineEventsParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listMachineRegistrationsParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listMachineRegistrationsParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listMachinesParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listMachinesParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listMcpToolsParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listMcpToolsParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listPrivilegeAutoApprovalsParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listPrivilegeAutoApprovalsParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listPrivilegeRequestsParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listPrivilegeRequestsParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listSessionsParams.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/listSessionsParams.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineEventList.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineEventList.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineEventResource.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineEventResource.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineEventType.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineEventType.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineFeature.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineFeature.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps
@@ -245,7 +244,7 @@ export const MachineFeature = zod.strictObject({
     state: FeatureState,
     reason: zod
         .string()
-        .describe("Why it cannot be used, such as `Xvfb is not installed`; empty while available"),
+        .describe("Why it cannot be used, such as `Xwayland is not installed`; empty while available"),
     details: zod
         .array(zod.string())
         .describe("What it can do on this machine, as the dotted names its package defines, such as `audio.pipewire`"),

package/dist/fleet/v1/generated/validators/machineList.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineList.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineRegistrationList.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineRegistrationList.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineRegistrationResource.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/machineRegistrationResource.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps