fix checking of command status

In the spirit of pr #2589, we correct similar cases where the string
"status" instead of `$status` was being tested for a value.

In `bin/csv2entry.sh` changed VERSION from "1.1 2024-07-20"
to "1.1.1 2024-07-22".

In `bin/entry2csv.sh` changed VERSION from "1.1 2024-07-20"
to "1.1.1 2024-07-22".

In `bin/gen-sitemap.sh` changed VERSION from "1.3.10 2024-07-18"
to "1.3.11 2024-07-22".

In `bin/gen-status.sh` changed VERSION from "1.5.5 2024-07-18"
to "1.5.6 2024-07-22".

In `bin/md2html.sh` changed VERSION from "1.5.2 2024-07-18"
to "1.5.3 2024-07-22".

In `bin/tar-entry.sh` changed VERSION from "1.3.6 2024-04-28"
to "1.3.7 2024-07-22".

In `bin/tar-year.sh` changed VERSION from "1.2.4 2024-04-28"
to "1.2.5 2024-07-22".

Performed `make www` to accomplish the above and to test under macOS.

bin/md2html.sh

@@ -141,7 +141,7 @@ shopt -s lastpipe	# run last command of a pipeline not executed in the backgroun
 
 # set variables referenced in the usage message
 #
-export VERSION="1.5.2 2024-07-18"
+export VERSION="1.5.3 2024-07-22"
 NAME=$(basename "$0")
 export NAME
 export V_FLAG=0
@@ -2300,7 +2300,7 @@ if [[ -z $NOOP ]]; then
 	    mv -f -- "$TMP_INDEX_HTML" "$OUTPUT_HTML"
 	    status="$?"
 	fi
-	if [[ status -ne 0 ]]; then
+	if [[ $status -ne 0 ]]; then
 	    echo "$0: ERROR: mv -f -- $TMP_INDEX_HTML $OUTPUT_HTML filed, error code: $status" 1>&2
 	    exit 139
 	elif [[ $V_FLAG -ge 1 ]]; then