Release RelayX v0.1.16 colorized UX

Author: RedteamNotes

README.md

@@ -206,8 +206,9 @@ relayx -q paths examples/tutorial/sample-result.json -b
 relayx -q bundle -r examples/tutorial/sample-result.json -d /tmp/relayx-tutorial-bundle
 ```
 
-Read the full runbook in [docs/TUTORIAL.md](docs/TUTORIAL.md). The tutorial
-fixtures live in [examples/tutorial](examples/tutorial).
+Read the full runbook in [docs/TUTORIAL.md](docs/TUTORIAL.md), or use the
+Chinese version in [docs/TUTORIAL.zh-CN.md](docs/TUTORIAL.zh-CN.md). The
+tutorial fixtures live in [examples/tutorial](examples/tutorial).
 Authorized AD/IIS/AD CS/MSSQL lab expectations are documented in
 [docs/INTEGRATION_TESTS.md](docs/INTEGRATION_TESTS.md).
 
@@ -303,14 +304,15 @@ guardrails.
 ## Operator Console And Completion
 
 RelayX includes a local operator console for repeated analysis on the same
-result and path. It is not a C2 client and does not start listeners, pivot
-sessions, source triggers, or live relay adapters; it calls the same guarded
-CLI handlers with remembered context.
+result and path. It keeps result, path, OPSEC policy, and scope context in the
+prompt, then calls the same guarded CLI handlers you already use in scripted
+workflows.
 
 ```bash
 relayx console --result result.json --path-id PX-0001 --opsec-policy strict
 relayx completion zsh > relayx.zsh
 relayx help getting-started
+relayx --no-color help run
 ```
 
 Inside the console, use commands such as `use result <file>`, `use path

docs/CLI.md

@@ -7,7 +7,8 @@ for grouped command help, short-option documentation, shell completion, and
 quality-gate drift checks.
 
 For a complete end-to-end offline walkthrough, use
-[`docs/TUTORIAL.md`](TUTORIAL.md) with the fixtures in
+[`docs/TUTORIAL.md`](TUTORIAL.md) or
+[`docs/TUTORIAL.zh-CN.md`](TUTORIAL.zh-CN.md) with the fixtures in
 [`examples/tutorial`](../examples/tutorial).
 Authorized AD/IIS/AD CS/MSSQL integration-test expectations are documented in
 [`docs/INTEGRATION_TESTS.md`](INTEGRATION_TESTS.md).
@@ -75,15 +76,15 @@ Next steps
 ## Operator Console
 
 `relayx console` provides a local, single-process operator shell for repeated
-work on the same result, path, OPSEC policy, and scope. It is inspired by
-mature operator consoles, but it is not a C2 runtime: there is no server-client
-split, no listener start, no pivot-session operation, no source-side trigger
-execution, and no live relay adapter registration.
+work on the same result, path, OPSEC policy, and scope. It keeps the current
+operator context visible in the prompt and reuses the same RelayX CLI handlers
+and guardrails as scripted workflows.
 
 ```bash
 relayx console
 relayx console --result examples/tutorial/sample-result.json --path-id PX-0001 --opsec-policy strict
 relayx console --script console.txt
+relayx --no-color console --result examples/tutorial/sample-result.json
 ```
 
 The prompt reflects context:
@@ -138,6 +139,10 @@ relayx completion fish > relayx.fish
 Completion only suggests syntax. It does not weaken authorization, OPSEC,
 scope, audit, or adapter checks.
 
+ANSI color is enabled by default for human-readable curated help and console
+output. Use `--no-color` or the `NO_COLOR` environment variable for plain text.
+Machine-readable output and generated completion scripts are never colorized.
+
 ## Short Options
 
 RelayX exposes short aliases for high-use options. Long options remain the

docs/README.zh-CN.md

@@ -190,7 +190,8 @@ relayx -q paths examples/tutorial/sample-result.json -b
 relayx -q bundle -r examples/tutorial/sample-result.json -d /tmp/relayx-tutorial-bundle
 ```
 
-完整 runbook 见 [docs/TUTORIAL.md](TUTORIAL.md)。示例 fixture 位于
+完整英文 runbook 见 [docs/TUTORIAL.md](TUTORIAL.md)，中文版本见
+[docs/TUTORIAL.zh-CN.md](TUTORIAL.zh-CN.md)。示例 fixture 位于
 [examples/tutorial](../examples/tutorial)。
 授权 AD/IIS/AD CS/MSSQL lab 的 integration-test 期望见
 [docs/INTEGRATION_TESTS.md](INTEGRATION_TESTS.md)。
@@ -286,14 +287,14 @@ relayx quality-gate -C . -f json -o relayx-quality-gate.json
 ## Operator Console 与 Completion
 
 `relayx console` 是本地单进程 operator console，用来在同一个 result、path、
-OPSEC policy 和 scope 上重复分析。它不是 C2 client，不启动 listener、pivot
-session、source trigger 或 live relay adapter；console 命令仍调用同一套 CLI
-handler 和 guardrail。
+OPSEC policy 和 scope 上重复分析。它会在 prompt 中显示当前上下文，并调用与
+脚本化 workflow 相同的 CLI handler 和 guardrail。
 
 ```bash
 relayx console --result result.json --path-id PX-0001 --opsec-policy strict
 relayx completion zsh > relayx.zsh
 relayx help getting-started
+relayx --no-color help run
 ```
 
 console 内可使用 `use result <file>`、`use path PX-0001`、`set opsec-policy

docs/TUTORIAL.md

@@ -72,13 +72,14 @@ relayx -q schema validate -k result examples/tutorial/baseline-result.json
 
 The expected validation result is `valid: true` with zero errors.
 
-You can also use `relayx console`, the local operator console, for repeated work on the same
-result. The console remembers selected result, path, OPSEC policy, and scope;
-it still calls the same CLI handlers and does not start listeners, pivots,
-source triggers, or live relay adapters.
+You can also use `relayx console`, the local operator console, for repeated
+work on the same result. The console remembers selected result, path, OPSEC
+policy, and scope, then calls the same guarded CLI handlers used by scripted
+workflows.
 
 ```bash
 relayx -q console --result examples/tutorial/sample-result.json --path-id PX-0001 --opsec-policy strict
+relayx --no-color -q console --result examples/tutorial/sample-result.json
 ```
 
 Example console commands:
@@ -174,8 +175,7 @@ relayx -q schema validate -k route-report /tmp/relayx-routes.json
 
 Route and pivot awareness is model-driven. RelayX uses source metadata such as
 `session`, `segment`, `subnets`, and structured `route_hops` to explain likely
-reachability and route risk. It does not open Ligolo, Sliver, SOCKS,
-tun2socks, or port-forward sessions.
+reachability, route constraints, and route risk.
 
 In an authorized lab or assessment window, you can add a direct TCP observation
 without opening a pivot session: