refactor(fleet): dispatch suites with rc inputs and drop parent repin and floor gate

.github/actions/dispatch-suite/action.yaml

@@ -105,10 +105,11 @@ runs:
           DISPATCH_TS=$(date -u +%Y-%m-%dT%H:%M:%SZ)
           echo "Dispatching $TARGET_WORKFLOW in $TARGET_REPO @ $TARGET_REF (since $DISPATCH_TS)"
 
-          # NOTE: cascade_version / cascade_version_sha are only forwarded when
-          # non-empty. No caller passes them today, so this stays inert: the
-          # suites do not define those inputs yet, and an undeclared input would
-          # error with "unexpected inputs" if passed unconditionally.
+          # NOTE: cascade_version / cascade_version_sha are forwarded to the
+          # target suite only when non-empty, so a suite that has not declared
+          # those inputs is unaffected (an undeclared input passed
+          # unconditionally would error with "unexpected inputs"). When present,
+          # they tell the suite which version and peeled commit to self-repin to.
           local -a EXTRA_ARGS=()
           if [ -n "$CASCADE_VERSION" ]; then
             EXTRA_ARGS+=(-f "cascade_version=$CASCADE_VERSION")

.github/scripts/bump-suite-bootstrap-pin.sh

@@ -18,8 +18,8 @@
 # Callers detect "did anything change" from git status, so the script itself
 # only reports argument or IO failure through its exit code.
 #
-# The two rewritten shapes mirror exactly what check-suite-tooling-floor.sh reads
-# back, so a bump here clears the floor check for the same repo.
+# Both shapes are the suite's bootstrap tooling pin, so a bump here moves the
+# committed pin onto the freshly published release for the same repo.
 #
 # Usage:
 #   bump-suite-bootstrap-pin.sh <suite-file> <target-version>
@@ -66,8 +66,8 @@ fi
 #   2. the version input:        version: vX.Y.Z
 # Only bare semver pins are matched, so a moving ref (@main) or an unrelated
 # non-semver value is never touched. A `version:` line carrying a vX.Y.Z value
-# is the suite's setup-cli input; this mirrors the floor check's own extraction,
-# which treats a `version: vX.Y.Z` line as the tooling pin.
+# is the suite's setup-cli input, so a `version: vX.Y.Z` line is treated as the
+# tooling pin alongside the action ref.
 tmp="$(mktemp)"
 trap 'rm -f "$tmp"' EXIT