Refresh bench tooling and Claude profiles

[brettheap]

Summary

• mount portable Claude account profiles where applicable
• refresh the bench-specific runtime and administration toolchain
• keep the bench aligned with the synchronized workBenches parent

Validation

• git diff --check
• changed shell scripts: bash -n
• changed Dockerfile: docker buildx build --check

Summary by Sourcery

Update devcontainer and layer2 Docker configuration to refresh bench tooling and align with current workbench setup.

Build:

• Adjust devcontainer configuration to match updated bench runtime and tooling.
• Refresh layer2 Dockerfile settings to support the revised bench environment.

[brettheap]

@codex review

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR refreshes the devcontainer and layer2 Docker image configuration to align the bench environment with updated Claude profiles and the synchronized workBenches parent, including tooling/runtime updates for local development and administration.

File-Level Changes

Change	Details	Files
Update devcontainer configuration to mount portable Claude profiles and align bench tooling with the parent workBenches setup.	Adjust devcontainer settings to mount and expose portable Claude account profiles where applicable Refresh installed tooling/runtime inside the devcontainer to match the bench-specific administration toolchain Synchronize devcontainer environment configuration with the shared workBenches parent conventions	.devcontainer/devcontainer.json
Refresh layer2 Docker image definition to match the updated bench runtime and tooling.	Update base image and/or build arguments to reflect the refreshed bench runtime Adjust installed dependencies and tools to align with the new administration/tooling stack Ensure Dockerfile configuration remains compatible with devcontainer and parent workBenches expectations	Dockerfile.layer2

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Copilot]

Pull request overview

This PR refreshes the .NET bench container/tooling configuration to better align with the upstream workbench setup, including portable Claude profile mounting and updated Kubernetes tooling configuration.

Changes:

• Bumped Layer 2 image metadata version and parameterized the kubectl APT repo minor version in Dockerfile.layer2.
• Added a devcontainer bind mount for ~/.claude-profiles to support portable Claude account profiles.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
Dockerfile.layer2	Updates layer metadata and parameterizes the kubectl APT repository version.
.devcontainer/devcontainer.json	Adds a new bind mount for ~/.claude-profiles in the devcontainer.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e2cb6f3204

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Make optional Claude profile mount safe

For hosts that do not already have ~/.claude-profiles, this new devcontainer bind mount prevents the container from starting: devcontainer mounts entries use Docker --mount syntax, and Docker errors when a bind source path is absent. Since this profile directory only exists on machines that have opted into that layout, consider creating it in initializeCommand or otherwise making the mount safe; otherwise users who satisfied the previous credential mounts but have no profile directory can no longer open the bench.

Useful? React with 👍 / 👎.