feat(template): add Self-Validation Testing as 14th testing type (#125)

Add Self-Validation Testing to the STP framework so authors consider
whether new tests should be included in the self-validation package.

Changes:
- stp.md: new checkbox under Functional group after Regression
- child-stp.md: matching entry with parent STP reference
- AGENTS.md: review checklist updated (13→14 types), new guidance item
- stp-guide.md: added to Types of Testing list

Signed-off-by: rnetser <rnetser@redhat.com>
Co-authored-by: PI (claude-opus-4-6) <noreply@pi.dev>
Co-authored-by: Claude <noreply@anthropic.com>

Author: 3 people

AGENTS.md

@@ -160,10 +160,12 @@ Assisted-by: Claude <noreply@anthropic.com>
 ### II.2 — Test Strategy
 
 - [ ] All testing types are addressed (checked or unchecked with justification)
-- [ ] All 13 testing types from the template are present (Functional, Automation, Regression,
+- [ ] All 14 testing types from the template are present (Functional, Automation, Regression, Self-Validation,
   Performance, Scale, Security, Usability, Monitoring, Compatibility, Upgrade, Dependencies,
   Cross Integrations, Cloud Testing)
 - [ ] Unchecked items without details = incomplete review — flag this
+- [ ] Self-Validation: if the feature introduces core operational scenarios, confirm whether
+  any new tests should be included in the self-validation test package
 - [ ] Usability Testing: if checked, must describe what QE tests (not "UI team owns it")
 - [ ] If UI team owns UI testing, uncheck Usability and note in details
 - [ ] Monitoring: explicitly state whether alerts/metrics are required

docs/stp-guide.md

@@ -99,6 +99,7 @@ QE perspective on testing priorities:
 - Usability Testing
 - Compatibility Testing
 - Regression Testing
+- Self-Validation Testing
 - Upgrade Testing
 - Backward Compatibility Testing
 

stps/stp-template/child-stp.md

@@ -117,6 +117,9 @@ uncheck and state "Covered by parent STP" or "Covered by [SIG name]". -->
 - [ ] **Regression Testing**
   - *Details:* [Which existing SIG test suites run on the feature cluster]
 
+- [ ] **Self-Validation Testing** — Tests to include in the self-validation package
+  - *Details:* [SIG-specific, or "Covered by parent STP"]
+
 **Non-Functional**
 
 - [ ] **Performance Testing**

stps/stp-template/stp.md

@@ -266,6 +266,13 @@ Example: Strategy says "Performance testing is applicable — we will measure mi
 - [ ] **Regression Testing** — Verifies that new changes do not break existing functionality
   - *Details:* [ Add details ]
 
+- [ ] **Self-Validation Testing** — Should any of the new tests be included in the self-validation test package?
+  <!-- The self-validation package is a curated subset of tests that run as product health checks.
+  Consider whether any new test scenarios validate core feature functionality that should
+  be part of self-validation. Self-validation tests should be fast, reliable, and cover
+  critical operational scenarios. -->
+  - *Details:* [ Add details ]
+
 **Non-Functional**
 
 - [ ] **Performance Testing** — Validates feature performance meets requirements (latency, throughput, resource usage)