https-only-test #

This repository was created and populated entirely over HTTPS, from a sandbox with outbound port 22 blocked. No SSH was used at any point.

• sh.tangled.repo.create (knot XRPC) created the bare repo
• com.atproto.repo.putRecord published the sh.tangled.repo record
• git push over HTTPS landed the commits, authorized by a service JWT with lxm sh.tangled.repo.push

Auth for the knot calls was an atproto inter-service JWT minted via com.atproto.server.getServiceAuth, audience did:web:knot1.tangled.sh.

See SKILL.md for the full recipe and the gotchas found along the way — chiefly that knot1 runs the Rust knot2, whose HTTP push support differs from the older Go knotserver.