diff --git a/docs/showcase/cli-tools/tool-and-validation-management.md b/docs/showcase/cli-tools/tool-and-validation-management.md
index 6cc76f3cc..d71108cea 100644
--- a/docs/showcase/cli-tools/tool-and-validation-management.md
+++ b/docs/showcase/cli-tools/tool-and-validation-management.md
@@ -368,6 +368,12 @@ $ agents tool show qa/coverage-check
 (`namespace/short-name`). For validations, the panel includes an extra
 **Validation Mode** field showing `required` or `informational`.
 
+> **Why do capabilities show as `(default)`?**
+> The detail view collapses the default capability flags and omits resource slot
+> bindings when they match the defaults stored in the registry. The values you
+> set during registration are still persisted and enforced when the tool runs,
+> even though the summary view shows `(default)` / `(none)`.
+
 ---
 
 ### Step 7: Get machine-readable JSON output
diff --git a/docs/showcase/examples.json b/docs/showcase/examples.json
index a9f1908f0..cbe5f8931 100644
--- a/docs/showcase/examples.json
+++ b/docs/showcase/examples.json
@@ -68,6 +68,31 @@
       "educational_value": "high",
       "generated_by": "uat-tester",
       "generated_at": "2026-04-07"
+    },
+    {
+      "title": "Managing Tools and Validations in CleverAgents",
+      "category": "cli-tools",
+      "path": "cli-tools/tool-and-validation-management.md",
+      "feature": "Tool and validation management",
+      "commands": [
+        "agents tool add --config examples/tools/custom-tool.yaml",
+        "agents validation add --config examples/validations/required-validation.yaml",
+        "agents validation add --config examples/validations/wrapped-validation.yaml",
+        "agents tool list",
+        "agents tool list --type validation",
+        "agents tool list --type tool",
+        "agents tool list --namespace qa",
+        "agents tool show local/line-counter",
+        "agents tool show qa/coverage-check",
+        "agents tool list --format json",
+        "agents tool show local/line-counter --format json",
+        "agents validation add --config examples/validations/required-validation.yaml --update",
+        "agents tool remove --yes local/line-counter"
+      ],
+      "complexity": "intermediate",
+      "educational_value": "high",
+      "generated_by": "uat-tester",
+      "generated_at": "2026-04-07"
     }
   ],
   "categories": {
@@ -92,5 +117,5 @@
       "keywords": ["test", "pytest", "behave", "unittest", "automation", "QA"]
     }
   },
-  "last_updated": null
+  "last_updated": "2026-04-07"
 }
diff --git a/robot/coverage_threshold.robot b/robot/coverage_threshold.robot
index 7d081bffc..455afca74 100644
--- a/robot/coverage_threshold.robot
+++ b/robot/coverage_threshold.robot
@@ -9,7 +9,7 @@ Suite Teardown    Cleanup Test Environment
 *** Test Cases ***
 Noxfile Contains Coverage Threshold Constant
     [Documentation]    Verify COVERAGE_THRESHOLD = 97 is defined in noxfile.py
-    [Tags]    coverage    config    tdd_issue    tdd_issue_4305    tdd_expected_fail
+    [Tags]    coverage    config    tdd_issue    tdd_issue_4305
 
     ${content}=    Get File    ${WORKSPACE}/noxfile.py
     Should Contain    ${content}    COVERAGE_THRESHOLD = 97
@@ -34,8 +34,7 @@ Pyproject Coverage Source Includes Src
 
 Coverage Threshold Is 97 In Noxfile
     [Documentation]    Verify noxfile enforces 97% threshold via fail-under
-    [Tags]    tdd_issue    tdd_issue_4227    tdd_expected_fail
-    [Tags]    coverage    config
+    [Tags]    coverage    config    tdd_issue    tdd_issue_4227
     ${content}=    Get File    ${WORKSPACE}/noxfile.py
     Should Contain    ${content}    --fail-under=