# Issue URL port isolation proof

The scenario uses a deterministic ACP driver to execute `read_issue` and `comment_on_issue` against T3 Code's real authenticated MCP endpoint. Its chat output summarizes the live responses and independently fetched Gitea issue comment counts.

Requirements: Docker, OpenSSL, Python 3, Node, Vite Plus, Tea 0.16.0, and ghdrop. Run from a current-main checkout with dependencies installed. Set `ISSUE_PROOF_DIR` to a fresh scratch directory. Put `agent.mjs` there and `start.py` in its `setup` subdirectory. Put the scenario in `scripts/scenarios/`.

```sh
mkdir -p "$ISSUE_PROOF_DIR/setup"
openssl req -x509 -newkey rsa:2048 -nodes \
  -keyout "$ISSUE_PROOF_DIR/setup/key.pem" \
  -out "$ISSUE_PROOF_DIR/setup/cert.pem" -days 2 \
  -subj /CN=gitea.127.0.0.1.nip.io \
  -addext subjectAltName=DNS:gitea.127.0.0.1.nip.io
python3 "$ISSUE_PROOF_DIR/setup/start.py"
export XDG_CONFIG_HOME="$ISSUE_PROOF_DIR/setup/config"
export GITEA_SERVER_TOKEN="$(cat "$ISSUE_PROOF_DIR/setup/default-token")"
tea login add --name proof-default --url https://gitea.127.0.0.1.nip.io --insecure
unset GITEA_SERVER_TOKEN
export NODE_EXTRA_CA_CERTS="$ISSUE_PROOF_DIR/setup/cert.pem"
export T3CODE_DEV_SEED=0
export T3_SCENARIO_INHERIT_ENV=ISSUE_PROOF_DIR,XDG_CONFIG_HOME,NODE_EXTRA_CA_CERTS,T3CODE_DEV_SEED
vp run scenarios:prove scripts/scenarios/issue-url-unconfigured-port.e2e.ts \
  --base efbd13983fe3280721469815415a3a1d53de3e62 \
  --head 35a59673d32e006c8fbdd4e8159f5207f3d2f95c \
  --upload-command 'env -u XDG_CONFIG_HOME ghdrop upload'
docker rm -f proof40047-default proof40047-alternate
```

Only the default-port server is authenticated. Both servers contain `acme/web` issue 3 with different titles. The scenario clears prior proof comments before each side and creates a fresh T3 project and thread through the application's own API and CLI.

The MCP wire format presents tracker-unsupported as “Issues cannot be browsed for this project yet.” It does not expose the tagged error or its reason field.
