Improve edge scenario in RC script

[rudimusmaximus]

objective / purpose
Improve edge scenario experience where user attempts to 'make test ready' a freshly updated script (whether new TC or updated RC) that has a short semVer in it and HAS not updated for long semVer. Test each. There may be an issue when doing this for a registered release candidate script. confirm

completion checklist

• [ ] Discovered in: v0.5.0
• [ ] Resolved/introduced in: whichx.y.z
• [ ] Design Ready - labels, complexity, optional estimate
• [ ] Development Ready - design and change list created, updated complexity label and estimates
• [ ] Changes Listed (mark each member as completed update as needed)
  • [ ] tbd
• [ ] Developer Tested - Test Copies (Disposable Alpha "DA!s" and Release Candidate)

POST LIVE:

• [ ] Beta Tested - Live to a controlled audience  
• [ ] Customer Experience - Live analytics reveal working for customers  

full pipeline documentation

---

Overview - describe with history and related items

Solution Design

What's New Entry

Solution Implementation Notes

Developer Testing- Disposable Alpha and Release Candidate

Live Testing - Beta live to controlled audience

Customer Experience - Re-open and append if issues for customers