Ship usable ooo bridge path so GJC can run ooo interview out of the box

[Yeachan-Heo]

Summary

Community request from Discord #playground-ko: make GJC able to use ooo so users can run ooo interview.

Current state

• Exact-prefix ooo bridge API already exists: createOuroborosOooBridge() / createExactPrefixCommandBridge({ prefix: \"ooo\", command: \"ouroboros\", args: [\"dispatch\"] }) (merged PR feat(extensibility): exact-prefix command bridge for external ooo dispatch #441).
• Contract docs: docs/ooo-bridge-extension-contract.md.
• Deep-interview already adopted ooo-interview behavior ports (merged PR feat(deep-interview): port ouroboros ooo-interview updates #2640), but that is not the same as typing ooo ... in GJC.
• The bridge is not a default workflow skill / built-in agent. It only works if:
  1. an extension registers the input handler, and
  2. the ouroboros CLI is available for ouroboros dispatch <text>.
• packages/coding-agent/examples/extensions/ has no ooo example, and default GJC extensions do not register the bridge.

Requested outcome

Make ooo / ooo interview a usable path for GJC users, not just an internal helper export.

Proposed acceptance criteria

1. Provide a first-class install path for the ooo bridge:
   • either ship a default/opt-in extension under defaults/gjc/extensions or examples/extensions with copy-install docs, and/or
   • document one-command enablement.
2. End-to-end docs for:
   • install/enable the bridge
   • install/discover ouroboros CLI dependency
   • run ooo interview (and other ooo ... commands)
   • failure modes (missing binary, exit 78 pass-through, recursion guard, non-interactive sources)
3. Tests covering the shipped extension/example wiring (not only the helper unit tests).
4. Clear product note distinguishing:
   • GJC /skill:deep-interview (native interview skill with ooo-inspired behavior)
   • external ooo interview via the ouroboros bridge
5. Do not invent a security fix from unsubstantiated public banter; any vulnerability work requires private repro + coordinated disclosure.

Context

• Discord source: gajae community #playground-ko message 1534010886245580891 (direct mention of gaebal-gajae).
• Related prior work: PR feat(extensibility): exact-prefix command bridge for external ooo dispatch #441 (bridge contract), PR feat(deep-interview): port ouroboros ooo-interview updates #2640 (deep-interview ooo-interview ports).

Non-goals

• Replacing native deep-interview with ouroboros.
• Shipping secrets, private ops doctrine, or speculative vuln patches without repro.

[Yeachan-Heo]

Follow-up refinement from Discord

Community follow-up in #playground-ko (1534014083462860841):

when running ooo interview, implement so it can operate through ouroboros MCP
base it on the latest release

Updated acceptance (additive)

• Keep the original usable ooo / ooo interview path goal.
• Explicit runtime path: ooo interview should be able to operate via the ouroboros MCP path, not only as an internal helper export.
• Implementation baseline: latest release / current dev, not stale docs-only guidance.
• Still distinguish native /skill:deep-interview from external ooo interview via ouroboros.

GJC lane gajae-code-issue-3803-ooo-bridge-usable is being re-prompted with this refinement.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[Yeachan-Heo]

Signed computer/task batch triage decision

Decision: BLOCKED — do not open an implementation lane yet.

Exact product scope and ownership

• GJC owns: the extension input-event contract and loader, createExactPrefixCommandBridge / createOuroborosOooBridge, GJC-side compatibility behavior, tests, and docs/ooo-bridge-extension-contract.md.
• Ouroboros owns: installation of the concrete extension, the ouroboros executable, skill routing, MCP server/tools, interview session persistence, and release documentation. Latest release v0.50.7 (cb658aa819bfabafecbbe91bc36327f10691171b) already implements ouroboros setup --runtime gjc, installing ~/.gjc/agent/extensions/ouroboros-ooo-bridge/index.ts, and dispatches ouroboros dispatch --runtime gjc --cwd <cwd> <text>.
• Not this product surface: @gajae-code/bridge-client. That package is the SDK v3 transport-only client and must not gain OOO command/MCP/session authority.
• Native distinction: /skill:deep-interview remains GJC-owned. External ooo interview remains Ouroboros-owned and must not replace or alias the native workflow.

Duplicate census

• No other open issue or PR for a usable ooo interview GJC path was found.
• feat(extensibility): exact-prefix command bridge for external ooo dispatch #441 is the prerequisite GJC extension contract, not a duplicate.
• feat(deep-interview): port ouroboros ooo-interview updates #2640 and feat(deep-interview): port recent ouroboros interview enhancements + trim skill #590 port interview behavior into native deep-interview; they are intentionally not the external bridge path.

Concrete blockers

1. Successful output is dropped by current GJC. On current dev a8fa63a599e9fa3d0189e48bfce778a36353ccdd, input-controller.ts returns immediately when InputEventResult.handled is true and only reads result.text afterward for non-handled results. Ouroboros v0.50.7's installed GJC extension returns { handled: true, text: body } for success/failure. Therefore the first MCP interview question is not displayed by GJC.
2. There is no cross-process multi-turn continuation contract. Ouroboros's dispatcher can resume ouroboros_interview only when a RuntimeHandle carrying ouroboros_interview_session_id is passed. The CLI bridge calls the dispatcher with current_handle = None, prints only result content, and discards that handle. Subsequent GJC input therefore has no typed session ID/answer route and would start a new interview or fall through.
3. Contract drift: GJC's public helper still invokes ouroboros dispatch <text> and treats exit 0 as silent terminal handling; the latest Ouroboros-owned extension invokes --runtime gjc --cwd and expects handled text to be rendered. Prefix normalization also differs. Shipping a second default/example extension now would duplicate upstream ownership without resolving these incompatibilities.

Bounded acceptance required before implementation

A cross-repo contract decision must first specify one machine-readable continuation envelope for ooo interview, including:

1. initial question text, session_id, and terminal/nonterminal state;
2. how GJC renders handled extension output without sending it to the model;
3. how subsequent interactive answers are claimed and forwarded with that session_id;
4. cancel, timeout, exit-78 pass-through, extension reload/session switch, and terminal cleanup semantics;
5. one canonical prefix/whitespace/case contract;
6. ownership of conformance fixtures shared between GJC current dev and Ouroboros latest release.

Once that envelope is agreed, the implementation stays bounded to the existing helper/input extension surface, one installed-extension integration test, docs/setup guidance for ouroboros setup --runtime gjc, and explicit native-vs-external product wording. No default workflow skill, built-in agent, bridge-client authority, duplicate extension installer, or unrelated MCP framework work is accepted.

No linked/open mutation PR or repo-visible active implementation artifact was found, and no new lane was created during triage.

Signature: GJC computer/task triage | issue #3803 | GJC dev a8fa63a599e9fa3d0189e48bfce778a36353ccdd | Ouroboros v0.50.7@cb658aa819bfabafecbbe91bc36327f10691171b | BLOCKED_CROSS_REPO_CONTINUATION_CONTRACT

[Yeachan-Heo]

Implemented and opened PR #3805: #3805

The PR ships a copy-installable GJC ooo bridge example, documents the preferred Ouroboros v0.50.7+ ouroboros setup --runtime gjc path, and binds the canonical helper to ouroboros dispatch --runtime gjc so ooo interview uses Ouroboros's GJC MCP-backed skill dispatcher. Missing Ouroboros remains a handled notification and does not affect GJC startup or ordinary prompts.

Verification: 60 focused tests passed, coding-agent Biome/TypeScript checks passed, git diff --check passed, and the Ultragoal review reported no findings.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]