docs: sort the top-level directories into five sections by what the reader wants
Every docs directory moves under 1-getting-started, 2-handbook, 4-implementation or 5-project; the options reference (section 3) comes from the website and has no directory here. trust-boundary stays whole under the handbook for now. web-ui, swarm and tools split between handbook and implementation, and the command-line references move to 2-handbook/reference. Links, path references in code and nix, and the docs index follow the moves; no page content changes.
This commit is contained in:
parent
53ccbcb4b3
commit
6739bb903d
1 changed files with 736 additions and 701 deletions
|
|
@ -73,7 +73,7 @@ pub fn builtin_tools_for(perms: &[Permission]) -> Vec<&'static str> {
|
|||
/// `Execution` already grants shell execution to the parent agent, via the
|
||||
/// out-of-process `bash` MCP server (`mcp__bash__run`/`status`/`kill` —
|
||||
/// see the variant's own doc comment). A subagent has no MCP server at all
|
||||
/// by default (`docs/tools/subagent.md`), so there is no `mcp__bash__*` for
|
||||
/// by default (`docs/2-handbook/tools/subagent.md`), so there is no `mcp__bash__*` for
|
||||
/// it to inherit that permission through; it gets Claude's own `Bash`
|
||||
/// instead.
|
||||
///
|
||||
|
|
|
|||
Loading…
Reference in a new issue