Unclear error and recovery on active environment post blueprint update

[1800joe]

v0.10.3

• Error occurred after saving blueprint.yaml. See below
• Toggling env switch produces same error.
• Triggering build through superficial change (whitespace) partially resolved. launch services stalled see below
• Launch services eventually fails
• Hard reset Workshop and changing the blueprint before restart led to a resolution.

Eventually got it working, but something interesting is going on.

Take this blueprint:

name: Next Site
components:
  - name: NextSite
    type: service
    image: node:20-alpine
    port: 3000
    build:
      # 👇 intentional/selective ordering of 'copy' and 'run' steps
      # will make it possible to take advantage of cached build
      # layers in Noop Workshop (TLDR - speedier subsequent builds!)
      steps:
        # first copy over dependency files and install...
        - copy: [package.json, yarn.lock]
        - run: yarn install --immutable
        # ...then copy over project files before generating build assets
        - copy: [next.config.mjs, tsconfig.json]
        - copy: public/
        - copy: src/
        - run: yarn build
    runtime:
      command: yarn start

  # - name: NextStatic
  #   type: static
  #   image: node:20-alpine
  #   build:
  #     steps:
  #       - copy: [package.json, yarn.lock]
  #       - run: yarn install --immutable
  #       - copy: [next.config.mjs, tsconfig.json]
  #       - copy: public/
  #       - copy: src/
  #       - run: yarn build
  #       - directory: build/
routes:
  - target:
      component: NextSite

If I uncomment the static, I get the ambiguous errors. Otherwise it works. Also worth noting that that state appears unrecoverable without a reset + "fixing" of blueprint.