docs(workflows): fix stray escape sequence in --json redirect comments

The redirect helper's docstring and its test comment wrote ``print``\s,
which renders as "print\s" rather than "prints". Replace with plain
"prints".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: doquanghuy

src/specify_cli/__init__.py

@@ -2761,7 +2761,7 @@ def _stdout_to_stderr_when(active: bool):
 
     Suppressing the banner and the step-start callback is not enough to
     keep a ``--json`` stream clean: individual steps may still write to
-    stdout while the engine runs — the gate step ``print``\\s its prompt,
+    stdout while the engine runs — the gate step prints its prompt,
     and the prompt step runs a subprocess that inherits the process's
     stdout file descriptor. Either would corrupt the single JSON object.
 

tests/test_workflows.py

@@ -3147,7 +3147,7 @@ def test_resume_json(self, project_dir):
 
     def test_json_redirect_keeps_stdout_clean(self, capfd):
         # While a workflow runs under --json, steps can still write to stdout:
-        # the gate step ``print``\s its prompt and the prompt step runs a
+        # the gate step prints its prompt and the prompt step runs a
         # subprocess that inherits the stdout fd. Both must be redirected to
         # stderr so the JSON object on stdout stays parseable. capfd captures
         # at the file-descriptor level, so it sees the subprocess output too.