diff --git a/TODO-1.6.md b/TODO-1.6.md
index 30771e8..2ccfcdb 100644
--- a/TODO-1.6.md
+++ b/TODO-1.6.md
@@ -26,10 +26,19 @@ the official docs (code.claude.com/docs/en/skills.md, plugins.md):
         command, so coexistence is safe.
   - [x] `argument-hint` carries over as-is; `$ARGUMENTS` substitution unchanged —
         **done 1.6.0** (save/recall/reflect).
-- [ ] Verify a migrated build installs cleanly on desktop **and** in a CoWork session
-      before deleting `commands/` (deleting the legacy dir is a 2.0 item —
-      see `ROADMAP-2.0.md`; in 1.6 both may coexist). *(1.6.0 artifact built —
-      operator install test pending.)*
+- [x] Verify a migrated build installs cleanly on desktop **and** in a CoWork session
+      before deleting `commands/` — **verified 2026-07-28** on the baked 1.6.0-jason
+      artifact, all four checks pass: (1) all eight skills register and take
+      precedence over the coexisting legacy commands; (2) `allowed-tools` present on
+      load/health/recall; (3) `disable-model-invocation` confirmed on exactly
+      sweep+triage; (4) CoWork `$ECHO` fallback resolves via
+      `/sessions/*/mnt/.remote-plugins/*` and executes. **2.0's `commands/` deletion
+      is unblocked.** *Known caveat, accepted (CLI is not a normal operating surface
+      here): the `allowed-tools` globs match the literal script names
+      (`*echo.py*`/`*vault_lint.py*`) while the bodies invoke via the resolved
+      `"$ECHO"` variable — if the Claude Code CLI matches permissions before
+      variable expansion, those skills could still prompt there. Re-confirm on the
+      CLI if that surface ever matters.*
 
 ## 2. plugin.json completeness (from the old MAINTENANCE checklist)