Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

Codex/autoreview: CLEAN

Reviewed the exact PR diff for #1882. No blocking findings.

Evidence checked:

• Runtime alias is scoped to $HOME/.claude/skills only.
• Canonical skills/gstack installs are left unchanged.
• Existing separate real skills/gstack installs are not replaced.
• No generated skill bodies are rewritten.
• Regression tests cover renamed install, non-Claude skills dir, and canonical install cases.

Verification from PR body / agent run:

• bun test test/setup-claude-runtime-alias.test.ts test/setup-windows-fallback.test.ts test/setup-sections-linking.test.ts test/setup-conductor-worktree.test.ts PASS, 23 tests
• bash -n setup PASS
• git diff --check PASS
• temp HOME smoke test PASS

Residual risk: GitHub currently reports no checks on this fork draft PR; gh pr view reports mergeable=MERGEABLE.

Possible overlap with #1819 (opened 2026-05-31, Fixes #1202 / addresses #1694) - flagging so the two can be coordinated. #1819 relocates a direct ~/.claude/skills/gstack checkout out to ~/.gstack/repos/gstack and explicitly states it keeps ~/.claude/skills as the alias root, with "a runtime-only sidecar is created later in the Claude install step." This PR adds exactly that runtime sidecar/alias at ~/.claude/skills/gstack via ensure_claude_runtime_alias().

So the two are two halves of the same problem - a renamed or relocated install must still resolve ~/.claude/skills/gstack/... runtime paths (here keyed to #1882 vs #1202/#1694) - and both add new functions to the same setup region near link_claude_root_skill_alias, so they will likely textually conflict. There is also a real question of whether the sidecar/alias ends up created once or twice once both install paths exist. Might be cleanest to land them together (or rebase one onto the other) so the alias/sidecar creation lives in a single place.

Not a blocker on this PR's logic - the ensure_claude_runtime_alias guards (skip the canonical gstack install, skip non-Claude skills/ dirs, refuse to clobber a separate real install) look sound, and the helper-ordering test is a nice touch.