8616839cab
CHANGELOG promotion was a manual operator step that was never run, so 463 fragments for work already shipped in <=1.3.1 accumulated in .changeset/. Their notes were already hand-curated into the dated [1.2.0]/[1.3.0]/[1.3.1] CHANGELOG sections (#690 backfill, PR #694). Rendering them now would duplicate and mis-attribute shipped work. Move them to .changeset/archived/ (read non-recursively by all changeset tooling, so never rendered), keeping only the 3 genuinely-unreleased fragments at the top level. Prep for wiring `render` into the release finalize job (#690 follow-up). Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
1.1 KiB
type, pr
| type | pr |
|---|---|
| Fixed | 3097 |
Executor agents now detect and halt on cwd-drift out of worktrees (#3097) — when a Bash call cd'd out of a worktree, [ -f .git ] became false (main repo's .git is a directory), silently skipping all HEAD/branch guards and allowing commits to land on the main repo's branch. Adds step 0a (cwd-drift sentinel using git rev-parse --git-dir + a per-worktree sentinel file at .git/worktrees/<name>/gsd-spawn-toplevel) to gsd-executor.md's task_commit_protocol. Closes #3097.
type: Fixed pr: 3099
Executor agents now detect absolute paths that resolve outside the worktree (#3099) — absolute paths constructed from the orchestrator's pwd (main repo root) resolved to the main repo when used in Edit/Write calls from a worktree, silently losing work. Adds step 0b (absolute-path guard using WT_ROOT=$(git rev-parse --show-toplevel)) with a clear warning and instructions to prefer relative paths. Both guards are documented in references/worktree-path-safety.md (loaded into every executor spawn prompt via <execution_context>). Closes #3099.