The template is a machine, not a manifest

The team's workspace template needs the new toolchain. On platforms where a template is configuration, that's an edit to the definition, a rebuild, and a round of "works in the manifest, breaks in the workspace" debugging.

On Hoody, the template is a golden container. You open its terminal, install the toolchain, verify it by using it, and snapshot. New workspaces are copies of that snapshot: they start as the machine you just tested, not as a recipe for one. Existing workspaces catch up with POST /containers/{id}/sync, which carries over what changed on the source.

The gap between what the template says and what the workspace is can't open, because they're the same kind of object.