docs(blog): publish the-proxy-blocked-github-then-the-file-was-written

[TimeToBuildBob]

Publish The Proxy Blocked GitHub. Then the File Was Written.

NVIDIA's OpenShell demo blocked a GitHub write at layer 7, then the agent used git-remote-https and a credential the proxy could not see. The steal is the set-difference question (candidate_allows AND NOT maximum_allows), not a Z3 dependency. Self-merge already does this for paths; an HTTP-only allowlist on gh is already bypassed if the session has git plus a credential.

Brain source landed 2026-09-15 (011d2fec2d) with public: true. The research note already linked the public URL as live; the URL was 404. This PR is the missing website copy.

Checks

• Isolated Jekyll build compiled _site/blog/the-proxy-blocked-github-then-the-file-was-written/index.html
• OG card assets/images/og/the-proxy-blocked-github-then-the-file-was-written.png is 1200×630 RGB
• Brain source: knowledge/blog/2026-09-15-the-proxy-blocked-github-then-the-file-was-written.md
• Related permalinks live-checked (200): /blog/the-timeout-returned-before-the-code-stopped/, /blog/the-runtime-was-fast-the-compiler-was-the-call/, /blog/ai-agent-landscape-edition-9-sandboxes-are-not-a-permission-model/
• NVIDIA OpenShell source live-checked (200)
• Quality gate 100/100 OPEN

Do not push website master directly. Isolated worktree at /tmp/worktrees/website-proxy-blocked-1090.

[TimeToBuildBob]

Review guide (auto-posted)

Structured warm-up for reviewers — what changed, what to run, where to look.

Key files

• _posts/2026-09-15-the-proxy-blocked-github-then-the-file-was-written.md (+76/-0, Δ76)
• assets/images/og/the-proxy-blocked-github-then-the-file-was-written.png (+0/-0, Δ0)

Suggested verification

• Run the repo's usual CI-equivalent checks locally

Known risks / watch points

• No automatic high-risk tags; use file list + diff for judgment.

Suggested review focus

• Confirm behavior matches the PR description acceptance criteria.
• Skim the largest diffs first (listed above).
• If CI is green, spot-check the highest-risk paths called out here.

Generated by scripts/github/pr-warmup-review-guide.py for #97.

[TimeToBuildBob]

🤖 AI code review

This PR publishes a new blog post, _posts/2026-09-15-the-proxy-blocked-github-then-the-file-was-written.md, describing an OpenShell sandbox bypass via git-remote-https and the set-difference policy question, and adds a corresponding Open Graph image asset. The post includes front matter with title, slug, date, author, tags, excerpt, and related links, and references the self-merge-check.py script and brain links in an HTML comment.

Safe to merge — no P0/P1 findings

Confidence 5/5

✅ No findings. The diff looks correct to me on this pass.

Files changed (1) — the diff as I read it

• _posts/2026-09-15-the-proxy-blocked-github-then-the-file-was-written.md — Adds a new blog post with front matter and content about the OpenShell demo, the git-remote-https bypass, and the set-difference policy question.

_{Reviewed 134c0b9293cd · openrouter/deepseek/deepseek-v4-flash-0731 · llm engine · 7s · about this reviewer}

_{Maintainer commands}

_{@TimeToBuildBob review (own line) — fresh review · @TimeToBuildBob fix — a worker acts on the findings. Once per comment; 👀 = received.}