Address cpflow docs review follow-up

Author: justin808

.controlplane/shakacode-team.md

@@ -68,7 +68,8 @@ Advanced optional settings are documented upstream in the
 
 Current workflow wrappers are pinned to upstream `control-plane-flow` PR #318 at
 `19ca93eadcba81e7438f26ab55a0f2ca7ace82b0` for downstream testing. After 5.0.1
-ships, repin the wrappers to `v5.0.1`.
+ships, repin the wrappers to `v5.0.1`; do not treat the temporary SHA as the
+steady-state master configuration.
 
 If staging moves off `master`, update both `STAGING_APP_BRANCH` and the branch
 filter in `.github/workflows/cpflow-deploy-staging.yml`.

.github/cpflow-help.md

@@ -2,7 +2,7 @@
 
 These commands are generated by [cpflow](https://github.com/shakacode/control-plane-flow).
 For full setup, version-pinning, and troubleshooting details, see the upstream
-[CI automation guide](https://github.com/shakacode/control-plane-flow/blob/19ca93eadcba81e7438f26ab55a0f2ca7ace82b0/docs/ci-automation.md).
+[CI automation guide](https://github.com/shakacode/control-plane-flow/blob/main/docs/ci-automation.md).
 
 ## Pull Request Commands
 
@@ -56,8 +56,9 @@ the environment approval gate passes.
 ## Version Locking
 
 Current wrappers pin both the reusable workflow `uses:` ref and
-`control_plane_flow_ref` to `19ca93eadcba81e7438f26ab55a0f2ca7ace82b0` for
-upstream PR testing. After `cpflow` 5.0.1 ships, switch both refs to `v5.0.1`.
+`control_plane_flow_ref` to `19ca93eadcba81e7438f26ab55a0f2ca7ace82b0` only for
+upstream PR testing. Do not leave production automation on this temporary SHA:
+after `cpflow` 5.0.1 ships, switch both refs to `v5.0.1`.
 Leave `CPFLOW_VERSION` unset so the workflow builds cpflow from the same
 checked-out upstream source. If you set `CPFLOW_VERSION`, it must match the
 release tag, for example `CPFLOW_VERSION=5.0.1` with