CI: sync Credenza Space (101ae9b)

Dockerfile

@@ -9,7 +9,7 @@
 # this file would publish the application; deploy/deploy_to_hf.py has a test
 # that fails if app source ever enters the sync payload.
 #
-# The `:5b506315a4b4e22a553fe9e7c38090acea5883c7` tag below is what a developer building this file locally gets.
+# The `:101ae9bcea84b10d2305e0c5b329f3cfdb58a698` tag below is what a developer building this file locally gets.
 # CI does NOT deploy it as written: `deploy_to_hf.py` rewrites the tag to the
 # commit SHA before syncing.
 #
@@ -18,6 +18,6 @@
 # no-op commit, no HF rebuild, and a Space that goes on serving the previous
 # image while every gate in the pipeline reports success. It happened. Pinning
 # the SHA gives the commit something to differ by, and names the exact image
-# built from this source rather than whatever `:5b506315a4b4e22a553fe9e7c38090acea5883c7` resolves to at pull time.
+# built from this source rather than whatever `:101ae9bcea84b10d2305e0c5b329f3cfdb58a698` resolves to at pull time.
 
-FROM ghcr.io/cloudronin/credenza:5b506315a4b4e22a553fe9e7c38090acea5883c7
+FROM ghcr.io/cloudronin/credenza:101ae9bcea84b10d2305e0c5b329f3cfdb58a698