Add devcontainer-bridge (dbr) for VS Code-independent port forwarding

forwardPorts in devcontainer.json is a no-op outside VS Code. dbr provides
dynamic port auto-discovery via /proc/net/tcp polling and forwards to the
host via reverse TCP connections. Container daemon is inert without the
host daemon, so VS Code users are unaffected.

Author: AnExiledDev

.devcontainer/CHANGELOG.md

@@ -1,5 +1,11 @@
 # CodeForge Devcontainer Changelog
 
+## [Unreleased]
+
+### Added
+
+- **devcontainer-bridge (dbr)** — Dynamic port auto-discovery and forwarding independent of VS Code. Container daemon polls for new listeners and forwards them to the host via reverse TCP connections. Requires `dbr host-daemon` running on the host machine. See [devcontainer-bridge](https://github.com/bradleybeddoes/devcontainer-bridge)
+
 ## [v1.14.2] - 2026-02-24
 
 ### Fixed

.devcontainer/CLAUDE.md

@@ -45,6 +45,7 @@ Config files deploy via `file-manifest.json` on every container start. Most depl
 | `agent-browser` | Headless Chromium (Playwright-based) |
 | `check-setup` | Verify CodeForge setup health |
 | `claude-dashboard` | Session analytics dashboard (port 7847) |
+| `dbr` | Dynamic port forwarding (devcontainer-bridge) |
 | `cc-tools` | List all installed tools with versions |
 
 ## Plugins
@@ -95,3 +96,14 @@ All experimental feature flags are in `settings.json` under `env`. Setup steps c
 ## Features
 
 Custom features in `./features/` follow the [devcontainer feature spec](https://containers.dev/implementors/features/). Every local feature supports `"version": "none"` to skip installation. Claude Code is installed via `ghcr.io/anthropics/devcontainer-features/claude-code:1`.
+
+## Port Forwarding
+
+Two mechanisms handle port access:
+
+| Mechanism | When Active | Dynamic Discovery |
+|-----------|-------------|-------------------|
+| `forwardPorts` (devcontainer.json) | VS Code / Codespaces only | Yes (VS Code auto-detect) |
+| devcontainer-bridge (`dbr`) | Any terminal client | Yes (polls `/proc/net/tcp`) |
+
+`forwardPorts` is a no-op outside VS Code — the `devcontainer` CLI ignores it. `dbr` provides VS Code-independent dynamic port discovery via a reverse connection model (container→host). The container daemon auto-starts and is inert without the host daemon (`dbr host-daemon`). Both mechanisms coexist. See [devcontainer-bridge](https://github.com/bradleybeddoes/devcontainer-bridge).

.devcontainer/devcontainer.json

@@ -35,7 +35,8 @@
 	// npm-dependent features (agent-browser, ccusage, ccburn, claude-session-dashboard,
 	// biome, lsp-servers) must come after Node. uv-dependent features (ruff, claude-monitor) must
 	// come after uv. cargo-dependent features (ccms) must come after Rust.
-	// notify-hook is last (lightweight, no dependencies).
+	// notify-hook is second-to-last (lightweight, no dependencies).
+	// dbr (devcontainer-bridge) is last — standalone binary, no dependencies.
 	"overrideFeatureInstallOrder": [
 		"ghcr.io/devcontainers/features/node",
 		"ghcr.io/devcontainers/features/github-cli",
@@ -63,7 +64,8 @@
 		"./features/shellcheck",
 		"./features/hadolint",
 		"./features/biome",
-		"./features/notify-hook"
+		"./features/notify-hook",
+		"ghcr.io/bradleybeddoes/devcontainer-bridge/dbr"
 	],
 
 	"features": {
@@ -133,7 +135,8 @@
 		"./features/notify-hook": {
 			"enableBell": true,
 			"enableOsc": true
-		}
+		},
+		"ghcr.io/bradleybeddoes/devcontainer-bridge/dbr:latest": {}
 	},
 
 	"forwardPorts": [7847],