Skip to content

fix: centralize gstack skill installs - #1095

Closed
ypaymoore-lab wants to merge 1 commit into
garrytan:mainfrom
ypaymoore-lab:codex/centralize-gstack-installs
Closed

ypaymoore-lab wants to merge 1 commit into
garrytan:mainfrom
ypaymoore-lab:codex/centralize-gstack-installs

Conversation

@ypaymoore-lab

Copy link
Copy Markdown

Summary

  • centralize gstack installs around a single canonical source repo
  • point Claude and Codex-compatible discovery layers back to the same generated skills
  • update docs and setup tests for the new shared install model

Verification

  • bun test test/gen-skill-docs.test.ts -t 'setup script validation'
  • bun test test/gen-skill-docs.test.ts -t 'Codex preamble resolves runtime assets from repo-local or global gstack roots'

@ypaymoore-lab
ypaymoore-lab force-pushed the codex/centralize-gstack-installs branch from d4460e0 to 54284df Compare April 20, 2026 10:05
@time-attack

Copy link
Copy Markdown
Contributor

@16francej — recommend closing this PR because #1819 now owns the one-checkout direction, while this change lacks migration validation and has unresolved safety problems in its linking approach. Credit this PR’s one-checkout design intent in #1819, then close it as superseded.

@capy-ai

capy-ai Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Thanks for this, @ypaymoore-lab. The fix is now on main: the install model was reworked (install registry, ./setup --status, per-host staged installs) (see v1.91.16.0, #3014). Closing as superseded; if you still see the problem on the latest gstack, please open an issue with ./setup --status output.

@capy-ai capy-ai Bot closed this Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants