Skip to content

Add opt-in host GitHub SSH proxy for release 0.3.1 - #47

Merged
ccozianu merged 48 commits into
release-0.3.1from
ws-github-auth/ssh-proxy
Nov 16, 2026
Merged

ccozianu merged 48 commits into
release-0.3.1from
ws-github-auth/ssh-proxy

Conversation

@ccozianu

@ccozianu ccozianu commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Adds opt-in host SSH authentication for GitHub clone, fetch and push inside capsules. With github-ssh authorized, the outside launcher runs host OpenSSH for validated GitHub Git requests. Capsule Git connects through a private Unix socket; private keys and the host SSH agent stay on the host. Non-GitHub destinations use capsule SSH.

Target: release-0.3.1, as directed by the owner. Package/workflow version files and the documentation version manifest match that release. Unrelated mainline documents are excluded. The release branch is already included through merge history; this PR does not bring the next development version into the release.

The initial transport supports Linux/WSL with native Docker, including the tested rootless Docker setup. Host key trust and noninteractive host SSH authentication are prerequisites. The grant covers all GitHub repositories available to the host identity. Docker Desktop, HTTPS/gh API credentials, Git LFS authentication, signing and arbitrary SSH aliases/options remain outside this slice.

Pair Review: GPT-6 Codex with Antigravity Gemini 4 Hydrogen High (gemini-4-hydrogen-high, high effort). Review #44 was accepted after round 2 at 455d3acc and merged at 9638cb11. It corrects error attribution and authorization/lifetime disclosure, and strengthens parser, process cleanup and refusal tests. Both assessments are on #44.

Validation on combined review merge 9638cb11:

  • 64 focused unit/integration cases passed, including real local Git clone/fetch/push through the broker.
  • Full build reached 3,320 passing unit cases; two inherited recursive-launch tests fail because this capsule's Docker socket group ID is zero. One skip, one xfail, one xpass; 191 deselected by the standard suite. The same failures occurred in the reviewer's independent run. No tests were disabled.
  • Types passed on 351 files; conventions found zero breaches.
  • Separate CLI smoke, PEX build/smoke, documentation contract (249 pages), console types and all 474 console tests passed.
  • The rebuilt PEX completed a real read-only GitHub ls-remote using an empty HOME and the inherited host proxy. Missing-socket control exited 128. No GitHub write, container launch or host-launcher replacement occurred.

The local full gate is not green. The owner-directed PR cleanup and release retarget do not waive these release-acceptance failures. The known failures are test_public_dry_run_is_unique_redacted_and_cleans_owned_staging and test_contained_display_dry_run_forwards_no_host_x11 in tests/test_recursive_orchestrator.py.

Earlier physical-host relaunch and recorded recursive E2E passed: a fresh capsule without SSH files or agent cloned the real repository through the inherited host proxy; missing-socket access failed. That recording predates the final review corrections. The retained movie and six-step presentation are local evidence, not GitHub attachments. See the procedure.

Limits: process-lifecycle integration tests depend on Linux /proc, scheduling and a documented 0.5-second fixture-startup allowance. The broker's runtime I/O is not proof of strict Host Inputs separation across the whole subsystem. Desktop transport and broader effect separation remain follow-ups. The human merges this PR into the release; maintenance carries the release to main.

Test coverage, from CI run

Changed lines covered 44% (147 of 327 measured changed lines; 180 uncovered)
Overall devcapsule 87.3% (18,480 of 20,671 statements)

ccozianu and others added 30 commits November 7, 2026 12:32
release-0.3.1 is cut from main at 31e8fec by the owner's decision of
2026-11-07, and the Version Scheme's rule 4 reopens main with the next
development version at the cut, so main is ahead of every candidate. Set
by nox -s bump -- 0.3.2.dev0.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…0.3.2

Reopen main at 0.3.2.dev0 after the 0.3.1 cut
…erge

The release branch sets 0.3.1 in pyproject and adds the source-version
line to docs/versions.yaml, so a clean merge would carry the release
version onto main. This one commit on the copy sets the files back to
what main holds once PR #8 is merged: 0.3.2.dev0 in pyproject and both
WORKFLOW.md frontmatters, and docs/versions.yaml without the
release-branch lines. The copy is deleted on merge; release-0.3.1 is
untouched.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Release 0.3.1: pre-candidate merge for rc0 (throwaway copy of release-0.3.1)
…nd the alternatives

Why real Apple hardware is needed and why Google Cloud and hosted macOS
runners cannot supply it; EC2 Mac as the first run, with prices, the
24-hour rule, the GUI procedure and the Docker Desktop evidence found;
Scaleway as the cheaper second machine; building the three executables on
hosted runners; a one-shot ephemeral self-hosted runner on a
collaborator's Mac and the rules for it on a public repository; and the
smoke to record for 0.3.1, including the Eclipse acquisitions that close
the libsoup bug. Indexed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…e-testing-note

Engineering note: testing the macOS launcher on cloud Mac hardware, and the alternatives
…erge

The release branch carries 0.3.1 in pyproject and the source-version line
in docs/versions.yaml, so a clean merge would carry the release version
onto main. This one commit on the copy sets the four files back to what
main holds: 0.3.2.dev0 in pyproject and both WORKFLOW.md frontmatters, and
docs/versions.yaml without the release-branch lines. The copy is deleted
on merge; release-0.3.1 is untouched.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Release 0.3.1: pre-candidate merge for rc1 (throwaway copy of release-0.3.1)
… move

The owner's ruling of 2026-11-08 on a highlighted discovery test: a module
helper such as read_json is not the public interface of discovery.py, and
replacing it from a test, assuming the operation under test calls it once,
tests the implementation's call shape and not the contract. The order turns
that into checked rules under Unit Tests: a declared public surface for every
module, held like legacy files are held; no patching of project modules in a
conforming test; imports that respect the surface; one line in the briefs. The
first slice is the discovery module, where the pattern was born and eleven
tests across four files copy it. A test-improvements workstream is asked for;
maintenance stays on the 0.3.1 candidates.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ements-work-order

Work order: test improvements, with the discovery module as the first move
…erge

The release branch carries 0.3.1 in pyproject and the source-version line
in docs/versions.yaml, so a clean merge would carry the release version
onto main. This one commit on the copy sets the four files back to what
main holds: 0.3.2.dev0 in pyproject and both WORKFLOW.md frontmatters, and
docs/versions.yaml without the release-branch lines (keeping pyproject's
_webconsole_bundle.zip package-data entry). The copy is deleted on merge;
release-0.3.1 is untouched.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Gemini 4 Argon (High) Antigravity <noreply@google.com>
Merge release-0.3.1 into main before v0.3.1-rc2
Merge release-0.3.1 into main: the pile of ideas and two bug records
Claude's audit of pull request #29: what moving the test suite toward the
stricter standards bought, what it cost, where the rules are wrong, and a
postscript answering the owner's three questions on why LLMs wrote tests
the other way. Released unedited at the owner's word; Part 2 is to be
written together.

Listed in the blog README and the root index.

Co-Authored-By: Claude <noreply@anthropic.com>
…en-hours-part-1

Blog: Thirteen hours, thirty-five tests. Part 1: the AI's audit
…ng and dual navigation

From 91309a7a to 3de4a110, the head of mycodespace-ai/devcapsule-website
main on 2026-11-12: four commits, a fast-forward. They deliver the
restyled site (retro Blueprint and Primer styling, three-column dual
navigation), its work order, and the website repository's own refresh of
its workflow definition to 0.3.1.

The test site is built from this repository's main with the pinned
website commit, so the new styling shows there only once this pointer is
on main.

Co-Authored-By: Claude <noreply@anthropic.com>
…nter-retro-blueprint

Website: advance the submodule to its main (retro-blueprint styling, dual navigation)
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Keep host credentials outside the capsule; gate Git transfer access through github-ssh authorization. Include binary transport, Git process and admission tests.

Co-authored-by: GPT-6 Codex <noreply@openai.com>
Preserve existing registry contracts in the module mirror and cover the optional github-ssh node. All 20 cases pass; no test-convention breaches.

Co-authored-by: GPT-6 Codex <noreply@openai.com>
Treat github-ssh denial as a restriction on both sides of the configuration channel.

Co-authored-by: GPT-6 Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Remove unused frame helper, separate capsule SSH fallback errors from proxy failures, clarify launcher disclosure/CLI help and public surface, and add unit/integration coverage for bridge gating and process-group cleanup.

Co-authored-by: Gemini 4 Hydrogen High Antigravity <noreply@google.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Apply the code and tests from release-0.3.1 commit a1a54eb. Adapt CapsuleUser behavior to this branch's foreground_command and prepare_filesystem APIs; retain GitHub authorization and verify both rootless and rootful proxy plans. Release and maintenance records remain with their owner.

Co-authored-by: Antigravity <noreply@google.com>

Co-authored-by: GPT-6 Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Allow scenario-specific launch needs and consents in the interactive recorder, bound its interactive phase, and retain the procedure and successful rootless proxy E2E evidence.

Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
ccozianu and others added 15 commits November 16, 2026 09:36
Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
Merge upstream release tip 10e7fda at the owner request. Keep the release CapsuleUser/runtime refactoring and retain GitHub proxy authorization, transport and mixed-ID coverage. Unit gate: 3309 passed; three failures remain from the prior baseline. Focused combined checks: 41 passed.

Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
…tory

Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
Co-authored-by: GPT-6 Astra Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Bound the full readiness handshake in _read_ready_line with pipe cleanup, parameterize test_containerized_bridge_requires_an_inherited_canonical_socket per Unit Tests rule 2, and raise the stalled-SSH deadline to 0.5s with explicit fixture-startup assertion.

Co-authored-by: Gemini 4 Hydrogen High Antigravity <noreply@google.com>
Antigravity Gemini 4 Hydrogen High review accepted by GPT-6 Codex after round 2. Corrects diagnostics and disclosure, bounds test readiness and cleanup, and adds parser, authorization and process lifecycle coverage. Two inherited recursive Docker gid-zero unit failures remain disclosed. Implementation PR #47 is directed to release-0.3.1; only the owner merges the release.
@ccozianu ccozianu changed the title Ws GitHub auth/ssh proxy Add opt-in host GitHub SSH proxy for release 0.3.1 Nov 16, 2026
@ccozianu
ccozianu changed the base branch from main to release-0.3.1 November 16, 2026 15:09
ccozianu and others added 2 commits November 16, 2026 15:11
Co-authored-by: GPT-6 Codex <noreply@openai.com>
Co-authored-by: GPT-6 Codex <noreply@openai.com>
@ccozianu
ccozianu merged commit a464088 into release-0.3.1 Nov 16, 2026
5 checks passed
@ccozianu
ccozianu deleted the ws-github-auth/ssh-proxy branch November 16, 2026 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant