Added per-theme build-script policy for the standalone subtree repos

The root `pnpm-workspace.yaml` carries the `dtrace-provider` build-script
denial, but it does not propagate to the standalone repos that CI
subtree-pushes from `packages/<theme>` (e.g. `TryGhost/Alto`). Those
repos now pin pnpm via `packageManager`, so without a policy of their
own, `pnpm install` in a standalone checkout exits non-zero with
ERR_PNPM_IGNORED_BUILDS (verified in a clean simulation).

Ship a settings-only `pnpm-workspace.yaml` inside each theme so the
standalone repos install cleanly. pnpm ignores the nested files when
installing from the monorepo root — verified that all 19 workspace
projects still resolve and the lockfile is unchanged.

Author: aileen

gulpfile.js

@@ -89,7 +89,8 @@ function zipper(done) {
             '!node_modules', '!node_modules/**',
             '!dist', '!dist/**',
             '!pnpm-debug.log',
-            '!pnpm-lock.yaml'
+            '!pnpm-lock.yaml',
+            '!pnpm-workspace.yaml'
         ]),
         zip(filename),
         dest('dist/')

pnpm-workspace.yaml

@@ -0,0 +1,9 @@
+# This file exists for the standalone repo this theme is subtree-pushed to:
+# without it, pnpm 11 fails `pnpm install` on the un-triaged dtrace-provider
+# build script. When installing from the monorepo root, pnpm uses the root
+# pnpm-workspace.yaml instead (including its linkWorkspacePackages setting)
+# and ignores this file.
+allowBuilds:
+  # Optional dtrace bindings for bunyan (a gscan dependency); not needed to
+  # build, test, or zip the theme.
+  dtrace-provider: false