kaish-help 0.14.1

Composable help & instructions content for kaish — shared by the kernel, REPL, MCP server, and embedders
Documentation
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
//! The English fragment registry.
//!
//! Phase 1 seeded the composition surface with the [`Concept::Foundations`] spine
//! (the guarantees and the idioms that follow from them) plus a couple of
//! [`Concept::Model`] fragments. Phase 2 (light) adds the [`Concept::Syntax`]
//! reference sections, which are the single source for `content/en/syntax.md`
//! (a committed, drift-tested mirror). `LANGUAGE.md` stays hand-authored. See
//! `docs/composable-help.md`.
//!
//! Bodies are inline `&'static str` for now; when i18n lands they move to
//! per-locale files keyed by (concept, key, variant).

use crate::compose::{Audience, Concept, Depth, Fragment, Variant, DEFAULT_LOCALE, UNRANKED};

/// Shorthand for an inline English fragment (no section heading). Unranked by
/// default; the always-on onboarding spine attaches an importance rank with
/// [`Fragment::ranked`].
const fn en(
    concept: Concept,
    key: &'static str,
    variant: Variant,
    depth: Depth,
    audience: Option<Audience>,
    body: &'static str,
) -> Fragment {
    Fragment {
        concept,
        key,
        variant,
        depth,
        locale: DEFAULT_LOCALE,
        audience,
        rank: UNRANKED,
        title: None,
        body,
    }
}

/// Shorthand for a titled English `Syntax`-reference section. These render as
/// `## <title>` blocks in [`crate::compose::render_syntax_reference`], which is the
/// single source for `content/en/syntax.md`.
const fn syntax_section(key: &'static str, title: &'static str, body: &'static str) -> Fragment {
    Fragment {
        concept: Concept::Syntax,
        key,
        variant: Variant::Example,
        depth: Depth::Reference,
        locale: DEFAULT_LOCALE,
        audience: None,
        rank: UNRANKED,
        title: Some(title),
        body,
    }
}

/// The canonical English content set.
pub const FRAGMENTS: &[Fragment] = &[
    // ---- Model ---------------------------------------------------------------
    en(
        Concept::Model,
        "what",
        Variant::Rule,
        Depth::Summary,
        None,
        "kaish (会sh) is a Bourne-like shell for AI agents: familiar syntax, fewer \
         footguns, validated before execution. Builtins run in-process; external \
         commands run via `PATH`.",
    ),
    en(
        Concept::Model,
        "data-model",
        Variant::Rule,
        Depth::Summary,
        None,
        "Values can be structured — a list (`xs=[a b c]`) or a record (`u={k: v}`), not \
         only strings. Access is brackets-only (`${r[key]}`, `${xs[0]}`, never dots); \
         iterate with `$(values $c)` (elements/values) or `$(keys $c)` (indices/keys); \
         `fromjson` / `tojson` bridge real JSON text in and out. See `help syntax` → \
         Collections.",
    ),
    en(
        Concept::Model,
        "welcome",
        Variant::Rule,
        Depth::Summary,
        Some(Audience::Human),
        "Type `help` for topics, `help <tool>` for a specific builtin, and `exit` to quit.",
    ),
    // ---- Foundations: guarantees + the idioms that follow --------------------
    en(
        Concept::Foundations,
        "no-word-splitting",
        Variant::Rule,
        Depth::Summary,
        None,
        "**No word splitting.** `$VAR` is always a single value — a variable holding \
         spaces stays one argument. Use `split` when you actually want to split on \
         whitespace, a delimiter, or a regex.",
    )
    .ranked(0),
    en(
        Concept::Foundations,
        "no-word-splitting",
        Variant::Contrast,
        Depth::Reference,
        None,
        "Bash splits unquoted `$VAR` on `$IFS`; kaish never does, so you never have \
         to quote a variable just to keep it whole.",
    ),
    en(
        Concept::Foundations,
        "quote-to-join",
        Variant::Rule,
        Depth::Summary,
        None,
        "**Quote to join.** `$VAR`, `$(cmd)`, and globs are each a separate word \
         unless quoted — kaish never pastes adjacent unquoted tokens. To build one \
         word from text plus interpolation, wrap the whole thing in double quotes: \
         `\"$dir/file.txt\"`, `\"out-$(date +%s).log\"`.",
    )
    .ranked(1),
    en(
        Concept::Foundations,
        "quote-to-join",
        Variant::Contrast,
        Depth::Reference,
        None,
        "Bash pastes adjacent tokens, so bare `$dir/file` is one word. kaish keeps \
         them separate: bare `$dir/file` becomes two arguments, and a bare \
         interpolated redirect target (`> $dir/out`) is a parse error. Always quote \
         interpolated words — the same thing `shellcheck` (SC2086) asks for.",
    ),
    en(
        Concept::Foundations,
        "pipe-needs-capture",
        Variant::Rule,
        Depth::Summary,
        None,
        "**A compound statement can't feed a pipe.** `for`/`while`/`if`/`case` \
         can't sit left of `|` — `for f in a b; do echo $f; done | grep a` is a \
         parse error. Capture first, then pipe: \
         `out=\"$(for f in a b; do echo $f; done)\"; echo \"$out\" | grep a`.",
    )
    .ranked(3),
    en(
        Concept::Foundations,
        "structured-output",
        Variant::Rule,
        Depth::Summary,
        None,
        "**Structured output.** Every builtin can emit machine-readable data with \
         `--json` (`ls --json`, `ps --json`, `kaish-vars --json`).",
    )
    .ranked(8),
    en(
        Concept::Foundations,
        "structured-output",
        Variant::Example,
        Depth::Reference,
        None,
        "```\nls --json | jq '.[].name'\n```",
    ),
    en(
        Concept::Foundations,
        "newline-split",
        Variant::Rule,
        Depth::Summary,
        None,
        "**Newline-split substitution.** `for x in $(cmd)` splits on newlines only — \
         one iteration per line; whitespace within a line never splits.",
    )
    .ranked(5),
    en(
        Concept::Foundations,
        "structured-substitution",
        Variant::Rule,
        Depth::Summary,
        None,
        "`$(cmd)` carries structured data: `for i in $(seq 1 5)` iterates five values, \
         not split text. Enumerate a collection the same way — `for x in $(values $c)` \
         (list elements / record values) or `for k in $(keys $c)` (list indices / record \
         keys). A bare `for x in $c` is an error: wrap the collection in `$(...)`.",
    )
    .ranked(4),
    en(
        Concept::Foundations,
        "glob-strict",
        Variant::Rule,
        Depth::Summary,
        None,
        "**Strict globs.** `*.txt` expands to matching files; zero matches is an \
         error, not a silent pass-through.",
    )
    .ranked(6),
    en(
        Concept::Foundations,
        "bracket-test-not-a-command",
        Variant::Rule,
        Depth::Summary,
        None,
        "**`[ … ]` is not a command.** No `[` builtin exists — \
         `if [ -f file ]; then` fails on the first flag. Use `[[ … ]]` (validated, \
         richer tests) or `test`: `if [[ -f file ]]; then`, \
         `test -f file && echo yes`.",
    )
    .ranked(7),
    en(
        Concept::Foundations,
        "pre-validation",
        Variant::Rule,
        Depth::Summary,
        None,
        "**Pre-validation.** kaish validates the whole command before running it — \
         syntax errors are caught up front, so a command never half-runs.",
    )
    .ranked(9),
    en(
        Concept::Foundations,
        "crash-not-corrupt",
        Variant::Rule,
        Depth::Summary,
        None,
        "**Fail loud, not silent.** kaish prefers to error over corrupting data; \
         `set -o trash` snapshots what a delete or overwrite would destroy, so \
         the mistake is recoverable.",
    )
    .ranked(10),
    en(
        Concept::Foundations,
        "boolean-like-yes-no",
        Variant::Rule,
        Depth::Summary,
        None,
        "**Bare `yes`/`no` are lexer errors.** They read as ambiguous booleans — so \
         does `TRUE`/`Yes`/any non-lowercase `true`/`false` — so `echo yes` fails \
         before it runs. Quote them or use `true`/`false`. `on`/`off` are \
         unaffected.",
    )
    .ranked(11),
    en(
        Concept::Foundations,
        "json-orchestration",
        Variant::Rule,
        Depth::Summary,
        Some(Audience::Agent),
        "When orchestrating tools, prefer `--json` piped through `jq` — consuming \
         structured data beats scraping text output.",
    )
    .ranked(12),
    en(
        Concept::Foundations,
        "collection-literals",
        Variant::Rule,
        Depth::Summary,
        None,
        "**Collection literals.** Lists/records have native syntax — `xs=[a b c]`, \
         `u={k: v}` — no `fromjson` needed. `push xs v` appends in place (like \
         `read`/`unset`, it takes the bareword NAME, not `$xs`); `...$xs` spread \
         flattens into a new list — a bare `$xs` nests as one element instead.",
    )
    .ranked(13),
    en(
        Concept::Foundations,
        "collection-literals",
        Variant::Contrast,
        Depth::Reference,
        None,
        "Collections are brackets-only, never dots: `${u.name}` is a loud parse \
         error naming the fix (`${u[name]}`) — the `Ident` token allows `.` for \
         other uses (filenames), so this can't be caught silently.",
    ),
    // ---- Overlay: opt-in, excluded from every default Recipe -----------------
    // See Concept::Overlay's doc comment for why this isn't in the Foundations
    // spine. Compose it in explicitly: `Recipe::agent_onboarding().with_overlay()`.
    en(
        Concept::Overlay,
        "overlay-mode",
        Variant::Rule,
        Depth::Summary,
        Some(Audience::Agent),
        "**Overlay mode** (opt-in: `--overlay` flag or `KernelConfig::with_overlay`). \
         All writes go into a virtual in-memory layer; the real filesystem is never \
         touched until you explicitly commit. Use `kaish-vfs` to inspect and finalize \
         the transaction: `kaish-vfs status` (dirty flag + counts), `kaish-vfs diff` \
         (unified diff), `kaish-vfs commit` (write to real files), \
         `kaish-vfs reset [path]` (discard edits). \
         **Fresh-kernel-per-call rule**: when an embedder runs a fresh kernel per \
         `execute()` call (the common pattern), each call gets a fresh overlay \
         transaction. `kaish-vfs commit` MUST run in the same call as the writes — if \
         you commit in a later call the transaction from the write call was already \
         discarded.",
    ),
    // ---- Syntax reference (single source for content/en/syntax.md) -----------
    syntax_section(
        "variables",
        "Variables",
        r#"```sh
NAME="value"              # assignment (no spaces around =)
local NAME="value"        # local scope
COUNT=42                  # integer
PI=3.14159                # float
ENABLED=true              # boolean (only true/false)
```"#,
    ),
    syntax_section(
        "expansion",
        "Expansion",
        r#"```sh
$VAR                      # simple
${VAR}                    # braced
${VAR:-default}           # default if unset/empty
${#VAR}                   # string length
$0 $1 $@ $#              # script name, args, all args, count
$?                        # last exit code (0-255)
$$ ${$}                   # kaish session id — see note below
```

**`$$` is a kaish-internal session identifier**, not the OS PID. It's a
monotonic `u64` counter (starts at 1) assigned at kernel construction;
forks/subshells inherit the parent's value. This is an intentional
divergence from bash — kaish runs embedded inside long-lived host
processes, where the host PID is meaningless to the script."#,
    ),
    syntax_section(
        "collections",
        "Collections (lists & records)",
        r#"```sh
# CONSTRUCTION — native literal syntax, no fromjson needed. Commas optional.
xs=[apple banana cherry]  # list — space-separated, like shell words
nums=[1 2 3]               # ≡ [1, 2, 3]
u={name: amy, role: maintainer}   # record — bareword keys
compact={port:8080}        # colon may be spaced or unspaced
r={"content-type": x}      # quoted key for anything that isn't a bareword
d={"$k": x}                # double-quoted keys interpolate; '$k' stays literal
nested={tags: [a b], meta: {active: true}}   # nesting works both ways

# SPREAD (...) flattens; a bare $var nests as ONE element instead:
xs=[1 2]
ys=[0 $xs 4]                # [0,[1,2],4]  — nests
new=[...$xs date]           # [1,2,"date"] — flattens

# Values are also structured JSON — fromjson/tojson bridge real JSON text:
u=$(fromjson '{"name":"amy","tags":["rust","shell"]}')
xs=$(fromjson '[10,20,30]')

# READ ACCESS — brackets only, never dots. Bad access is a loud error.
${u[name]}                # record key (bareword = literal key)
${u[$k]}                  # dynamic key ($var)
${xs[0]}   ${xs[-1]}      # list index; negative counts from the end
${xs[0:2]}                # slice (end-exclusive) → a list
${s[0:5]}   ${s[-3:]}     # SAME slice on a string → characters, not bytes
${u[tags][0]}             # nested path
${#xs}   ${#u}            # length: list elements / record keys
${u.name}                 # error — brackets only, use ${u[name]}
${s:0:5}                  # error — that is bash; use ${s[0:5]}

# ENUMERATE — always wrap the collection in $(keys ...) or $(values ...).
# A bare `for x in $xs` is an ERROR (E012): there is no word splitting.
# keys → indices (list) / keys (record).  values → elements (list) / values (record).

for x in $(values $xs); do echo $x; done          # each list element: 10 20 30
for i in $(keys $xs);   do echo $i; done          # each list index:   0 1 2
for k in $(keys $u);    do echo $k; done          # each record key:   name tags
for v in $(values $u);  do echo $v; done          # each record value

# key + value together — index the record by the loop key:
for k in $(keys $u); do echo "$k = ${u[$k]}"; done

# nested — a subscript access is still a VarRef, so it needs $() too:
for t in $(values ${u[tags]}); do echo $t; done   # rust shell

# filter while iterating — test each element, act on the matches:
for x in $(values $xs); do
  if [[ $x -gt 15 ]]; then echo "big: $x"; fi      # big: 20  big: 30
done

# MEMBERSHIP — RHS must be a collection (see Test Expressions):
if [[ rust in $(values ${u[tags]}) ]]; then echo "has it"; fi   # element present?
if [[ name in $u ]]; then echo "has it"; fi                     # record has key?
if [[ 1 in $(keys $xs) ]]; then echo "in bounds"; fi            # index in bounds?

# SHAPE GUARD — an API sometimes returns a list, sometimes a record; check
# before committing to keys/values/for. typeof + [[ -list ]] / [[ -record ]]:
if [[ -record $data ]]; then
  for k in $(keys $data); do echo $k; done
elif [[ -list $data ]]; then
  for x in $(values $data); do echo $x; done
fi

tojson $u                 # serialize back to JSON text (--pretty to indent)
# A stream of many documents (JSONL/NDJSON) is fromjsonl/tojsonl, not fromjson/tojson.

# ASSIGNMENT — the same bracket paths write, in place, no spaces around `=`.
# No autovivification — every intermediate must already exist with the right
# shape; the ONLY thing a path-set may create is the final record key.
xs[0]=9                   # in-bounds index update (negative index works too)
u[host]=localhost         # record key: insert or update
s[web][port]=9000         # deep path
xs[9]=x                   # error — index out of bounds (push grows lists)
s[api][port]=1            # error — no `api` key (no autoviv; init it first)
user.email=x              # error — brackets only, use `user[email]=x`

# push appends to a LIST in place — takes the NAME (like read/unset), a
# top-level name or a bracket path; same lvalue rules as assignment (no
# autoviv on intermediates, leaf must already be a list)
push xs date               # xs is now [...,"date"]
push xs $rec               # values push as typed Values, not stringified text
push services[web][tags] canary   # bracket-path target
```"#,
    ),
    syntax_section(
        "paths",
        "Paths",
        r#"```sh
/usr/bin/foo              # absolute
../parent/file            # relative with ..
./script.sh               # dot-slash (explicit relative)
~/src/project             # tilde expands to $HOME
cd                        # bare cd goes to $HOME
cd -                      # previous directory
```"#,
    ),
    syntax_section(
        "quoting",
        "Quoting",
        r#"```sh
"hello $NAME"             # double quotes — interpolation
"literal \$X"             # escape $ to prevent expansion
'hello $NAME'             # single quotes — literal, no interpolation

# Quote to JOIN text with interpolation — kaish does not paste adjacent
# unquoted tokens into one word (no implicit concatenation):
"$dir/file.txt"           # one path
"out-$(date +%s).log"     # one filename (text + command substitution)
echo "/tmp/$(id -u).sock" # one argument

# Unquoted text adjacent to an expansion is a PARSE ERROR (quote the word):
echo $dir/file.txt        # error — quote "$dir/file.txt"
echo /tmp/$(id -u).sock   # error — quote "/tmp/$(id -u).sock"
cmd > $dir/out.txt        # error — quote "$dir/out.txt"
# (single-token words like file.txt or v1.2.3 are fine unquoted)
```"#,
    ),
    syntax_section(
        "pipes-redirects",
        "Pipes & Redirects",
        r#"```sh
cmd1 | cmd2 | cmd3        # pipe stdout
cmd > file                # write stdout
cmd >> file               # append
cmd < file                # stdin from file
cmd 2> file               # stderr
cmd &> file               # stdout + stderr
cmd 2>&1                  # merge stderr into stdout

cat <<EOF                 # here-doc
content with $VAR
EOF

jq -r '.name' <<< "$R"    # here-string — feed expanded word to stdin

cmd > "$dir/out.log"      # quote interpolated targets — one word required
cat < "$(find-config)"    # command substitution works in a quoted target
```

A redirect target is a single word: quote it when it interpolates
(`> "$dir/f"`, not `> $dir/f`). Bare command substitution as the whole
target (`> $(cmd)`) works; bare text-plus-interpolation does not.

One stdin source per command: `<`, `<<`, and `<<<` cannot be combined.
jq is built-in (native jaq), so `<<<` + jq replaces `echo … | jq`
without a subprocess. jq also accepts real jq's `--arg NAME VALUE`,
`--argjson NAME VALUE`, and `-n` / `--null-input` flags for binding
kaish variables directly into the filter."#,
    ),
    syntax_section(
        "operators",
        "Operators",
        r#"```sh
cmd1 && cmd2              # cmd2 if cmd1 succeeds
cmd1 || cmd2              # cmd2 if cmd1 fails
```"#,
    ),
    syntax_section(
        "test-expressions",
        "Test Expressions",
        r#"```sh
# File: -f (file) -d (dir) -e (exists) -r (readable) -w (writable) -x (executable)
# String: -z (empty) -n (non-empty) == != =~ (regex) !~ (not regex)
# Shape guard: -list -record — the value's shape, not a path stat. A
#   defined-but-wrong-shaped value is false; a bare unset $var errors (like
#   -z), so a typo isn't silently false. Pairs with the typeof builtin.
# Numeric: -gt -lt -ge -le
# Logic: && || !
# Membership: in (list→element, record→key) / not in — RHS must be a collection

[[ -f config.json && -n $NAME ]]
[[ $N -gt 5 ]]
[[ $s =~ "\.rs$" ]]
if [[ banana in $fruits ]]; then echo "have one"; fi
if [[ tmp not in $services ]]; then echo "not running"; fi
[[ -list $x ]]
[[ -record $x ]]
```"#,
    ),
    syntax_section(
        "control-flow",
        "Control Flow",
        r#"```sh
if [[ -f file ]]; then echo "found"; elif [[ -d dir ]]; then echo "dir"; else echo "none"; fi

for item in "one" "two"; do echo $item; done
for f in *.txt; do cat "$f"; done
for x in $(values $list); do echo $x; done            # a collection's elements/values
for k in $(keys $rec); do echo "$k=${rec[$k]}"; done  # a record's keys (bare $rec is E012)

while [[ $N -gt 0 ]]; do N=$((N - 1)); done

case $VAR in
    hello) echo "matched" ;;
    *.rs) echo "Rust file" ;;
    *) echo "default" ;;
esac

break; continue; return [N]; exit [N]
```"#,
    ),
    syntax_section(
        "command-substitution",
        "Command Substitution",
        r#"```sh
NOW=$(date)

# In for-loops, $(cmd) splits on newlines (only):
for line in $(cat file); do echo $line; done   # per-line iteration
for x in $(echo "a b c"); do echo $x; done     # one iteration (no \n)

# Whitespace splitting needs explicit split:
for x in $(split "a b c"); do echo $x; done

# Builtins that emit .data (seq, jq, cut, find, glob) iterate per element:
for i in $(seq 1 5); do echo $i; done

# Outside for-loops, $(cmd) is one value:
R=$(printf 'a\nb')                # R is "a\nb"
echo "got: $(printf 'x\ny')"      # one echo, newline preserved

# A $(...) body takes the full statement grammar: &&/|| chains, ; sequences,
# multi-line bodies, and # comments (not just a single pipeline):
H=$(cd "$repo" && git rev-parse HEAD)
B=$(printf a; printf b)           # "ab"

# kaish-last prints the previous command's .data (or its stdout) as text:
seq 1 5
kaish-last | jq '.[2]'            # → 3
seq 1 5
DATA=$(kaish-last)                # capture for later use
```"#,
    ),
    syntax_section(
        "arithmetic",
        "Arithmetic",
        r#"```sh
X=$((5 + 3))              # 8
Y=$((X * 2))              # 16
# Operators: + - * / % > < >= <= == !=
# Comparisons return 1/0
```"#,
    ),
    syntax_section(
        "functions",
        "Functions",
        r#"```sh
greet() { echo "Hello, $1!"; }
function greet { echo "Hello, $1!"; }
greet "Amy"
```"#,
    ),
    syntax_section(
        "glob-expansion",
        "Glob Expansion",
        r#"```sh
ls *.txt                  # expands to matching .txt files
cat src/*.rs              # path-prefixed globs work
for f in *.json; do       # iterates over matches
    jq ".name" "$f"
done
set +o glob               # disable bare glob expansion
set -o glob               # re-enable (on by default)
```

Zero matches is an error (exit code 1). The `glob` builtin receives its
pattern as written — `glob **/*.rs` needs no quotes, takes multiple patterns,
and adds `--exclude`, `--ftype`, and depth control."#,
    ),
    syntax_section(
        "regex",
        "Regex (grep, sed, awk)",
        r#"```sh
# ERE (egrep-style) everywhere: a|b  (…)  x+ y? z{2,5}  [a-z]  ^…$
grep 'error|warn' log.txt           # alternation — one call, many terms
sed -E 's/v([0-9]+)\.[0-9]+/\1/'    # (…) capture; \1 \2 in the REPLACEMENT
awk '/^(GET|POST) /' access.log     # same engine in all three

# GNU BRE spellings are accepted too — \| \(…\) \{n,m\} \+ \? rewrite to ERE:
grep 'error\|warn' log.txt          # ≡ error|warn
sed 's/\(a\)\(b\)/\2\1/'            # ≡ s/(a)(b)/\2\1/

# A literal | + ? ( ) { }: bracket class, or strict-ERE mode
grep '[|]' f                        # literal pipe (works in all three)
grep -E 'a\|b' f                    # -E / -r (grep, sed): backslashed meta = literal
grep -F 'a|b' f                     # -F: fixed string, nothing is a metachar

grep '\d+\.\w\b' f                  # \d \w \s \b \. work; \< \> too
sed 's/(a)\1/x/'                    # ERROR — no backreference IN a pattern
```"#,
    ),
    syntax_section(
        "shell-options",
        "Shell Options",
        r#"```sh
set -e                    # exit on first error
set -o trash              # move rm'd / overwritten files to Trash
set -o glob               # enable bare glob expansion (on by default)
set +o trash              # disable trash
set +o glob               # disable bare glob expansion
```

Env var: `KAISH_TRASH=1` enables trash at startup.

`set` ignores an unknown `-o` name and exits **0**. `set -o approvals` and
`set -o latch` are retired spellings — from the removed approval subsystem
and the confirmation latch — and turn nothing on.

**Trash:** `rm` and a truncating overwrite (`cp`, `dd`, `mv`, `patch`,
`sed -i`, `tee`, `write`) snapshot the prior content under `set -o trash`
before they run, so the mistake is recoverable from Trash; `tee -a` append,
new files, and `patch --dry-run` have no prior content to snapshot. Files
<= 10MB and directories always trash; `/tmp`, `/v/*` are excluded. A
**symlink** is the exception: `rm` unlinks the link itself rather than
trashing its target, which is trivially recreatable while the target may
not be. If trash fails, the op errors — no silent fallthrough to a
destructive delete/overwrite. Configure threshold: `kaish-trash config
max-size <bytes>`.

`kaish-trash empty --confirm` is the one operation that always asks — it
discards the recovery net itself. A bare `kaish-trash empty` refuses and
names the flag; the flag carries no token, records nothing, and no session
setting disables the ask."#,
    ),
    syntax_section(
        "error-handling",
        "Error Handling",
        r#"```sh
set -e                    # exit on first error
cmd || { echo "failed"; exit 1; }
source utils.kai          # load script (shared scope)
```"#,
    ),
    syntax_section(
        "aliases-background-jobs",
        "Aliases & Background Jobs",
        r#"```sh
alias ll='ls -la'         # define (first word only, not in pipelines)
unalias ll                # remove

slow-task &               # run in background
jobs                      # list jobs
wait %1 %2                # wait for specific jobs
```"#,
    ),
];