fix(docs): resolve markdownlint regressions

This commit is contained in:
Vincent Koc
2026-03-22 11:54:11 -07:00
parent 1f93a99f47
commit 6d9d9319b2
2 changed files with 8 additions and 5 deletions

View File

@@ -43,7 +43,7 @@ export default definePluginEntry({
});
```
### Options
### Channel entry options
| Field | Type | Required | Default |
| -------------- | ---------------------------------------------------------------- | -------- | ------------------- |

View File

@@ -179,14 +179,14 @@ Long options are validated fail-closed in safe-bin mode: unknown flags and ambig
abbreviations are rejected.
Denied flags by safe-bin profile:
[//]: # "SAFE_BIN_DENIED_FLAGS:START"
<!-- SAFE_BIN_DENIED_FLAGS:START -->
- `grep`: `--dereference-recursive`, `--directories`, `--exclude-from`, `--file`, `--recursive`, `-R`, `-d`, `-f`, `-r`
- `jq`: `--argfile`, `--from-file`, `--library-path`, `--rawfile`, `--slurpfile`, `-L`, `-f`
- `sort`: `--compress-program`, `--files0-from`, `--output`, `--random-source`, `--temporary-directory`, `-T`, `-o`
- `wc`: `--files0-from`
[//]: # "SAFE_BIN_DENIED_FLAGS:END"
<!-- SAFE_BIN_DENIED_FLAGS:END -->
Safe bins also force argv tokens to be treated as **literal text** at execution time (no globbing
and no `$VARS` expansion) for stdin-only segments, so patterns like `*` or `$HOME/...` cannot be
@@ -216,9 +216,12 @@ multiplexer cannot be safely unwrapped, no allowlist entry is persisted automati
If you allowlist interpreters like `python3` or `node`, prefer `tools.exec.strictInlineEval=true` so inline eval still requires an explicit approval.
Default safe bins:
[//]: # "SAFE_BIN_DEFAULTS:START"
<!-- SAFE_BIN_DEFAULTS:START -->
`cut`, `uniq`, `head`, `tail`, `tr`, `wc`
[//]: # "SAFE_BIN_DEFAULTS:END"
<!-- SAFE_BIN_DEFAULTS:END -->
`grep` and `sort` are not in the default list. If you opt in, keep explicit allowlist entries for
their non-stdin workflows.