fix(e2e): #1644 Part A — SC2034 disable directive for PARENT_TOKEN

shellcheck E2E job on PR#1680 (task 146208) flagged: In tests/e2e/test_peer_visibility_mcp_local.sh line 245: PARENT_TOKEN=$(echo "$P_RESP" | extract_auth_token) ^----------^ SC2034 (warning): PARENT_TOKEN appears unused. PARENT_TOKEN is captured for symmetry with the per-sibling auth-token capture below + reserved as a hand-off point for follow-up parent-auth flows. The current downstream peer-visibility checks reach the parent workspace via the admin token, so PARENT_TOKEN isn't dereferenced — surfacing as SC2034. Same disable-directive pattern as the WS_IDS_MAP / VERDICT_MAP declarations a few lines below (lines 257, 260) — surface the intention via comment rather than silence the lint. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-22 03:50:50 -07:00
parent 50b9181fd4
commit d7519d815a
1 changed files with 5 additions and 0 deletions
@@ -242,6 +242,11 @@ log "1/5 provisioning parent ($PARENT_RUNTIME, mode=$PV_LOCAL_PROVISION_MODE) +
 P_RESP=$(curl -s -X POST "$BASE/workspaces" ${ADMIN_AUTH[@]+"${ADMIN_AUTH[@]}"} -H "Content-Type: application/json" \
  -d "{\"name\":\"${NAME_PREFIX}-parent\",\"runtime\":\"$PARENT_RUNTIME\",\"tier\":3$PARENT_EXTRA,\"secrets\":$PARENT_SECRETS}")
 PARENT_ID=$(echo "$P_RESP" | python3 -c 'import json,sys;print(json.load(sys.stdin).get("id",""))' 2>/dev/null)
+# PARENT_TOKEN captured for symmetry with the per-sibling auth-token
+# capture in the runtime loop below + reserved for follow-up steps
+# that need parent-side auth. Current downstream steps reach the parent
+# via admin token, so the variable isn't dereferenced — SC2034.
+# shellcheck disable=SC2034 # captured for downstream parent-auth use; see #1644 follow-up
 PARENT_TOKEN=$(echo "$P_RESP" | extract_auth_token)
 if [ -z "$PARENT_ID" ]; then
  echo "::error::parent create failed: $(echo "$P_RESP" | head -c 300)" >&2