fix: ban array indexing in monitoring scripts — use explicit mapping

[JeremyDev87]

Purpose

zsh arrays are 1-indexed, bash arrays are 0-indexed. Using arrays in monitoring scripts caused wrong issue mapping and deletion of valid RESULT.json files.

Solution

Never use array indexing. Always use explicit "N:value" string mapping:

# BANNED
EXPECTED=("#888" "#811")
${EXPECTED[$IDX]}

# REQUIRED
for PANE_INFO in "1:#888" "2:#811"; do
  N="${PANE_INFO%%:*}"
  EXP="${PANE_INFO##*:}"
done

Add to taskMaestro SKILL.md and parallel-orchestrator agent.

References

• Incident: Wave B stale RESULT.json deletion due to zsh 1-index
• Parent: Improve taskMaestro orchestration reliability (session 2 retrospective) #900

[JeremyDev87]

Implemented in PR #918 (batch update)