implementing review feedback.

Signed-off-by: Kamesh Akella <kakella@redhat.com>

Author: kami619

CONSTITUTION.md

@@ -29,11 +29,11 @@ All changes MUST follow existing code patterns and architecture.
 
 ### III. Test Independence
 
-Each test MUST verify a single aspect of the product and SHOULD be independent of other tests.
+Each test MUST verify a single aspect of the product and May Be be dependent on other tests.
 
 - Tests MUST have a clear purpose and be easy to understand
 - Tests MUST be properly documented with docstrings explaining what the test does
-- When test dependencies exist, use pytest-dependency plugin to declare them explicitly
+- When test dependencies exist, use pytest-dependency plugin to declare them explicitly, encourage use of dependency marker(s) when possible.
 - Group related tests in classes only when they share fixtures; never group unrelated tests
 
 **Rationale**: Independent tests enable parallel execution, easier debugging, and selective test runs.
@@ -50,7 +50,7 @@ Fixtures MUST do one thing only and follow proper scoping.
 
 **Rationale**: Single-responsibility fixtures are easier to debug, reuse, and compose.
 
-### V. Kubernetes API First
+### V. Interacting with Kubernetes Resources
 
 All cluster interactions MUST use openshift-python-wrapper or oc CLI.
 
@@ -147,9 +147,7 @@ This constitution supersedes all other practices when there is a conflict. All P
 
 ### Versioning Policy
 
-- MAJOR: Backward-incompatible governance/principle removals or redefinitions
-- MINOR: New principle/section added or materially expanded guidance
-- PATCH: Clarifications, wording, typo fixes, non-semantic refinements
+No versioning policy is enforced.
 
 ### Compliance Review