[wz-gsa]

Summary

• Route a bare opencode invoked outside PID 1 to the real OpenCode binary; keep the PID-1 shim entrypoint and argument passthrough.
• Reject wrapper symlink/hard-link aliases and tighten the Paseo verifier so skipped or incomplete checks do not produce a measured pass.
• Document backend-dependent lifecycle and port behavior; cover wrapper dispatch, guest path spellings, and verifier verdicts with offline fixtures.

Eligibility & Accountability

• I am a federal employee or contractor (author-of-record attestation for human confirmation).
• I understand this change and can explain it in my own words (author-of-record attestation for human confirmation).
• I have the right to release this work under CC0-1.0 (author-of-record attestation for human confirmation).

AI Assistance Disclosure

• AI tools were used: OpenCode helped implement, test, document, and review this change.
• Human author verified all AI-generated content and release rights; human confirmation remains required.
• No third-party material was copied into this change.

Type of Change

• New tool/editor integration (integrations/) update
• Documentation update
• Bug fix

Motivation

In #548, MSB runs the wrapper outside PID 1; the old no-argument route printed Paseo connect instructions and returned instead of opening the OpenCode TUI. A shell invocation should not repin the daemon worktree root.

Testing and validation

• make validate passed in an isolated managed Ubuntu VM on exact tree ff9ce4d111d5d92f397feec40e7a43d2ccd64e80 (47/47 pattern files; existing advisory warnings).
• 78/78 Paseo Node tests passed in a network-disabled, non-root, read-only container.
• Managed VM pre-commit hooks passed on the exact tree, including acq-kit validation and Gitleaks; local push hook also scanned the 20-commit history without leaks.
• Commits follow Conventional Commits and are signed; fixed-SHA independent agent QA/security static reviews found no new scoped blocker at 35efa98b74caa55a0161ea6505bcaebec33c4596.
• Tested in a live MSB sandbox: PID-1 hold, real TUI routing, host-to-guest mount mapping, and same-daemon host identity remain unverified. The detached verifier deliberately returns exit 3 for skipped checks.

Safety checklist

• Reviewed changed files for secrets, credentials, PII, CUI, internal infrastructure, and proprietary data; no such material identified.
• No new pattern/output contract is introduced.

Reviewer notes

Review the wrapper PID-1/no-argument split and the verifier’s skip/transport classifications at this head. Independent agent reviews are supporting evidence, not a GitHub CODEOWNER approval. The pre-existing shim readiness fallback, mount registrar symlink boundary, and host-daemon identity check are separate concerns and are not claimed fixed here.

Related issues

Relates to #548. Human/live acceptance is pending before closure.

[basiliskus]

Verdict: request changes — 35efa98b74caa55a0161ea6505bcaebec33c4596

Must fix before merge: Fix the cache probe's newline handling and cover its actual output.

• major — integrations/isolation/acq-kits/paseo/scripts/verify:638–643: A healthy agent-owned cache is reported as a failure. When find returns no foreign-owned file, printf "%s\n" "$result" still emits a newline before CACHE_PROBE_DONE. Removing only the marker leaves that newline, so [ -n "$bad_cache_owner" ] is true and the live verifier records a failure (exit 1). Confirmed by executing the actual guest probe against an empty, current-user-owned .npm; the same fixture passes at the base revision. Emit the separator only for a nonempty result, or remove the exact separator along with the marker. Add a regression test that executes the real probe: the existing fixture supplies CACHE_PROBE_DONE without the newline and misses this case.

Assisted-by: OpenCode [GPT 6.1 Sol Latest Guardrails Defaultv2] skill:change-review

[basiliskus]

Verdict: approve — 475aa0a5244c62df268e3b3de24f17a02a8ad2dd

Must fix before merge: none.

The prior cache-probe finding is resolved in 475aa0a5: empty results no longer leave a separator, and the real-probe regression reproduces the old failure and passes with the fix. No new findings.

Live PID-1 hold, real TUI routing, mount transport, and same-daemon identity remain unverified; this review does not replace that acceptance work.

Assisted-by: OpenCode [GPT 6.1 Sol Latest Guardrails Defaultv2] skill:change-review