Distillation

Date: Sep 8, 2026

• 🟡 (06:49) Investigation of github.com/coreos/go-systemd/v22@v22.5.0/dbus confirmed relevant APIs: StartTransientUnitContext(...) at dbus/methods.go:191, StopUnitContext(...) at line 122, GetUnitPropertiesContext(...) at line 272, GetUnitTypePropertiesContext(...) at line 347, and property helpers PropExecStart(...), PropType(...), PropBindsTo(...), PropAfter(...), and PropSlice(...) in dbus/properties.go.
• 🟡 (06:49) StartTransientUnitContext(ctx, name, mode, properties, ch) creates and starts a uniquely named transient unit through org.freedesktop.systemd1.Manager.StartTransientUnit; the unit is released once it is no longer running or referenced, or upon reboot.
• 🟡 (06:49) GetUnitPropertiesContext(...) reads org.freedesktop.systemd1.Unit properties; GetUnitTypePropertiesContext(...) reads type-specific properties using org.freedesktop.systemd1.<unitType>, where valid types include Service, Socket, Target, Device, Mount, Automount, Snapshot, Timer, Swap, Path, Slice, and Scope.
• 🟡 (06:49) Confirmed transient-unit property behavior in dbus/properties.go: PropExecStart(command, uncleanIsFailure) uses command[0] as the executable path and the complete command slice as arguments; PropType(t) sets Type; PropBindsTo(...) sets BindsTo; PropAfter(...) sets After; and PropSlice(slice) sets Slice.
• 🔴 (06:50) User stated systemd start-job mode replace may replace already queued jobs that conflict with the requested start.
• 🟡 (06:50) github.com/coreos/go-systemd/v22@v22.5.0/dbus job modes are replace, fail, isolate, ignore-dependencies, and ignore-requirements: replace may replace conflicting queued jobs; fail refuses changes to an already queued job; isolate terminates units that are not dependencies; ignore-dependencies ignores all dependencies; and ignore-requirements ignores only requirement dependencies. The latter two modes are not recommended.
• 🟡 (06:50) A non-nil systemd job result channel can receive exactly one of done, canceled, timeout, failed, dependency, or skipped; startJob(...) registers the channel by returned D-Bus job object path and derives the numeric job ID from that path.
• 🟡 (06:51) Standard Go test run passed: cmd/supervisor had no test files; cmd/client passed in 0.220s; cmd/launcher passed in 1.067s; internal/protocol passed in 0.007s; and internal/supervisor passed in 2.595s.
• 🟡 (06:51) A second test run also passed: cmd/supervisor had no test files; cmd/client passed in 2.241s; cmd/launcher passed in 2.097s; internal/protocol passed in 1.031s; and internal/supervisor passed in 3.614s.
• 🟡 (06:51) First clean source rebuild under /tmp/opencode/pty-review.DL0iOT produced SHA-256 values opencode-pty-supervisor = b8f1914dfea234ec86c74cc9d4c087c3b6db4a8f333d1f1d2624238745db366a, opencode-pty-launcher = d4f483d2f5824137da5a11c798f4ef7b2b13261954236488eaf6fa4d290d8d0c, and opencode-pty-client = b6cd329200d5dae973f6a53a486d0ae90e938ee26703ed39c2f11eebf385ace3.
• 🟡 (06:51) All 3 rebuilt binaries differed byte-for-byte from the shipped binaries despite matching Go and module metadata; investigation separated two hypotheses: stale shipped binaries versus nondeterministic builds.
• 🟡 (06:52) Second clean rebuild under /tmp/opencode/pty-review.tzR3OV produced the same SHA-256 values as the first rebuild for all 3 binaries, proving the rebuilds are deterministic and ruling out nondeterministic compilation as the explanation for the shipped-binary mismatch.
• 🟡 (06:52) Rebuilt Go build IDs were opencode-pty-supervisor = X7uuC5VQs-Pi-CM5KkWZ/kkhua8CfrFuCgWTs5SIN/ooGNSymP4_kEy3kieQO8/u-09TBWm-qCHm6OuWF0g, opencode-pty-launcher = VWY-fgfTf2y2Get3IcVr/LdudBBCNOyYpTUXtFrXm/7lnZocARUX26Z8ZDflb3/KJMRsdPNiEq9OM7-6vAp, and opencode-pty-client = FmYup255hQfTyKyM0npi/FXLWPxcEl0Lalgu7xkay/CJz4EzsssM_mihTcrsGt/2rrPRVzHq3ixsrtHJZHw; shipped binaries exposed empty build IDs.
• 🟡 (06:52) Investigation outcome: reproducible current-source binaries do not match the shipped binaries, supporting the stale/out-of-sync shipped-binary hypothesis rather than nondeterministic-build behavior.