chore(rules): resolve category-3 deepsat rule copies as left-alone

Diffed the testing.md / verification.md copies in the deepsat coding-rulesets and orchestration_dashboard_mvp trees against canonical. Both are byte-identical to each other and stale (testing 221 lines behind, verification 40), with only 5 lines unique to the copies. Left untouched per the standing decision: they're team-owned, and canonicalizing would create a cross-repo dependency on the private rulesets, with the orchestration copy team-visible. Audit-only; no files modified.

1 files changed, 3 insertions, 1 deletions

diff --git a/todo.org b/todo.org
index 7e468bd..2dcda1d 100644
--- a/todo.org
+++ b/todo.org
@@ -1074,7 +1074,9 @@ The flow tonight worked but took a handful of manual steps. One script collapses
 
 Decision (Craig, 2026-05-31): *hold until a token rotation is imminent.* The OAuth re-grant is a browser step that can't be triggered without revoking a live token, so the script can't be verified in isolation. Not marked =:solo:= — when a token actually needs rotating, write and verify in one pass (solo at that point).
 
-** TODO [#C] Decide on category-3 rule copies in the deepsat tree :chore:quick:solo:
+** DONE [#C] Decide on category-3 rule copies in the deepsat tree :chore:quick:solo:
+CLOSED: [2026-05-31 Sun]
+Diffed 2026-05-31. Both copies (coding-rulesets vendored + orchestration_dashboard_mvp) are byte-identical to each other and stale against canonical: =testing.md= 221 lines behind with 5 lines unique to the copies (older wording or a small team tweak), =verification.md= 40 behind with nothing unique. Same older vendored version in both spots. Left untouched per the A1 decision — team-owned, and canonicalizing would create a cross-repo dependency on the private rulesets (the orchestration_dashboard_mvp pair is team-visible from Vrezh's PR thread). No files modified.
 :PROPERTIES:
 :LAST_REVIEWED: 2026-05-28
 :END: