## Why

Oh My OpenCode's `task()` subagents run in child sessions that are invisible to Paseo's `paseo ls` command. Users who orchestrate across both systems see a split view — Paseo agents on one side, OMO subagents only via `list-child-sessions`. This creates a cognitive gap: you can't see your full agent fleet in one place.

Paseo already has the bridge: `paseo import <session-id> --provider opencode` wraps an existing session as a Paseo agent without starting a new process. But nothing automatically calls it for OMO subagents.

We need a thin bridge layer that registers OMO child sessions as Paseo agents — automatically, with labels for filtering, and cleanup when the subagent finishes.

## What Changes

- **New OpenCode skill** (`omo-paseo-bridge`): A skill that wraps `paseo import` for OMO child sessions. Can be invoked from the Atlas orchestration prompt or triggered by a hook.
- **New hook or prompt instruction**: Atlas-level rule to call `paseo import` on every `task()` child session, and `paseo archive` on completion.
- **Optional bridge script**: Standalone CLI tool that reads child sessions and imports all unregistered ones.

## Capabilities

### New Capabilities

- `omo-paseo-visibility`: OMO subagents from `task()` appear in `paseo ls` with labels (`omo=true`, `type=<category>`)
- `omo-paseo-cleanup`: Completed/failed OMO subagents are automatically archived from Paseo's agent list
- `omo-paseo-filter`: `paseo ls --filter omo=true` shows only OMO subagents; `--filter omo=false` excludes them

## Impact

- **`/home/samkintop/opt/forks/.opencode/skills/`**: New `omo-paseo-bridge` directory with SKILL.md
- **Atlas orchestration prompt**: New instruction block for `task()` → `paseo import` mapping
- **`~/.paseo/agents/`**: Receives imported OMO child session records via `paseo import`
- **No changes to Paseo daemon code**: Uses existing `importAgent` API
