chore: Update subproject commit reference in wild-cloud

CLAUDE.md

@@ -9,4 +9,4 @@ Wild Cloud applications are custom packages designed to be deployed to Wild Clou
 
 The Wild Cloud API maintains data for each Wild Cloud instance in its configured WILD_API_DATA_DIR. A data directory is intended to be checked into version control (e.g., git) to track changes to the configuration of Wild Cloud instances and their deployed applications over time. These are designed to follow infrastructure-as-code and gitops principles, allowing experienced devops users to manage their Wild Cloud instances using familiar tools and workflows. For ease of access, a symlink to our Wild API data dir is made at ./wild-cloud-redmond-data. `payne-cloud` is a PRODUCTION instance. Do not make changes to it without considering the impact and receiving permission. For development, use `test-cloud`.
 
-We have a public website for Wild Cloud (https://mywildcloud.org) with source in `wild-cloud/docs`.
+We have a public website for Wild Cloud https://mywildcloud.org.

activate.sh

@@ -1,21 +0,0 @@
-#!/usr/bin/env bash
-
-# Bash completion
-if [ -n "$BASH_VERSION" ]; then
-    # kubectl completion
-    if command -v kubectl &> /dev/null; then
-        eval "$(kubectl completion bash)"
-    fi
-
-    # talosctl completion
-    if command -v talosctl &> /dev/null; then
-        eval "$(talosctl completion bash)"
-    fi
-
-    # wild completion
-    if command -v wild &> /dev/null; then
-        eval "$(wild completion bash)"
-    fi
-fi
-
-source <(wild instance env)

docs/branding.md

@@ -0,0 +1,9 @@
+# Branding
+
+## Colors
+
+fd9631 (gold)
+fd6331 (burn orange)
+a49ffa (baby blue)
+d06463 (peach)
+ca95c8 (lilac)