You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
audit: remove the fusion pitfall bullet added by #13 #16
Putting a Fusion model in a role. A fusion-* slug names a lead and sidekick pair for the main chat, so pstack rejects it and falls back to the role's default. Pick the lead's or the sidekick's own slug, like claude-opus-5-5-max or swe-2-high.
why devin doesn't require it: the harness rule (drop fusion-* from detected slugs, treat it as a rejected slug) already lives in skills/setup-pstack/SKILL.md step 1 and in the routed skills. This bullet is an extra guide note with no upstream source. I asked for it to be removed in my review of #13, which merged with it still in.
smallest fix: delete line 175.
found by the whole-port audit against upstream 88d4751 (pstack 0.15.29). fix with Closes #16.
Activity