revert: remove Squid intercept mode and all cascading fixes

Reverts the following PRs which introduced unnecessary complexity:

- #520: fix: enable Squid intercept mode for NAT-redirected traffic
- v0.13.5 release: chore(release): bump version to 0.13.5
- #524: fix: remove HTTP_PROXY/HTTPS_PROXY env vars from agent container
- #526: chore: recompile workflow lock files for AWF v0.13.5
- #527: fix: recompile lock files with release action mode
- #522: fix: mount /etc/hosts in chroot and fix HTTP blocking test
- #530: fix: restore HTTPS_PROXY, fix chroot hosts/permissions, fix Bun crash
- v0.13.6 release: chore(release): bump version to 0.13.6

The intercept mode (#520) was introduced to fix Codex failing with
HTTP_PROXY, but the simpler fix is to just not set HTTP_PROXY for
Codex. The intercept mode introduced a cascade of breakage:
- HTTPS can't be transparently intercepted (needs CONNECT method)
- Image version bumps required lock file recompilation
- host.docker.internal traffic crashed Squid under load
- Multiple PRs needed to fix each regression

This reverts to the pre-#520 explicit proxy mode (HTTP_PROXY/HTTPS_PROXY
pointing to Squid port 3128) which worked for all engines.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Mossaka

.github/workflows/agentics-maintenance.yml

@@ -13,7 +13,7 @@
 # \  /\  / (_) | | | | ( | | | | (_) \ V  V /\__ \
 #  \/  \/ \___/|_| |_|\_\|_| |_|\___/ \_/\_/ |___/
 #
-# This file was automatically generated by pkg/workflow/maintenance_workflow.go. DO NOT EDIT.
+# This file was automatically generated by pkg/workflow/maintenance_workflow.go (v0.42.0). DO NOT EDIT.
 #
 # To regenerate this workflow, run:
 #   gh aw compile
@@ -33,7 +33,7 @@ name: Agentic Maintenance
 
 on:
   schedule:
-    - cron: "37 0 * * *"  # Daily (based on minimum expires: 7 days)
+    - cron: "37 0 * * *"  # Daily (based on minimum expires: 30 days)
   workflow_dispatch:
 
 permissions: {}
@@ -47,7 +47,7 @@ jobs:
       pull-requests: write
     steps:
       - name: Setup Scripts
-        uses: github/gh-aw/actions/setup@v0.42.2-28-gfba53102d
+        uses: github/gh-aw/actions/setup@v0.42.0
         with:
           destination: /opt/gh-aw/actions
 

.github/workflows/build-test-bun.lock.yml

@@ -11,14 +11,12 @@ permissions:
   issues: read
 name: Build Test Bun
 engine: copilot
-runtimes:
-  bun:
-    version: "latest"
 network:
   allowed:
     - defaults
     - github
     - node
+    - "bun.sh"
 tools:
   bash:
     - "*"
@@ -37,11 +35,6 @@ timeout-minutes: 15
 strict: true
 env:
   GH_TOKEN: "${{ secrets.GH_AW_GITHUB_MCP_SERVER_TOKEN }}"
-steps:
-  - name: Checkout repository
-    uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8
-    with:
-      persist-credentials: false
 ---
 
 # Build Test: Bun
@@ -50,7 +43,12 @@ steps:
 
 ## Test Requirements
 
-1. **Verify Bun**: Bun is pre-installed. Run `bun --version` to confirm it's available on PATH.
+1. **Install Bun**:
+   ```bash
+   curl -fsSL https://bun.sh/install | bash
+   export BUN_INSTALL="$HOME/.bun"
+   export PATH="$BUN_INSTALL/bin:$PATH"
+   ```
 
 2. **Clone Repository**: `gh repo clone Mossaka/gh-aw-firewall-test-bun /tmp/test-bun`
    - **CRITICAL**: If clone fails, immediately call `safeoutputs-missing_tool` with message "CLONE_FAILED: Unable to clone test repository" and stop execution
@@ -83,7 +81,7 @@ If ANY test fails, report the failure with error details.
 **CRITICAL**: This workflow MUST fail visibly when errors occur:
 
 1. **Clone failure**: If repository clone fails, call `safeoutputs-missing_tool` with "CLONE_FAILED: [error message]"
-2. **Bun not available**: If `bun --version` fails, call `safeoutputs-missing_tool` with "BUN_NOT_FOUND: bun not available on PATH"
+2. **Bun install failure**: Call `safeoutputs-missing_tool` with "BUN_INSTALL_FAILED: [error message]"
 3. **Test failure**: Report in comment table with FAIL status and include failure details
 
 DO NOT report success if any step fails. The workflow should produce a clear, actionable error message.