Add multi-client documentation and dynamic port forwarding

CodeForge is editor-agnostic but docs were VSCode-first. Update all
documentation to reflect the five supported DevContainer clients:
VS Code, DevContainer CLI, JetBrains Gateway, DevPod, and Codespaces.

- Switch to dynamic port forwarding for all ports in devcontainer.json
- Add tabbed client-specific instructions on the installation page
- Add dedicated port forwarding reference page (VS Code, dbr, SSH)
- Update prerequisites in README and docs to list all clients
- Fix stale merge conflict marker in first-session.md

Author: AnExiledDev

.devcontainer/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 ## [Unreleased]
 
+### Changed
+
+#### Port Forwarding
+- Dynamic port forwarding for all ports in VS Code — previously only port 7847 was statically forwarded; now all ports auto-forward with notification
+
+#### Documentation
+- Updated prerequisites and installation docs to support all DevContainer clients (VS Code, CLI, JetBrains Gateway, DevPod, Codespaces)
+- Added tabbed client-specific instructions on the installation page
+- Added dedicated port forwarding reference page covering VS Code auto-detect, devcontainer-bridge, and SSH tunneling
+
+### Fixed
+
+#### Docs
+- Removed stale merge conflict marker in first-session docs page
+
 ### Added
 
 #### README

.devcontainer/CLAUDE.md

@@ -184,11 +184,14 @@ Custom features in `./features/` follow the [devcontainer feature spec](https://
 
 ## Port Forwarding
 
-Two mechanisms handle port access:
+Three mechanisms handle port access depending on your client:
 
-| Mechanism | When Active | Dynamic Discovery |
-|-----------|-------------|-------------------|
-| `forwardPorts` (devcontainer.json) | VS Code / Codespaces only | No (static list; VS Code auto-detects separately) |
-| devcontainer-bridge (`dbr`) | Any terminal client | Yes (polls `/proc/net/tcp`) |
+| Mechanism | Client | Discovery |
+|-----------|--------|-----------|
+| VS Code auto-detect | VS Code only | Dynamic — all ports auto-forwarded with notification |
+| devcontainer-bridge (`dbr`) | Any terminal client | Dynamic — polls `/proc/net/tcp` |
+| SSH tunneling | Any SSH client | Manual — `ssh -L localPort:localhost:remotePort` |
 
-`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).
+VS Code auto-detects all ports opened inside the container (configured via `portsAttributes` in `devcontainer.json`). Outside VS Code, `dbr` provides 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).
+
+For full setup instructions, see the [Port Forwarding reference](https://anexileddev.github.io/CodeForge/reference/port-forwarding/) in the docs.

.devcontainer/README.md

@@ -1,6 +1,6 @@
 # CodeForge Usage Guide
 
-Everything you need to know once you're inside the devcontainer.
+Everything you need to know once you're inside the devcontainer. These instructions apply regardless of which client you used to start the container — VS Code, the `devcontainer` CLI, JetBrains Gateway, DevPod, or GitHub Codespaces.
 
 ## Quick Start
 

.devcontainer/devcontainer.json

@@ -153,14 +153,14 @@
 		"ghcr.io/bradleybeddoes/devcontainer-bridge/dbr:0.2.0": {}
 	},
 
-	"forwardPorts": [7847],
+	"forwardPorts": [],
 	"portsAttributes": {
 		"7847": {
 			"label": "Claude Dashboard",
 			"onAutoForward": "notify"
 		},
 		"*": {
-			"onAutoForward": "silent"
+			"onAutoForward": "notify"
 		}
 	},
 

README.md

@@ -48,7 +48,12 @@ npx codeforge-dev@1.2.3
 ## Prerequisites
 
 - **Docker Desktop** (or compatible container runtime like Podman)
-- **VS Code** with the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers), or **GitHub Codespaces**
+- **A DevContainer client** — any of:
+  - **VS Code** with the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
+  - **DevContainer CLI** — `npm install -g @devcontainers/cli` ([docs](https://containers.dev/supporting#devcontainer-cli))
+  - **GitHub Codespaces** — zero local setup
+  - **JetBrains Gateway** with [Dev Containers plugin](https://plugins.jetbrains.com/plugin/21962-dev-containers)
+  - **DevPod** — open-source, editor-agnostic ([devpod.sh](https://devpod.sh/))
 - **Claude Code authentication** — run `claude` on first start to authenticate
 
 ## What's Included
@@ -127,11 +132,14 @@ For the complete configuration guide, see the [documentation site](https://anexi
 ## Quick Start
 
 1. **Install**: `npx codeforge-dev`
-2. **Open in Container**: "Reopen in Container" in VS Code, or create a Codespace
+2. **Open in Container**:
+   - **VS Code**: "Reopen in Container" from the Command Palette
+   - **CLI**: `devcontainer up --workspace-folder .` then `docker exec -it <container> zsh`
+   - **Codespaces**: Create a Codespace from the repo
 3. **Authenticate**: Run `claude` and follow prompts
 4. **Start coding**: Run `cc`
 
-For full usage documentation — authentication, configuration, tools, agents, and keybindings — see [`.devcontainer/README.md`](.devcontainer/README.md).
+CodeForge uses the open [Dev Containers specification](https://containers.dev/) — any compatible client works. For full usage documentation — authentication, configuration, tools, agents, and keybindings — see [`.devcontainer/README.md`](.devcontainer/README.md).
 
 ## Contributing