@sealant/api-contracts-next 0.39.0-next.701 → 0.39.0-next.703

package/dist/core-api/workspaces.d.ts

@@ -223,10 +223,10 @@ export declare const applyWorkspaceDotfilesArchiveSchema: Schema.Struct<{
  * order) and the same applier (sealantd's: chezmoi, stow or copy, then each tree's bootstrap).
  *
  * `user` must exist and must not be root or in root's group, and `home` must be its passwd home: an
- * existing directory of the user's, reached without a symbolic link. The clone, chezmoi, stow and the
- * bootstrap run as the user; sealantd's archive staging and `copy` manager still run as root inside
- * the home and follow links the person planted there, until sealantd's fix for it lands (see
- * docs/connected-accounts-design.md §6g). `onBehalfOfUserId` names whose dotfiles they are: it is
+ * existing directory of the user's, reached without a symbolic link. The clone, chezmoi, stow, the
+ * `copy` manager and the bootstrap run as the user, and every file in the home is written as the
+ * user: sealantd unpacks archives outside every home, and a link the person planted is followed only
+ * as them (see docs/connected-accounts-design.md §6g). `onBehalfOfUserId` names whose dotfiles they are: it is
  * recorded on the run, and a home whose logins another person holds is refused (`home-held`). Answered `202` with a run (`harnessId`
  * `dotfiles`) once the archives are staged: the run's first `processStarted` is the bootstrap,
  * started once every file is applied; its output and exit are the run's. The run completes with the

package/dist/core-api/workspaces.js

@@ -207,10 +207,10 @@ export const applyWorkspaceDotfilesArchiveSchema = Schema.Struct({
  * order) and the same applier (sealantd's: chezmoi, stow or copy, then each tree's bootstrap).
  *
  * `user` must exist and must not be root or in root's group, and `home` must be its passwd home: an
- * existing directory of the user's, reached without a symbolic link. The clone, chezmoi, stow and the
- * bootstrap run as the user; sealantd's archive staging and `copy` manager still run as root inside
- * the home and follow links the person planted there, until sealantd's fix for it lands (see
- * docs/connected-accounts-design.md §6g). `onBehalfOfUserId` names whose dotfiles they are: it is
+ * existing directory of the user's, reached without a symbolic link. The clone, chezmoi, stow, the
+ * `copy` manager and the bootstrap run as the user, and every file in the home is written as the
+ * user: sealantd unpacks archives outside every home, and a link the person planted is followed only
+ * as them (see docs/connected-accounts-design.md §6g). `onBehalfOfUserId` names whose dotfiles they are: it is
  * recorded on the run, and a home whose logins another person holds is refused (`home-held`). Answered `202` with a run (`harnessId`
  * `dotfiles`) once the archives are staged: the run's first `processStarted` is the bootstrap,
  * started once every file is applied; its output and exit are the run's. The run completes with the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sealant/api-contracts-next",
-  "version": "0.39.0-next.701",
+  "version": "0.39.0-next.703",
   "description": "Contract-first HTTP API definitions for Sealant services",
   "license": "Apache-2.0",
   "repository": {
@@ -32,7 +32,7 @@
   "peerDependencies": {
     "effect": ">=4.0.0-beta.85 <5"
   },
-  "gitHead": "1e2df7d1683a2a9d0d1d1d79580dfb3bb0620650",
+  "gitHead": "d2015951c37eb196787b66819b0e0590c413f626",
   "publishConfig": {
     "access": "public"
   }