ops-bridge/registry/capabilities/capability.ops.tunnel-bridge.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.ops.tunnel-bridge	SSH Reverse Tunnel Lifecycle Manager (ops-bridge)	CLI that manages named SSH reverse tunnels keeping remote execution environments connected to the local Custodian State Hub, with auto-reconnect, health checks, and structured audit events.	ops-bridge	draft	infotech	ssh tunnel ops connectivity	discovery availability current target confidence rationale D3 D5 medium README.txt documents named tunnels, auto-reconnect with exponential backoff, HTTP health checks, and structured JSON audit events per tunnel; this is also the tool underlying reuse-surface's own `/bridge` skill. current target confidence rationale A2 A3 medium Ships a `bridge` CLI, installable via pyproject; already actively used to keep remote Claude Code sessions (COULOMBCORE, Railiance nodes) connected to the State Hub MCP.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 low scope_vs_intent_and_consumer_expectations auto-reconnecting named SSH reverse tunnels HTTP health checks confirming forwarded service reachability, not just SSH liveness structured audit event log per tunnel level confidence basis known_reliability_risks R1 low consumer_quality_signals operational tool with real production usage but no independent load/failure testing recorded in this sweep	intent includes excludes assumptions use_cases research_memos Keep remote execution environments' MCP connectivity to the local State Hub alive and observable via managed, auto-reconnecting SSH reverse tunnels. named SSH reverse tunnel lifecycle management auto-reconnect with exponential backoff HTTP health checks structured audit event logging the State Hub or MCP servers themselves (bridge only manages connectivity)	current_level target_level current_artifacts target_artifacts consumption_modes A2 A3 `bridge` CLI cli	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.txt tests/	recommended_for not_recommended_for known_limitations any workstation/remote-machine pair needing durable SSH-tunneled MCP or service connectivity needs for tunnel types other than SSH reverse port-forwards no independent load/failure testing recorded beyond production usage observations

SSH Reverse Tunnel Lifecycle Manager (ops-bridge)

Overview

ops-bridge is an SSH reverse tunnel lifecycle manager: a bridge CLI that keeps remote execution environments (COULOMBCORE, Railiance nodes) connected to the local Custodian State Hub, with auto-reconnect, health checks, and structured audit logging per tunnel.

Assessment notes

Discovery

README.txt documents named tunnels, auto-reconnect with exponential backoff, HTTP health checks, and structured JSON audit events per tunnel; this is also the tool underlying reuse-surface's own /bridge skill.

Availability

Ships a bridge CLI, installable via pyproject; already actively used to keep remote Claude Code sessions (COULOMBCORE, Railiance nodes) connected to the State Hub MCP.

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml