Add --publish: the one ingress control

Everything else in the file gates egress, which left an everyday request unanswered: the
agent starts a dev server inside the sandbox and a human wants to look at it. This puts a
listener on the host that forwards into the container, so a browser, curl or an API
tester reaches the server the sandboxed process runs.

`--publish [ADDR:]HOST:CONTAINER`, config `publish` and AISB_PUBLISH, repeatable, with the
cost named in the flag: it is ingress, so whatever that server serves is reachable from
the address it binds. The default address is 127.0.0.1 because a bare podman -p binds
every interface (measured) -- a port committed in a repo config must not quietly be a port
on the LAN. publish_addr changes the default machine-wide; a spec with a non-loopback
address warns on every run. The grammar is smaller than podman's on purpose: one port per
entry, no ranges, no /udp, no `*` -- this list is reviewed line by line, and typing
0.0.0.0 is the whole warning. An address means three parts, so `127.0.0.1:8000` is refused
rather than guessed. No -p alias: that flag belongs to the harness (claude -p prints).

Fail closed, as elsewhere: --net none cannot forward a port and podman discards the
mapping while starting the container anyway, so "it ran" would mean "nothing is
listening"; a host port already in use is named before the container starts, not after a
build; pick_port() will not hand the gate a port this run publishes. The container is
labelled with the ports it was given, and doctor reports them.

Inside, publish_rules() accepts tcp on the published ports in the input chain and never
the output one. Measured (docs/networking.md): pasta delivers the connection over
loopback, so that rule counts 0 packets on the reference host; it is there for a host or a
bridge network that delivers on the interface, and so that `nft list table inet aisb`
answers "what can reach this container". The ports are validated again inside the
entrypoint, because a ruleset is not somewhere to splice an unvalidated string. And the
measurement that makes a configured preview look broken: a server bound to 127.0.0.1
inside answers inside and refuses the published port outside, so dev servers must bind
0.0.0.0 -- both skills say so in the change that writes the port.

Tests. Unit: the grammar and every port list that looks right and is not, config/env/flag
precedence and dedup, the canonical spec in --print-policy, the `# ingress:` header, the
flags reaching the invocation before the image, egress enforcement byte-identical with a
port open, which chain the rule lands in and that a non-numeric port never reaches nft as
code. e2e (tests/e2e/13_publish.sh): one real container with enforce=nft where the host
gets its 200 and the same run still refuses a domain outside the allowlist at 403, the
server runs as uid 1000 with no capabilities so it cannot widen its own port, and the host
listener is gone when the container exits.

LLM-Generated: true

tests/unit/02_config.sh

@@ -91,6 +91,44 @@ for last in '# a trailing comment' '' '   '; do
   assert_contains "api.openai.com" "user target survives a file ending on [$last]"
   assert_contains "pypi.org"       "repo target survives a file ending on [$last]"
 done
+
+t_name "publish accumulates like the other list keys"
+cat > "$CFG/config" <<'EOF'
+publish = 8000
+EOF
+cat > "$REPO/.ai-sandbox/config" <<'EOF'
+publish = 18080:8000
+EOF
+sb --print-policy --net allow --allow example.com
+assert_contains "publish=127.0.0.1:8000:8000" "user config publishes"
+assert_contains "127.0.0.1:18080:8000"         "repo config adds to it rather than replacing it"
+sb_env AISB_PUBLISH=9000,9100:80 --print-policy --net allow --allow example.com
+assert_contains "127.0.0.1:9000:9000"  "AISB_PUBLISH is a comma list of the same shapes"
+assert_contains "127.0.0.1:9100:80"    "  ... including host:container"
+sb --print-policy --net allow --allow example.com --publish 9200
+assert_contains "127.0.0.1:9200:9200"  "a flag adds to both files"
+sb --print-policy --net allow --allow example.com --publish 8000
+N="$(printf '%s' "$OUT" | grep -o '127.0.0.1:8000:8000' | wc -l | tr -d ' ')"
+assert_eq "1" "$N" "the same port from two sources collapses to one"
+
+t_name "publish_addr is the default bind address, and only that"
+cat > "$CFG/config" <<'EOF'
+publish_addr = 127.0.0.2
+EOF
+rm -f "$REPO/.ai-sandbox/config"
+sb --print-policy --net allow --allow example.com --publish 8000
+assert_contains "publish=127.0.0.2:8000:8000" "config file sets the address a bare port binds"
+sb_env AISB_PUBLISH_ADDR=127.0.0.3 --print-policy --net allow --allow example.com --publish 8000
+assert_contains "127.0.0.3:8000:8000" "AISB_PUBLISH_ADDR beats the config file"
+sb_env AISB_PUBLISH_ADDR=localhost --print-policy --net allow --allow example.com --publish 8000
+assert_contains "publish=localhost:8000:8000" "a name is accepted where an address goes"
+printf '%s' "$OUT" | grep -qF 'route to this machine' \
+  && _bad "localhost warned about as if it were the LAN" || _ok "localhost counts as loopback: no LAN warning"
+sb --print-policy --net allow --allow example.com --publish 0.0.0.0:8000:8000
+assert_contains "publish=0.0.0.0:8000:8000" "an address written in the spec is the address used"
+printf '%s' "$OUT" | grep '^publish=' | grep -qF '127.0.0.2' \
+  && _bad "publish_addr overwrote an explicit address" || _ok "publish_addr only fills in a bare port"
+
 # The fix must not trade one silence for another: with no target anywhere, the run still
 # refuses, and says why.
 printf '# nothing but a header here\n' > "$CFG/allow"