needs-decision: bump OpenShell console pin from v0.1.1 to v0.1.2 (digest unresolved) #760

What happened

While bumping OpenShell to v0.1.5-rhaiv.2 (gateway release line 0.1), the
/update-openshell agent found a newer OpenShell dashboard (console) release on
the same release line: v0.1.2, one release ahead of the currently pinned
v0.1.1 (OPENSHELL_CONSOLE_DIGEST in OPENSHELL_VERSION).

Release notes: https://github.com/Gkrumbach07/openshell-dashboard/releases/tag/v0.1.2

Per skills/tooling/update-openshell/SKILL.md Step 3b, the console should track
the newest dashboard release on the gateway's release line, pinned by image
digest.

Why this is not done yet

The agent run executed in a sandbox with no outbound network access except
gh/git to github.com. The Quay tag API
(https://quay.io/api/v1/repository/gkrumbach07/openshell-dashboard/tag/...,
the usual way to resolve the release tag to its manifest_digest) and skopeo inspect both require reaching quay.io, which this run could not do.
Fabricating or reusing the old v0.1.1 digest under a v0.1.2 label was
rejected as unsafe: it would silently point at the wrong image.

What a human (or a run with quay.io access) needs to do

1. Resolve the digest for quay.io/gkrumbach07/openshell-dashboard:0.1.2
   (skopeo inspect --format '{{.Digest}}' docker://quay.io/gkrumbach07/openshell-dashboard:0.1.2
   or the Quay tag API).
2. Set OPENSHELL_CONSOLE_DIGEST in OPENSHELL_VERSION to that digest and run
   make sync-openshell-version (stamps defaultConsoleImage in
   components/control-plane/internal/gateway/config.go).
3. Check the env contract: compare buildConsoleDeployment in
   components/control-plane/internal/gateway/console.go against the v0.1.2
   release's docs/configuration.md for any new, renamed, or changed env var.
4. Optionally trial on one gateway before merging (see Step 3b in the skill).

Reply with the resolved version or digest and the /update-openshell skill's
Step 0 will pick this up on its next scheduled run and open a PR.