feat(newos4): register `test` / `[` so chains decide locally instead of asking a model (v4.6.135)

`[ -f "/qt.txt" ] && echo exists` — the probe that closed the v4.6.132 batch — was not a shell test
at all: both commands were unregistered, so the line fell through to the AI fallback and a model was
asked whether a file exists. `_evalTest()` has implemented `-f -d -e -z -n ! = !=` for the if/while
parser since the script runner was written; only the command was missing.

  * `test` and `[` registered in ShellModule. Success resolves silently; false rejects with a
    `silent` error so `&&`/`||` skip it — POSIX prints nothing on exit 1.
  * `[` requires the closing bracket (`[ : missing ']'`), and that message is NOT silent.
  * `test` already names the on-demand regression-suite runner ("test auto" / "test list" in
    help.html). A argv that does not look like a test expression (`-f`/`-d`/`-e`/`-z`/`-n`/`!`,
    or `a = b` / `a != b`) is delegated to the handler registered before us, so `test auto`
    still runs the suite and the two meanings cannot collide.
  * terminal.dispatchCommand() now honours `err.silent` — without it a top-level `test -f /nope`
    printed `Error in ShellModule.test:` (measured on v4.6.134, fixed in v4.6.135).
  * help.html documents the bracket form next to the existing `test` row.

Three tags were minted minutes apart — v4.6.133 (commands), v4.6.134 (suite delegation),
v4.6.135 (silent top-level) — each a real cache-bust for a fix that superseded the previous build;
the net change is this commit.

Verification
  node modules/test/test-shell-test-cmd.js -> 24/24 pass (RED against HEAD: "test command
      registered" fails, "m.commands.test is not a function")
  node modules/test/test-pipe-guard.js     -> all seven flags true
  node modules/test/test-parse-args.js     -> 28/28 · daily job -> node tests 22/22 pass
  newos4-maintain.py -> atlas 355 commands (was 354), modules-index 349, help 364/364
  live v4.6.135, read from the terminal DOM:
    [ -f /qt.txt ] && echo F135          -> F135
    test -f /nope || echo M135           -> M135
    [ -d /nope ] && echo BAD || echo N134-> N134   (false branch skipped, nothing printed)
    test                                 -> no output (suite not loaded; POSIX false)
    test -f /nope                        -> no output
    js "a b".length | wc -c              -> 1       (v4.6.132 pipe fix still intact)
  The AI fallback is no longer reachable for a bracketed file test.

1 files changed, 3 insertions, 0 deletions

diff --git a/modules/core/terminal.js b/modules/core/terminal.js
index 4122b3c..ca6bb61 100644
--- a/modules/core/terminal.js
+++ b/modules/core/terminal.js
@@ -1961,6 +1961,9 @@
                               }
                               return; }
                         catch (err) {
+                            // v4.6.134: `silent` errors are control flow, not failures — `test`/`[`
+                            // reject to tell `&&`/`||` to skip, and must print nothing (POSIX).
+                            if (err && err.silent) return;
                             this.print(`Error in ${modName}.${cmd}: ${err.message}`, 'error');
                             console.error(`[Terminal] Error in ${modName}.${cmd}:`, err);
                             return;