Files
boocode/openspec/changes/omo-paseo-bridge/specs/omo-paseo-visibility/spec.md
indifferentketchup c935687725 chore(openspec): drop 9 superseded proposals + 11 stub archive files
Drop 9 batch proposals that are superseded by the boocode-lift-analysis
(boocontext-audit, conductor upgrades, self-healing/verify-gate skills):
add-3tier-memory, import-llm-evaluator, import-pregel-engine, plugin-platform,
conductor-evolution, code-intelligence-upgrade, dev-workflow, ui-overhaul,
agent-reliability.

Delete 11 stub archive files (49-66B each, 'Status: Shipped. Archived.' only)
that provide zero documentation value over the existing CHANGELOG.md + git tags.
2026-06-07 22:15:38 +00:00

52 lines
2.6 KiB
Markdown

## ADDED Requirements
### Requirement: OMO subagent registration
The system SHALL register OMO child sessions as Paseo agents via paseo import so they appear in paseo ls.
#### Scenario: User runs task() to create an OMO subagent
**Given** Atlas calls `task()` with a description and category
**When** the child session is created (returning `ses_xxx` ID)
**Then** the bridge skill calls `paseo import <ses_xxx> --provider opencode --label omo=true`
**And** the subagent appears in `paseo ls` with the task description as its name
**And** the agent carries an `omo=true` label for filtering
#### Scenario: User runs the bridge script manually
**Given** a valid OMO child session ID (ses_xxx)
**When** the user runs `omo-paseo-bridge.sh register <session-id> --type <category>`
**Then** `paseo import` wraps the session as a Paseo agent
**And** the script prints the agent UUID for later unregister
**And** the agent shows in `paseo ls` as an active agent
### Requirement: OMO subagent unregistration
The system SHALL remove Paseo agent records when OMO subagents complete via paseo archive.
#### Scenario: Subagent completes and is cleaned up
**Given** an OMO subagent was previously imported as a Paseo agent
**When** the subagent task completes
**Then** the bridge calls `paseo archive <agent-uuid>`
**And** the agent is removed from `paseo ls` active list
#### Scenario: User unregisters manually
**Given** an OMO subagent was previously imported as a Paseo agent (UUID `abc-123`)
**When** the user runs `omo-paseo-bridge.sh unregister abc-123`
**Then** `paseo archive abc-123` is called
**And** the agent is removed from active list
### Requirement: Script handles common error cases
The script SHALL gracefully handle daemon-not-running, already-imported, and invalid-session errors.
#### Scenario: Paseo daemon is not running
**Given** the Paseo daemon is not running
**When** the user runs any bridge command
**Then** the script prints a clear error message
**And** tells the user to run `paseo daemon start`
**And** exits with a non-zero exit code
#### Scenario: Session already imported
**Given** a session ID was previously imported as a Paseo agent
**When** the user tries to register it again
**Then** `paseo import` returns an error
**And** the script reports that the agent already exists
## ADDED Files
- `.opencode/skills/omo-paseo-bridge/SKILL.md` — Skill definition with frontmatter, register/unregister operations, error handling, and Atlas integration protocol.
- `.opencode/skills/omo-paseo-bridge/bin/omo-paseo-bridge.sh` — Shell script implementing `register`, `unregister`, `status`, `list`, and `find` commands for bridging OMO subagents into Paseo.