@boxes-dev/dvb-runtime 1.0.941 → 1.0.942

package/dist/bin/dvb.mjs

@@ -95684,8 +95684,8 @@ var init_otel = __esm({
       return trimmed && trimmed.length > 0 ? trimmed : void 0;
     };
     readBuildMetadata = () => {
-      const rawPackageVersion = "1.0.941";
-      const rawGitSha = "33574b8f76badae4eb1f3701a8160a6254abcade";
+      const rawPackageVersion = "1.0.942";
+      const rawGitSha = "cd3fc259b350855f0ced0daba2b8cbd98ea292d1";
       const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
       const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
       return { packageVersion, gitSha };
@@ -128091,9 +128091,9 @@ var init_sentry = __esm({
     uncaughtExceptionMonitorInstalled = false;
     currentDevboxSentryUser = null;
     readBuildMetadata2 = () => {
-      const rawPackageVersion = "1.0.941";
-      const rawGitSha = "33574b8f76badae4eb1f3701a8160a6254abcade";
-      const rawSentryRelease = "boxes-dev-dvb@1.0.941+33574b8f76badae4eb1f3701a8160a6254abcade";
+      const rawPackageVersion = "1.0.942";
+      const rawGitSha = "cd3fc259b350855f0ced0daba2b8cbd98ea292d1";
+      const rawSentryRelease = "boxes-dev-dvb@1.0.942+cd3fc259b350855f0ced0daba2b8cbd98ea292d1";
       const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
       const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
       const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -137396,7 +137396,7 @@ var init_packageVersion = __esm({
       return path17.join(process.cwd(), "dvb");
     };
     readEmbeddedPackageVersion = () => {
-      const raw = "1.0.941";
+      const raw = "1.0.942";
       return trimVersion(raw);
     };
     readNearestPackageMetadata = (basePath) => {

package/dist/bin/dvbd.mjs

@@ -92391,8 +92391,8 @@ var init_otel = __esm({
       return trimmed && trimmed.length > 0 ? trimmed : void 0;
     };
     readBuildMetadata = () => {
-      const rawPackageVersion = "1.0.941";
-      const rawGitSha = "33574b8f76badae4eb1f3701a8160a6254abcade";
+      const rawPackageVersion = "1.0.942";
+      const rawGitSha = "cd3fc259b350855f0ced0daba2b8cbd98ea292d1";
       const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
       const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
       return { packageVersion, gitSha };
@@ -124687,9 +124687,9 @@ var init_sentry = __esm({
     uncaughtExceptionMonitorInstalled = false;
     currentDevboxSentryUser = null;
     readBuildMetadata2 = () => {
-      const rawPackageVersion = "1.0.941";
-      const rawGitSha = "33574b8f76badae4eb1f3701a8160a6254abcade";
-      const rawSentryRelease = "boxes-dev-dvb@1.0.941+33574b8f76badae4eb1f3701a8160a6254abcade";
+      const rawPackageVersion = "1.0.942";
+      const rawGitSha = "cd3fc259b350855f0ced0daba2b8cbd98ea292d1";
+      const rawSentryRelease = "boxes-dev-dvb@1.0.942+cd3fc259b350855f0ced0daba2b8cbd98ea292d1";
       const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
       const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
       const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -130583,7 +130583,7 @@ var init_packageVersion = __esm({
       return path8.join(process.cwd(), "dvb");
     };
     readEmbeddedPackageVersion = () => {
-      const raw = "1.0.941";
+      const raw = "1.0.942";
       return trimVersion(raw);
     };
     readNearestPackageMetadata = (basePath) => {

package/dist/product-docs/references/team-template.md

@@ -58,10 +58,64 @@ preparing the entry does not publish a usable release: an admin must inspect
 the machine and save it first.
 
 Open a template's detail page to inspect its active release and release
-history. Admins also manage its name, description, project setup instructions,
-release cleanup script, and archive state there. The detail page is for
-inspection and administration; members start projects from the normal
-new-project flow instead.
+history. Admins also manage its Project defaults, name, description, release
+cleanup script, and archive state there. The detail page is for inspection and
+administration; members start projects from the normal new-project flow
+instead. Restore an archived Team Template before changing its Project defaults
+or running maintenance.
+
+## Project Defaults
+
+The **Project defaults** card controls what future projects receive. Its
+editors cover setup instructions, devbox startup and teardown behavior, Team
+Template maintenance and GitHub watches, Git and port behavior, Project URLs,
+and project-scoped MCP connections.
+
+Each editor saves independently and takes effect immediately for project
+creation. Saving a Project default does not publish a filesystem release and
+does not wait for the current editing session to close. Unsaved changes remain
+only in that focused editor; there is no configuration draft, publish action,
+history, or rollback. Existing projects never follow later changes.
+
+Project URLs receive fresh hostnames in each new project. MCP defaults contain
+only connection details, never credentials or a Codex/Claude choice. A new
+project normally receives an unconnected project-scoped MCP; its owner uses the
+ordinary MCP UI to sign in or add keys and choose agents. An exact matching
+account-wide MCP is reused. If an account-wide MCP has the same agent name but
+different settings, the account-wide MCP continues to apply and the owner must
+either rename the Team Template MCP to keep both or skip that inherited MCP.
+Account-wide MCPs apply across all projects and are edited from ordinary MCP
+settings.
+
+Machine size is fixed for the Team Template lineage and is not a Project
+default. Project creation offers no per-default overrides; members can change
+the resulting ordinary project afterward.
+
+## Team Template Maintenance
+
+Maintenance is real behavior for the Team Template, not only a preset for its
+children. An admin configures its script, schedule, and optional GitHub watches
+under **Project defaults**, or chooses **Run now**. boxes.dev restores the
+active release into a temporary team-owned maintenance machine with no user
+owner or customer billing, uses short-lived repository-scoped GitHub App
+access, runs the script, captures and verifies the result, and activates one
+new release. A failure preserves the prior active release and never modifies an
+admin's editing machine.
+
+A maintenance trigger waits behind an active editing session and starts after
+the session closes. Multiple triggers coalesce into the pending run. If the
+script succeeds but publication fails, the detail page offers **Retry
+publication** and **Discard result**; publication retry does not rerun the
+script. If GitHub App access is lost, use **Open GitHub settings** to restore
+the tracked repositories, then choose **Refresh repository access** on the
+maintenance failure before running it again. Repair refreshes only repositories
+the Team Template already tracks; it does not add or replace a repository.
+
+New projects receive an independent maintenance policy and watches containing
+only the saved behavior. Their schedules start at the next future occurrence,
+and enabled watches establish a fresh repository baseline without an initial
+run. Authorization, repository baselines, run history, errors, and other live
+state are never copied.
 
 ## Editing And Publishing
 
@@ -127,30 +181,39 @@ Start the ordinary new-project flow and choose **Start from a Team Template**.
 Select the exact template, then name the project and choose which coding agents
 should be available. The picker shows only templates with a published active
 release and does not preselect one. Before creation, the flow shows the exact
-release, machine size, and any included project setup instructions.
-
-boxes.dev pins that release when creation starts, creates a normal user-owned
-Template box, and makes the project available through the ordinary desktop
-workbench. It never silently substitutes another Team Template or a newer
-release. **Cancel and clean up** removes an unfinished creation. A recoverable
-failure stays in the flow with **Retry creation**, and returning to the same
-template reattaches to its unfinished creation.
+release, machine size, and a read-only summary of the current Project defaults.
+
+If the Team Template has any GitHub maintenance watch, including a disabled
+watch, project creation requires the member's current boxes.dev GitHub
+connection and GitHub App access to every watched repository. The flow presents
+the existing connect, update-authorization, install, or grant-access action and
+does not allocate the Template box until access is satisfied.
+
+When creation starts, boxes.dev pins the selected filesystem release and the
+current saved Project defaults as separate inputs. Later Team Template edits do
+not change that in-progress job. boxes.dev creates a normal user-owned Template
+box and makes the project available through the ordinary desktop workbench. It
+never silently substitutes another Team Template or a newer release. **Cancel
+and clean up** removes an unfinished creation. A recoverable failure stays in
+the flow with **Retry creation**, and returning to the same template reattaches
+to its unfinished creation.
 
 The new project is independent. Later Team Template releases, release cleanup,
 or leaving the team do not modify or remove the project's Template box,
 threads, snapshots, or devboxes. Creating it uses a normal project slot and its
 runtime uses the member's normal billing entitlement.
 
-An admin can save project setup instructions in the template's settings. Each
-release keeps the version of those instructions that existed when it was
-published. If instructions are present and the selected agent is authenticated,
+Setup instructions are current Project defaults, not part of the release save
+cadence. If instructions are present and the selected agent is authenticated,
 boxes.dev starts an optional setup thread after the project and its initial
 snapshot are usable. Project creation is considered complete once that setup
 thread starts; the user can open the project while it continues. The agent is
 asked to finish and validate as much setup as the destination user's
 credentials allow, explain anything the user must finish, and take a new
-Template box snapshot when done. If the setup thread cannot start, use **Retry
-setup** in the creation flow; that failure does not block **Open project**.
+Template box snapshot when done. If the setup thread or an optional inherited
+resource fails, the project remains usable. The creation card and the completed
+project's **Template setup needs attention** row show only unresolved items and
+offer a retry.
 
 ## Git Access
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boxes-dev/dvb-runtime",
-  "version": "1.0.941",
+  "version": "1.0.942",
   "type": "module",
   "license": "UNLICENSED",
   "imports": {
@@ -81,5 +81,5 @@
     "e2b": "^2.18.0",
     "ink-testing-library": "^4.0.0"
   },
-  "devboxReleasedAt": "2026-08-20T21:35:26Z"
+  "devboxReleasedAt": "2026-08-20T21:54:37Z"
 }