Agreed. The top-level SSH config provisioning path is too much machinery for the specific remote-alias case, and it changes git-gate assumptions more than this bug warrants.
I created #152 for…
Updated in 28cbe40.
The PRD now uses the requested shape:
git.remotesis a simple logical-name to upstream-URL mapping.ssh.known_hostsis a top-level list of OpenSSH known-host…
Agreed. That is a cleaner split, and it keeps the manifest from having three different host-resolution mechanisms hidden under git.remotes.
I’ll update the PRD around this shape:
git:
…
Yes, this is the cleaner shape. SSH config should be a top-level bottle capability, not nested under a specific git remote.
That gives us a clearer split:
git:
remotes:
gitea.dideri…
Design sketch after reading the current Docker/smolmachines paths:
Proposed abstraction: WorkspacePlan
Introduce a backend-neutral workspace plan resolved during prepare, then let each…
Acknowledged. I’ll keep the render contract failure as a plain ValueError for now and avoid adding a dedicated exception type in this PR.
Acknowledged. I’ll set the default supervise operator-response wait budget to 30 seconds and keep it configurable by env.
Thanks, I’ll implement those decisions in PRD 0034: repeated restart requests will coalesce by daemon name, and exit-code handling will clamp signal-only shutdown outcomes to 0 while preserving…