garrytan 63a6cbb8ee fix(slug): give nested-group projects their own state bucket and verify checkpoint identity (#3003, #2901) ...

gstack-slug kept only the last two remote path segments, so
customer-a/product/repo and customer-b/product/repo shared one bucket
and /context-restore could present another project's checkpoint.

- One canonical-remote rule (bash + TS, golden vectors) used by all six
  resolvers: lowercased host, no userinfo/port/.git, Azure DevOps and
  Bitbucket Server normalized. 3+ segment remotes get
  <last-two>-<16 hex>; two-segment remotes (all of GitHub) are unchanged.
- Versioned sticky cache (v2:) keeps cache hits git-free.
- context-save stamps the credential-free remote and root;
  context-restore only treats this project's checkpoints as latest,
  reports foreign/unverified ones first, and treats a different root
  with the same remote (Conductor handoff) as information.
- gstack-slug --adopt-legacy copies only files the user confirms.
- question-preference-hook reads the same versioned cache, so never-ask
  preferences fire; unknown identity asks instead of auto-deciding.

2026-10-02 14:49:15 +00:00

..

SKILL.md

fix(slug): give nested-group projects their own state bucket and verify checkpoint identity (#3003, #2901)

2026-10-02 14:49:15 +00:00

SKILL.md.tmpl

fix(slug): give nested-group projects their own state bucket and verify checkpoint identity (#3003, #2901)

2026-10-02 14:49:15 +00:00