diff --git a/docs/api/target-verification.md b/docs/api/target-verification.md
index 6a6cf70..589393e 100644
--- a/docs/api/target-verification.md
+++ b/docs/api/target-verification.md
@@ -21,7 +21,7 @@ This note records the current release-facing local verification boundary for Bit
 | --- | --- | --- | --- | --- | --- |
 | `src` compile check | verified | verified | verified | verified | not locally verified |
 | `src-async` compile check | verified | verified | verified | verified | not locally verified |
-| `moon test` | verified in current local environment | not separately re-run | not separately re-run | not separately re-run | not run |
+| `moon test` | verified in current local environment | verified | not separately re-run | not separately re-run | not run |
 | `moon test src-async` | verified | verified | verified | verified | not run |
 
 ### Explanation
@@ -30,6 +30,7 @@ Detailed rules explaining key parameters and behaviors
 
 - `verified` here means a local verification command was re-run successfully in the current environment.
 - `not locally verified` means the release should not imply fresh local confirmation even if the package is still designed for that target.
+- The root `moon test` line now has fresh local evidence on both `native` and `js` in this environment.
 - `llvm` is currently experimental in practice for this release context and did not complete local verification in this environment.
 - `src-async` now has fresh local test evidence on `native`, `js`, `wasm`, and `wasm-gc`, so async target notes may rely on more than compile-only confirmation for those targets.
 - `wasm` now has fresh local async test evidence as well as compile confirmation, and should be distinguished from the earlier state where only `wasm-gc` and `js` had been explicitly re-confirmed.
@@ -41,6 +42,7 @@ The current local verification evidence for this note is based on commands such
 
 ```text
 moon test
+moon test --target js
 moon check --target native
 moon check --target js
 moon check --target wasm