chore(todo): close add-tests audit items (1 fixed, 1 moot)

1 files changed, 6 insertions, 12 deletions

diff --git a/todo.org b/todo.org
index 528019c..010fc20 100644
--- a/todo.org
+++ b/todo.org
@@ -787,8 +787,8 @@ Each item below is a one-line summary of a sub-TODO further down. Tick the box w
 - [ ] [#B] =start-work=: claim-before-justify rollback risk
 
 **** Tests / TDD
-- [ ] [#B] =add-tests=: fix missing =typescript-testing.md= reference or add ruleset
-- [ ] [#B] =add-tests=: explicit exceptions to "all three categories per function"
+- [X] [#B] =add-tests=: fix missing =typescript-testing.md= reference or add ruleset (moot — ruleset now exists)
+- [X] [#B] =add-tests=: explicit exceptions to "all three categories per function"
 
 **** Debugging / RCA
 - [X] [#B] =debug=: capture environment + recent-change context before hypotheses
@@ -1000,19 +1000,13 @@ then says rolling back is required if justification fails. Consider moving
 claiming after Gate 1 for personal todo tasks, or make the rollback steps
 explicit per tracker with stored prior state.
 
-*** TODO [#A] =add-tests=: fix missing =typescript-testing.md= reference or add the ruleset
+*** 2026-05-22 Fri @ 14:28:41 -0500 Verified add-tests typescript-testing.md reference resolves (moot)
 
-Phase 3 references =typescript-testing.md=, but this repo currently has Python
-and Elisp testing rules only. Either add the TypeScript ruleset or change the
-skill to discover project-local JS/TS testing conventions instead of pointing
-to a missing file.
+Resolved since the audit: =languages/typescript/claude/rules/typescript-testing.md= now exists, and =add-tests/SKILL.md:68= references it by bare filename, the same way it references =python-testing.md= (both get copied into a project's =.claude/rules/=). The "missing file" premise no longer holds. No edit needed.
 
-*** TODO [#A] =add-tests=: add explicit exceptions to "all three categories per function"
+*** 2026-05-22 Fri @ 14:28:41 -0500 Added a category-exception protocol to add-tests
 
-The Normal/Boundary/Error rule is useful, but some functions are pure adapters,
-generated code, tiny wrappers, or framework glue. Add an exception protocol:
-state why a category does not apply, and cover the behavior at the integration
-or E2E level when unit categories would test framework behavior.
+Added an exception note to step 7 (proposal) in =add-tests/SKILL.md=: pure adapters, generated code, tiny pass-through wrappers, and framework glue may skip a category that would only re-test the framework, but the skip must be stated and justified in the plan and the behavior covered at integration/E2E level — never a silent omission. Step 12 (write) now points back to "honor documented category exceptions."
 
 *** 2026-05-22 Fri @ 14:25:37 -0500 Added environment + recent-change capture to debug Phase 1