@sous-io/sous 0.2.25 → 0.2.27

package/docs/markdown/_sidebar.md

@@ -25,3 +25,5 @@
   - [0004: A global sous defers to the project's install](adrs/0004-project-install-handoff.md)
   - [0005: Follow-ups from the first project on the hand-off](adrs/0005-first-project-follow-ups.md)
   - [0006: `sous repo init` follows `sous-recipes`](adrs/0006-repo-init-model-home.md)
+  - [0007: Frozen index entries and tolerant readers](adrs/0007-frozen-index-dependencies.md)
+  - [0009: One whole build, everywhere](adrs/0009-whole-build-everywhere.md)

package/docs/markdown/commands.md

@@ -93,10 +93,21 @@ and the command you want almost always. Takes `--dry-run`.
 
 - `--no-prune`, `--no-compile`: skip one half of the run.
 - `--rebuild`: ignore cached hashes and reprocess every output.
-- `--strict`: fail on any compilation error rather than reporting it and continuing.
+- `--strict`: treat compile warnings as errors (a `.tpl.` file copied without being rendered, a git branch the
+  runtime context could not read).
 - `-w, --watch`: rebuild on every change to a source file, a config layer or a linked checkout.
 
-Before it compiles, a build lists each recipe this project uses that has a newer version within the range
+Before it compiles, a build prepares the project's recipes: it seeds the core recipe, pins any subscription the
+lockfile does not pin yet, restores whatever the store on this machine is missing, and checks upstream for the
+repositories that ask for newer versions. Every command that builds (`init`, `build`, `launch`, `prune`,
+`repo remove`, `repo unlink`, `subscription add`, `subscription remove`, `subscription update`) runs this same
+build, so each one prints the same things.
+
+A compile error (a missing or circular include, a template that fails to render, a file sous cannot read) fails
+the build. Every target is still compiled and every error is listed, then the build exits `1`. An output whose
+target had an error is not written, so the copy from the last good build stays in place.
+
+A build also lists each recipe this project uses that has a newer version within the range
 declared for it, beside the version pinned. It moves no pin; only always-pull moves one. The build reads upstream
 for this at most once per freshness window (`store.freshnessSeconds`, five minutes by default), gives a
 repository three seconds to answer, and otherwise answers from the cached index without a word about the
@@ -106,18 +117,22 @@ Example: `sous build --rebuild`
 
 ### `sous compile`
 Compiles markdown templates into output files, and prunes nothing. Takes `--rebuild`, `--strict`, `--dry-run`
-and `-w, --watch`, each meaning what it means on `build`. Example: `sous compile --strict`
+and `-w, --watch`, each meaning what it means on `build`, and exits `1` after a compile error the way `build`
+does. It does not prepare the recipes first. Example: `sous compile --strict`
 
 ### `sous prune`
-Removes output files no longer in the current config. Takes `--dry-run` only. Example: `sous prune --dry-run`
+Removes output files no longer in the current config. It prepares the recipes first, as `build` does, because
+what counts as current depends on the recipes the lockfile pins. Takes `--dry-run` only. Example:
+`sous prune --dry-run`
 
 ### `sous clear`
 Deletes every file and directory sous has written for the project, and asks first; `-f, --force` answers that
 confirmation ahead of time. Example: `sous clear --force`
 
 ### `sous launch TOOL...`
-Builds this project's outputs, then starts a coding agent configured under `tools` in its config. `--no-build`
-launches without building; `--continuous` restarts the agent whenever it exits.
+Builds this project's outputs, then starts a coding agent configured under `tools` in its config. A build that
+fails starts nothing and exits `1`. `--no-build` launches without building; `--continuous` restarts the agent
+whenever it exits.
 
 Any argument `launch` does not recognize is forwarded to the tool; a flag that collides with one of sous's own
 goes after a bare `--`: `sous launch claude --resume`, `sous launch claude -- -c`.
@@ -447,8 +462,9 @@ Example: `sous vars ask --namespace workflow --var apiUrl`
 
 A command that succeeds exits `0`. A command line sous could not parse (a missing argument, an unknown flag, a
 value outside a flag's options) exits `2`. Every other failure exits `1`. A broken config halts sous rather than
-producing output built on a guess. Compilation is the one place sous reports a failure and carries on;
-`--strict` on `build` and `compile` turns those reports into a failed run.
+producing output built on a guess. A build with a compile error carries on long enough to compile every target
+and list every error, then exits `1`, leaving the last good copy of each output that had an error;
+`--strict` on `build` and `compile` makes compile warnings fail the run too.
 
 A failure prints one error block, in plain language, and nothing else; a usage mistake gets the command's own
 help under it, on standard error. An error sous raises names the cause and the cure:

package/docs/markdown/repositories-authoring.md

@@ -143,7 +143,7 @@ variables:
 ## Declare dependencies and co-subscriptions
 
 `depends` fetches and pins a recipe whose files stay OUT of a subscriber's output but are addressable from your
-own templates. `subscribes` is a co-subscription: its questions run and its files DO enter the output, which is
+own templates, and from the templates of any project whose lockfile pins it. `subscribes` is a co-subscription: its questions run and its files DO enter the output, which is
 how a curated bundle is built. Both hold plain strings naming their target by where it lives.
 
 ```yaml
@@ -240,9 +240,10 @@ this release's scope** is fine: the release depends on the last published versio
 
 Each version's resolved dependencies are written into the index, so a consumer installing that version gets what
 it was published with rather than ranges re-resolved months later. A published version never changes: its content
-hash is carried forward exactly as published, and a disagreement is an error telling you to bump rather than
-republish. A version counts as published once its tag exists, and the tags are the backstop, so a tagged version
-missing from the index is rebuilt from it whenever the index is regenerated, which only happens on a run that
+hash and its dependencies are carried forward exactly as published, and a disagreement is an error telling you
+to bump rather than republish ([what is checked](repositories-file-formats.md#sousindexjson)). A version counts
+as published once its tag exists, and the tags are the backstop, so a tagged version missing from the index is
+rebuilt from it, dependencies included, whenever the index is regenerated, which only happens on a run that
 publishes something. A bump edits the manifest in place, so comments, field order and layout survive; a folded
 block of YAML prose may be re-wrapped and the space before a trailing comment collapsed to one.
 

package/docs/markdown/repositories-file-formats.md

@@ -177,6 +177,22 @@ sibling, resolved exactly) or `range` plus `repo` (the identity of the repositor
 index resolves the range); at least one is required. Installing a version installs these rather than
 re-resolving the manifest's ranges.
 
+**A published version's entry is frozen.** Its dependencies are resolved once, when the version is first
+recorded, and every later release carries the entry forward exactly as published, like its hash; releasing
+other recipes, adding a recipe to a namespace it subscribes to, or raising a sibling it names changes nothing
+in it. A release still checks the recorded list against the version's manifest: a recipe the manifest names
+that the list lacks, a recipe in the list the manifest does not declare, a sibling outside its declared
+range, or another repository's entry with a different repository or range is an error naming the recipe, the
+version and each difference; restore the entry if the index was edited, or bump the version to publish
+different dependencies. A version rebuilt from its tag, when the index lost it, has its dependencies resolved
+against the repository as it stood at that tag, then frozen the same way. An entry written before sous
+recorded dependencies carries none, stays that way, and installs by resolving its manifest's ranges.
+
+**Fields this sous does not know are kept, not refused.** A later sous may add fields to the index, at any
+level. This one reads such an index, validates every field it defines as strictly as before, and ignores the
+rest; a release it runs carries a published version's entry forward with those fields intact. A sous older
+than the one that began tolerating unknown fields refuses the whole index once a repository publishes one.
+
 **The `seeded` field.** Sous ships the `core` recipe in its own npm package, so a project can build before
 reaching the network. That copy is folded into the official repository's index in memory and resolved like
 any other, marked `seeded: true`; if the repository already publishes it, the published copy wins. Sous

package/docs/markdown/repositories.md

@@ -331,9 +331,26 @@ published identity and then the path inside it, on a line of its own:
 ```
 
 The `~` is required. A bare `@path` is always a relative path or a declared alias, so an include
-line can never quietly stop meaning a file on disk. Inside a recipe, `~<namespace>` resolves only
-against that recipe's own `depends` and `subscribes` at the versions the lockfile pins, and the
-path after the recipe name may not be absolute or hold a `.` or `..` segment.
+line can never quietly stop meaning a file on disk. In your own templates, `~<namespace>`
+resolves against every recipe the lockfile pins, whatever brought it in: a recipe you subscribe
+to, a member of a set you subscribe to, or a library another recipe depends on. Inside a recipe,
+it resolves only against that recipe's own `depends` and `subscribes` at the versions the
+lockfile pins. The path after the recipe name may not be absolute or hold a `.` or `..` segment.
+
+An include naming a recipe the lockfile does not pin fails the build. When sous can tell what
+used to bring the recipe in (a switched-off subscription, or an earlier version of a set that
+listed it), the error names it:
+
+```text
+  Error: Include not found: @~workflow/member/memories/member.md
+  in file: .sous/prompts/AGENTS.md
+  namespace: workflow
+  recipe: workflow/member
+  The namespace "workflow" holds no recipe named "workflow/member".
+  Version 1.0.0 of "omakase/house" brought "workflow/member" in, but the version this project
+    pins, 1.1.0, does not, so the lockfile no longer pins it.
+  Subscribe to "workflow/member" directly to keep including it, or remove the include.
+```
 
 ## Where to go next
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sous-io/sous",
-  "version": "0.2.25",
+  "version": "0.2.27",
   "description": "Compiles AI coding agent configuration (CLAUDE.md, skills, memories) from LiquidJS templates",
   "type": "module",
   "license": "Apache-2.0",

package/recipes/core/sous-skills/skills/about-liquid-templates/SKILL.tpl.md

@@ -148,8 +148,9 @@ written `@~<namespace>/<recipe>/<path inside that recipe>`:
 
 Scoping is deliberate. A file inside a recipe may address that recipe itself plus the
 recipes it declares under `depends` or `subscribes`; a file in the project's own templates
-may address the project's subscriptions. Anything else is an error naming what was missing,
-so a reference can never quietly pick up a recipe nobody asked for.
+may address every recipe the project's lockfile pins, whatever brought it in. Anything else
+is an error naming what was missing, so a reference can never quietly pick up a recipe
+nobody asked for.
 
 Built-in **aliases** are reserved, always begin with `~`, and are consulted before recipe
 namespaces. There is exactly one:

package/recipes/core/sous-skills/sous.recipe.yaml

@@ -11,7 +11,7 @@ formatVersion: 1
 
 namespace: core
 name: sous-skills
-version: 0.2.25
+version: 0.2.27
 
 description: >-
   The skills that teach an agent what sous is and how it works: which files sous

package/src/commands/build.ts

@@ -1,23 +1,14 @@
 import { Flags } from "@oclif/core";
 import { BaseCommand } from "../base-command.js";
-import { BuildService } from "../lib/build-service.js";
+import { runProjectBuild } from "../lib/build-service.js";
 import { PidService } from "../lib/pid-service.js";
 import { resolveRootScope } from "../lib/settings.js";
-import { describeLinkedRepos } from "../lib/repos/links.js";
 import { resolveStoreSettings } from "../lib/repos/store/settings.js";
-import { prepareRepositoriesForBuild } from "../lib/build-preparation.js";
 import { subscriptionServiceFor } from "../lib/repos/subscription-service.js";
 import { buildReloadWatchConfig, startConfigReloadWatch } from "../lib/watch-loop.js";
 import type { WatchHandle } from "../lib/watch-service.js";
 import { WatchService } from "../lib/watch-service.js";
-import {
-  footer,
-  heading,
-  log,
-  paragraph,
-  showCommandVars,
-  warning,
-} from "../utils/formatting.js";
+import { log, paragraph, showCommandVars } from "../utils/formatting.js";
 
 export default class Build extends BaseCommand {
   static description =
@@ -49,7 +40,7 @@ export default class Build extends BaseCommand {
       default: false,
     }),
     strict: Flags.boolean({
-      description: "Fail on any compilation error",
+      description: "Treat compile warnings as errors",
       default: false,
     }),
     watch: Flags.boolean({
@@ -71,37 +62,20 @@ export default class Build extends BaseCommand {
       "No Prune": flags["no-prune"],
     });
 
-    // A linked repository is read from a working copy instead of a published
-    // version, so it is announced every single time; a build that silently
-    // produced something different would be far worse than a noisy one.
-    const linked = describeLinkedRepos(this.configContext.sousDir);
-    if (linked.length > 0) warning(linked.join("\n"));
-
-    const repositories = subscriptionServiceFor({
-      configContext: this.configContext,
-      settings: this.settings,
-      shellEnv: this.shellEnv,
-    });
-
-    if (!flags["dry-run"] && !flags["no-compile"]) {
-      await prepareRepositoriesForBuild(repositories);
-    }
-
-    heading("Building");
-
     const buildOptions = {
       strict: flags.strict,
       rebuild: flags.rebuild,
       dryRun: flags["dry-run"],
       noCompile: flags["no-compile"],
       noPrune: flags["no-prune"],
-      configContext: this.configContext,
     };
 
-    const buildService = new BuildService();
-    const success = await buildService.build(this.settings, buildOptions);
-
-    footer();
+    const success = await runProjectBuild({
+      settings: this.settings,
+      configContext: this.configContext,
+      shellEnv: this.shellEnv,
+      options: buildOptions,
+    });
 
     if (!success && !flags.watch) {
       this.exit(1);
@@ -129,17 +103,23 @@ export default class Build extends BaseCommand {
 
       const watchService = new WatchService();
 
-      // Reruns compile + prune with the command's current settings. Called for
+      // Reruns the build with the command's current settings. Called for
       // partial rebuilds (with the changed file) and, after a clean reload, for
-      // full rebuilds. Owns the "Rebuilding" heading/footer.
+      // full rebuilds, which prepare the recipes again the way the first build did.
       const rebuild = async (changedFile?: string) => {
-        heading("Rebuilding");
-        await buildService.build(this.settings, {
-          ...buildOptions,
-          // --rebuild means full clean build on every trigger; skip partial optimisation
-          changedFile: buildOptions.rebuild ? undefined : changedFile,
+        // A failed rebuild has already listed its errors, and the watch keeps
+        // running so the next save can fix them.
+        await runProjectBuild({
+          settings: this.settings,
+          configContext: this.configContext,
+          shellEnv: this.shellEnv,
+          heading: "Rebuilding",
+          options: {
+            ...buildOptions,
+            // --rebuild means full clean build on every trigger; skip partial optimisation
+            changedFile: buildOptions.rebuild ? undefined : changedFile,
+          },
         });
-        footer();
       };
 
       const { handle, triggerFullRebuild } = startConfigReloadWatch({
@@ -154,6 +134,11 @@ export default class Build extends BaseCommand {
       // and a failure never breaks the watch; the last good answer stands.
       const pollSeconds = resolveStoreSettings(this.settings).watchPollSeconds;
       if (pollSeconds > 0) {
+        const repositories = subscriptionServiceFor({
+          configContext: this.configContext,
+          settings: this.settings,
+          shellEnv: this.shellEnv,
+        });
         const poll = setInterval(() => {
           void repositories
             .checkUpstream()

package/src/commands/compile.ts

@@ -34,7 +34,7 @@ export default class Compile extends BaseCommand {
   static flags = {
     ...BaseCommand.baseFlags,
     strict: Flags.boolean({
-      description: "Fail immediately on any error",
+      description: "Treat compile warnings as errors",
       default: false,
     }),
     rebuild: Flags.boolean({
@@ -113,7 +113,7 @@ export default class Compile extends BaseCommand {
 
     footer();
 
-    if (!success && flags.strict && !flags.watch) {
+    if (!success && !flags.watch) {
       this.exit(1);
     }
 

package/src/commands/init.ts

@@ -17,8 +17,7 @@ import path from "node:path";
 import { Args, Flags } from "@oclif/core";
 import { confirm } from "@inquirer/prompts";
 import { BaseCommand } from "../base-command.js";
-import { prepareRepositoriesForBuild } from "../lib/build-preparation.js";
-import { buildProjectOutputs } from "../lib/build-service.js";
+import { runProjectBuild } from "../lib/build-service.js";
 import {
   CONFIG_FILE_NAMES,
   SOUS_DIR_NAME,
@@ -28,7 +27,6 @@ import {
 } from "../lib/config-discovery.js";
 import { ConfigError } from "../lib/errors.js";
 import { nonInteractiveError } from "../lib/interactive.js";
-import { subscriptionServiceFor } from "../lib/repos/subscription-service.js";
 import {
   PROJECT_CONFIG_FORMATS,
   SOUS_PACKAGE_NAME,
@@ -45,7 +43,6 @@ import {
   blankLine,
   dryRunNotice,
   footer,
-  heading,
   log,
   paragraph,
   section,
@@ -262,8 +259,8 @@ export default class Init extends BaseCommand {
   }
 
   /**
-   * Adopts the config just written and builds the project with it, in the
-   * same two steps `sous build` takes: the repositories are prepared (which
+   * Adopts the config just written and builds the project with it, through
+   * the same build `sous build` runs: the repositories are prepared (which
    * seeds the core recipe into the store and pins it in the lockfile), then
    * the outputs are compiled.
    *
@@ -274,17 +271,12 @@ export default class Init extends BaseCommand {
       resolveConfigFlag(configPath, this.configLocator.cwd, this.configLocator.confDirOverride)
     );
 
-    await prepareRepositoriesForBuild(
-      subscriptionServiceFor({
-        configContext: this.configContext,
-        settings: this.settings,
-        shellEnv: this.shellEnv,
-      })
-    );
-
-    heading("Building the project");
-
-    const succeeded = await buildProjectOutputs(this.settings, this.configContext);
+    const succeeded = await runProjectBuild({
+      settings: this.settings,
+      configContext: this.configContext,
+      shellEnv: this.shellEnv,
+      heading: "Building the project",
+    });
 
     if (!succeeded) {
       throw new ConfigError(

package/src/commands/launch.ts

@@ -2,7 +2,8 @@ import { Args, Flags } from "@oclif/core";
 import { spawnSync } from "node:child_process";
 import fs from "node:fs";
 import { BaseCommand } from "../base-command.js";
-import { BuildService } from "../lib/build-service.js";
+import { runProjectBuild } from "../lib/build-service.js";
+import { ConfigError } from "../lib/errors.js";
 import { resolveRootScope, resolveTools } from "../lib/settings.js";
 import { displayError, footer, heading, showCommandVars } from "../utils/formatting.js";
 
@@ -85,16 +86,21 @@ export default class Launch extends BaseCommand {
       ...(passThroughArgs.length > 0 && { "Tool Args": passThroughArgs.join(" ") }),
     });
 
-    const buildService = new BuildService();
-
     do {
-      // Build step (unless --no-build)
+      // Build step (unless --no-build). A failed build stops here: the agent
+      // would otherwise start on outputs the build could not bring up to date.
       if (!flags["no-build"]) {
-        heading("Building");
-        await buildService.build(this.settings, {
+        const built = await runProjectBuild({
+          settings: this.settings,
           configContext: this.configContext,
+          shellEnv: this.shellEnv,
         });
-        footer();
+        if (!built) {
+          throw new ConfigError(
+            `The build failed, so ${args.tool} was not started. Fix the errors listed ` +
+              `above, or pass --no-build to start it with the outputs as they are.`
+          );
+        }
       }
 
       // Config-defined args first, then pass-through, then promptFile content

package/src/commands/prune.ts

@@ -1,7 +1,7 @@
 import { Flags } from "@oclif/core";
 import { BaseCommand } from "../base-command.js";
-import { BuildService, resolveStateFilePath } from "../lib/build-service.js";
-import { footer, heading, showCommandVars } from "../utils/formatting.js";
+import { runProjectBuild } from "../lib/build-service.js";
+import { showCommandVars } from "../utils/formatting.js";
 
 export default class Prune extends BaseCommand {
   static description = "Remove output files that are no longer in the current config";
@@ -22,19 +22,22 @@ export default class Prune extends BaseCommand {
   async run(): Promise<void> {
     const { flags } = await this.parse(Prune);
 
-    const stateFilePath = resolveStateFilePath(this.settings, this.configContext);
-
     showCommandVars({
       Project: this.projectLabel,
       Config: this.configContext.configPath,
       "Dry Run": flags["dry-run"],
     });
 
-    heading("Pruning");
-
-    const buildService = new BuildService();
-    await buildService.prune(this.settings, stateFilePath, flags["dry-run"], this.configContext);
-
-    footer();
+    // Prune goes through the same build path as everything else, with the
+    // compile step switched off: what counts as current depends on the recipes
+    // the lockfile pins, so they are restored first, or a recipe missing from
+    // the store would have its outputs pruned as if it were gone.
+    await runProjectBuild({
+      settings: this.settings,
+      configContext: this.configContext,
+      shellEnv: this.shellEnv,
+      heading: "Pruning",
+      options: { noCompile: true, dryRun: flags["dry-run"] },
+    });
   }
 }

package/src/commands/repo/remove.ts

@@ -14,7 +14,7 @@
 
 import { Args, Flags } from "@oclif/core";
 import { BaseCommand } from "../../base-command.js";
-import { buildProjectOutputs } from "../../lib/build-service.js";
+import { runProjectBuild } from "../../lib/build-service.js";
 import { ConfigError } from "../../lib/errors.js";
 import { resolveRootScope } from "../../lib/settings.js";
 import { subscriptionServiceFor } from "../../lib/repos/subscription-service.js";
@@ -175,11 +175,12 @@ export default class RepoRemove extends BaseCommand {
   private async rebuildProject(name: string): Promise<void> {
     await this.reloadDiscoveredConfig();
 
-    heading("Building the project");
-
-    const succeeded = await buildProjectOutputs(this.settings, this.configContext);
-
-    footer();
+    const succeeded = await runProjectBuild({
+      settings: this.settings,
+      configContext: this.configContext,
+      shellEnv: this.shellEnv,
+      heading: "Building the project",
+    });
 
     if (!succeeded) {
       throw new ConfigError(

package/src/commands/repo/unlink.ts

@@ -2,7 +2,7 @@ import fs from "node:fs";
 import path from "node:path";
 import { Args, Flags } from "@oclif/core";
 import { BaseCommand } from "../../base-command.js";
-import { buildProjectOutputs } from "../../lib/build-service.js";
+import { runProjectBuild } from "../../lib/build-service.js";
 import { ConfigError, isConfigError } from "../../lib/errors.js";
 import {
   NonInteractiveError,
@@ -409,11 +409,12 @@ export default class RepoUnlink extends BaseCommand {
   private async rebuildProject(name: string): Promise<void> {
     await this.reloadDiscoveredConfig();
 
-    heading("Building the project");
-
-    const succeeded = await buildProjectOutputs(this.settings, this.configContext);
-
-    footer();
+    const succeeded = await runProjectBuild({
+      settings: this.settings,
+      configContext: this.configContext,
+      shellEnv: this.shellEnv,
+      heading: "Building the project",
+    });
 
     if (!succeeded) {
       throw new ConfigError(

package/src/commands/subscription/add.ts

@@ -24,7 +24,7 @@
 
 import { Args, Flags } from "@oclif/core";
 import { BaseCommand } from "../../base-command.js";
-import { buildProjectOutputs } from "../../lib/build-service.js";
+import { runProjectBuild } from "../../lib/build-service.js";
 import { ConfigError } from "../../lib/errors.js";
 import { subscriptionServiceFor } from "../../lib/repos/subscription-service.js";
 import { formatAskReport } from "../../lib/vars/ask.js";
@@ -267,11 +267,12 @@ export default class SubscriptionAdd extends BaseCommand {
   private async rebuildProject(key: string): Promise<void> {
     await this.reloadDiscoveredConfig();
 
-    heading("Building the project");
-
-    const succeeded = await buildProjectOutputs(this.settings, this.configContext);
-
-    footer();
+    const succeeded = await runProjectBuild({
+      settings: this.settings,
+      configContext: this.configContext,
+      shellEnv: this.shellEnv,
+      heading: "Building the project",
+    });
 
     if (!succeeded) {
       throw new ConfigError(

package/src/commands/subscription/remove.ts

@@ -12,7 +12,7 @@
 
 import { Args, Flags } from "@oclif/core";
 import { BaseCommand } from "../../base-command.js";
-import { buildProjectOutputs } from "../../lib/build-service.js";
+import { runProjectBuild } from "../../lib/build-service.js";
 import { ConfigError } from "../../lib/errors.js";
 import { subscriptionServiceFor } from "../../lib/repos/subscription-service.js";
 import { renderTable, type TableColumn } from "../../utils/table.js";
@@ -163,11 +163,12 @@ export default class SubscriptionRemove extends BaseCommand {
   private async rebuildProject(key: string): Promise<void> {
     await this.reloadDiscoveredConfig();
 
-    heading("Building the project");
-
-    const succeeded = await buildProjectOutputs(this.settings, this.configContext);
-
-    footer();
+    const succeeded = await runProjectBuild({
+      settings: this.settings,
+      configContext: this.configContext,
+      shellEnv: this.shellEnv,
+      heading: "Building the project",
+    });
 
     if (!succeeded) {
       throw new ConfigError(

package/src/commands/subscription/update.ts

@@ -19,7 +19,7 @@
 
 import { Args, Flags } from "@oclif/core";
 import { BaseCommand } from "../../base-command.js";
-import { buildProjectOutputs } from "../../lib/build-service.js";
+import { runProjectBuild } from "../../lib/build-service.js";
 import { ConfigError } from "../../lib/errors.js";
 import { subscriptionServiceFor } from "../../lib/repos/subscription-service.js";
 import { describeUpdateScope } from "../../lib/repos/update-plan.js";
@@ -198,11 +198,12 @@ export default class SubscriptionUpdate extends BaseCommand {
   private async rebuildProject(): Promise<void> {
     await this.reloadDiscoveredConfig();
 
-    heading("Building the project");
-
-    const succeeded = await buildProjectOutputs(this.settings, this.configContext);
-
-    footer();
+    const succeeded = await runProjectBuild({
+      settings: this.settings,
+      configContext: this.configContext,
+      shellEnv: this.shellEnv,
+      heading: "Building the project",
+    });
 
     if (!succeeded) {
       throw new ConfigError(

package/src/lib/build-preparation.ts

@@ -1,9 +1,8 @@
 /**
  * The step that runs before a project's outputs are compiled, and what it says
- * while it runs. `sous build` runs it on every build, and `sous init` runs it
- * for the first build of a project it has just set up; both must say the same
- * things about the same events, so the reporting lives here rather than in
- * either command.
+ * while it runs. `runProjectBuild` (`build-service.ts`) calls it, and every
+ * command that builds goes through that one function, so the step and its
+ * reporting are the same whichever command the user typed.
  */
 
 import type { SubscriptionService } from "./repos/subscription-service.js";