fix(test-driven-development): address round-4 findings — graph labels, comment, emoji, type annotation

Finding 1+5 (Important/Minor): verify_green diamond had unlabeled third edge
causing ambiguity about when to exit to next vs verify_invariant. Labeled the
exit as 'done (post-refactor)' and first-pass edge as 'yes (first pass)'.
Added prose note in REFACTOR: invariant check applies once per bug fix, not
after each refactor cycle.

Finding 2 (Important): Comment 'New methods MUST include the same arg' overstated
the enforcement — the table only gates methods explicitly listed. Updated comment
to instruct maintainers to add a row when adding a new method.

Finding 3 (Minor): Emoji checkmarks (✓) in new-flow.md violated workspace
convention (no emoji without user request). Replaced with [confirmed: ...] text.

Finding 4 (Minor): spy.lastArgs type unspecified; map[string]any silently returns
wrong comparison without type assertion. Updated comment to specify map[string]string
or explicit type assertion.

Author: intel352

skills/test-driven-development/SKILL.md

@@ -61,12 +61,12 @@ digraph tdd_cycle {
     verify_red -> green [label="yes"];
     verify_red -> red [label="wrong\nfailure"];
     green -> verify_green;
-    verify_green -> verify_invariant [label="yes"];
+    verify_green -> verify_invariant [label="yes\n(first pass)"];
     verify_green -> green [label="no"];
+    verify_green -> next [label="done\n(post-refactor)"];
     verify_invariant -> refactor [label="proven"];
     verify_invariant -> red [label="test\ndoesn't\ncatch bug"];
     refactor -> verify_green [label="stay\ngreen"];
-    verify_green -> next;
     next -> red;
 }
 ```
@@ -225,6 +225,8 @@ After green only:
 
 Keep tests green. Don't add behavior.
 
+**Note:** The Verify Regression Invariant step applies once per bug fix (after the initial GREEN), not after each refactor cycle. Refactoring must not change the fix path — if it does, that's a new production code change requiring a new test.
+
 ### Repeat
 
 Next failing test for next feature.
@@ -307,7 +309,9 @@ A `Dispatcher` struct has methods `Create`, `Read`, `Update`, `Delete`, `Inspect
 
 ```go
 // Regression gate for the class invariant: every Dispatcher method must
-// include "kind" in its Send args. New methods MUST include the same arg.
+// include "kind" in its Send args.
+// IMPORTANT: add a new row to cases whenever a new method is added —
+// the test only gates methods explicitly listed here.
 func TestDispatcher_AllMethods_IncludeKind(t *testing.T) {
     req := Request{Name: "test-resource"} // illustrative; use your actual Request type
     cases := []struct {
@@ -322,7 +326,7 @@ func TestDispatcher_AllMethods_IncludeKind(t *testing.T) {
     }
     for _, tc := range cases {
         t.Run(tc.name, func(t *testing.T) {
-            spy := &spyClient{} // spyClient is a test double; implement lastArgs capture for your client type
+            spy := &spyClient{} // spyClient is a test double; implement lastArgs as map[string]string (or use a type assertion if map[string]any)
             d := &Dispatcher{client: spy, kind: "widget"}
             if err := tc.call(d); err != nil {
                 t.Fatalf("unexpected error: %v", err)

skills/test-driven-development/test-fixtures/narrow-regression/new-flow.md

@@ -3,8 +3,8 @@
 - **RED**: `TestSum_HandlesSingleElement` written, runs, FAILs.
 - **GREEN**: fix applied, test PASSES.
 - **Verify Regression Invariant**:
-  - Revert fix. Run `TestSum_HandlesSingleElement`. Must FAIL. ✓ FAILS.
-  - Restore fix. Must PASS. ✓ PASSES.
+  - Revert fix. Run `TestSum_HandlesSingleElement`. Must FAIL. [confirmed: FAILS]
+  - Restore fix. Must PASS. [confirmed: PASSES]
   - Proof pasted in PR body:
     ```
     With fix reverted: