Control flow, documentation and update PROJECT ref

defaults.sh

@@ -106,7 +106,7 @@ export PRIMARY_DOMAIN=
 # this is the git commit of the project/ sub git repo.
 # used in the migration script to switch into past for backup
 # then back to present (TARGET_PROJECT_GIT_COMMIT) for restore.
-export TARGET_PROJECT_GIT_COMMIT=5260567a1871c41ef5cbf5a4a71016e018169c0e
+export TARGET_PROJECT_GIT_COMMIT=ba153765a76d32ab8d527db2c40f28891b2f9be5
 
 # 
 export TESTNET_BLOCK_HASH=00000000d8277ba1ca66b40b3e3476629e6f0f97c5b8cfaeabfe402e55db223a

deployment/destroy.sh

@@ -50,11 +50,6 @@ for PROJECT_CHAIN in ${DEPLOYMENT_STRING//,/ }; do
 
     # if the user sets USER_TARGET_PROJECT, let's ensure the project exists.
     if [ -n "$USER_TARGET_PROJECT" ]; then
-        if ! lxc project list | grep -q "$USER_TARGET_PROJECT"; then
-            echo "ERROR: the project does not exist! Nothing to destroy."
-            exit 1
-        fi
-
         if [ "$PROJECT_NAME" != "$USER_TARGET_PROJECT" ]; then
             echo "INFO: Skipping project '$PROJECT_NAME' since the system owner has used the --project= switch."
             exit

deployment/help.txt

@@ -11,4 +11,5 @@ You are in the Sovereign Stack Management Environment (SSME). From here, you can
 
 For more infomation about all these topics, consult the Sovereign Stack website starting with:
 
-  - https://www.sovereign-stack.org/tag/instance-management/
+  - https://www.sovereign-stack.org/tag/deployment-management/
+