Remove the conditional nftables firewall section and RAMEKIN_FIREWALL
env check from ramekin.ts. The container has no firewall — there is no
sidecar, no nftables rules, and the env var was never set. Replace the
inaccurate networking section with a simple statement that the container
has unrestricted network access via the default Docker bridge network.

The actual firewall implementation is tracked separately (task qt).

diff --git a/assets/ramekin.ts b/assets/ramekin.ts
index f4b4284..d431f31 100644
--- a/assets/ramekin.ts
+++ b/assets/ramekin.ts
@@ -1,9 +1,7 @@
 import type { ExtensionAPI } from "@mariozechner/pi-coding-agent";
 
 export default function (pi: ExtensionAPI) {
-  const firewall = process.env.RAMEKIN_FIREWALL !== "false";
-
-  let context = `
+  const context = `
 # Ramekin Container Environment
 
 You are running inside a Docker container managed by **ramekin**.
@@ -15,15 +13,11 @@ The project workspace is bind-mounted at \`/workspace\`. This is the only direct
 ## Filesystem
 
 The container filesystem is ephemeral. Any files written outside \`/workspace\` will be lost when the session ends. System packages installed with \`apt-get\` do not persist across sessions — use a custom \`.ramekin/Dockerfile\` to add permanent dependencies.
-`;
 
-  if (firewall) {
-    context += `
 ## Networking
 
-Networking is restricted by an nftables firewall. Only outbound connections to \`api.anthropic.com:443\` are allowed. You cannot fetch URLs, install packages from remote registries, or reach any other external host. All other outbound traffic is blocked.
+The container has unrestricted network access via the default Docker bridge network.
 `;
-  }
 
   pi.on("before_agent_start", async (event) => {
     return { systemPrompt: event.systemPrompt + "\n" + context };