…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

## Problem

The 'Hide tool details' toggle in the command palette (Ctrl+P) has no
effect on the UI - completed tools are always displayed regardless of
the setting.

## Root Cause

The Permission rework commit 351ddee (merged 2026-01-01, PR anomalyco#6319)
accidentally removed the showDetails check from the ToolPart function
when refactoring the tool rendering system.

### Before Permission rework (working):

```typescript
function ToolPart(props: { last: boolean; part: ToolPart; message: AssistantMessage }) {
  const { theme } = useTheme()
  const { showDetails } = use()  // <-- Gets showDetails from context
  const sync = useSync()
  const [margin, setMargin] = createSignal(0)
  const component = createMemo(() => {
    // Hide tool if showDetails is false and tool completed successfully
    // But always show if there's an error or permission is required
    const shouldHide =
      !showDetails() &&
      props.part.state.status === "completed" &&
      !sync.data.permission[props.message.sessionID]?.some((x) => x.callID === props.part.callID)

    if (shouldHide) {
      return undefined  // <-- Returns nothing, hiding the tool
    }
    // ...
  })
}
```

### After Permission rework (broken):

```typescript
function ToolPart(props: { last: boolean; part: ToolPart; message: AssistantMessage }) {
  const sync = useSync()
  // <-- No use() call!
  // <-- No showDetails check!

  const toolprops = { /* ... */ }

  return (
    <Switch>
      // <-- Always renders all tools unconditionally
    </Switch>
  )
}
```

## Fix

Restore the showDetails check by:
1. Adding `const ctx = use()` to access the context
2. Adding a `shouldHide` memo with the original logic
3. Wrapping the return in `<Show when={!shouldHide()}>`

The fix preserves the original behavior:
- Hide completed tools when showDetails is false
- Always show tools that are pending/running (so users see progress)
- Always show tools that require permission (so users can respond)

## Problem

The 'Hide tool details' toggle in the command palette (Ctrl+P) has no
effect on the UI - completed tools are always displayed regardless of
the setting.

## Root Cause

The Permission rework commit 351ddee (merged 2026-01-01, PR anomalyco#6319)
accidentally removed the showDetails check from the ToolPart function.

## Fix

Restore the showDetails check with simplified logic:
- Show all tools when showDetails is true
- Show running/pending tools (so users see progress)
- Hide completed tools when showDetails is false

Removed the permission-based visibility check as the new PermissionPrompt
dialog handles permissions separately at the bottom of the screen.

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution

The permission rework in anomalyco#6319 removed the ability to override the default
task tool restriction via agent frontmatter. Previously, agents could set
`tools: { task: true }` to enable nested sub-agents.

This fix restores that functionality using the new permission system:
- Check if the agent's permission ruleset explicitly allows task tool
- If so, don't add the deny rule to session permissions
- If so, don't pass task: false to the tools parameter

Agents can now enable nested sub-agents by setting:
```yaml
permission:
  task: allow
```

The default behavior remains unchanged - task tool is disabled for
sub-agents unless explicitly allowed.

The permission rework in anomalyco#6319 removed the ability to override the default
task tool restriction via agent frontmatter.

This fix checks if the agent has any task permission rule defined. If so,
we don't add our default deny - letting the agent's permission take effect.
If not specified, the default deny behavior is preserved.

…omalyco#6319) for tool availability and tool execution

…omalyco#6319) for tool availability and tool execution