Sprint 17 ceremony: grip

[laynepenney]

Summary

Sprint 17 ceremony PR for grip. All PRs reviewed, merged to sprint-17, tests green.

Changes (7 commits)

Features:

• feat: gr2 apply link operations and state tracking (grip#514, PR feat: gr2 apply link operations and state tracking (grip#514) #527)
• feat: glob-based link patterns in manifest (grip#521, PR feat: glob-based link patterns in manifest (grip#521) #524)

Bug fixes:

• fix: gr branch switches to existing branch instead of silently skipping (grip#401, PR fix: gr branch switches to existing branch (grip#401) #529)

Tests:

• test: TDD specs for gr2 apply remaining scope (grip#514, PR test: TDD specs for gr2 apply remaining scope (grip#514) #526)
• test: regression tests for org URL parsing (grip#429, PR test: regression tests for org URL parsing (grip#429) #528)

Chores:

• chore: sync sprint-17 from main (Sprint 16 ceremony, PR chore: sync sprint-17 from main (Sprint 16 ceremony) #525)
• chore: cargo fmt (ceremony prep, PR chore: cargo fmt (ceremony prep) #530)

Verification

• cargo fmt --all --check: clean
• cargo test: 48 suites, 0 failures, 4 ignored (expected)
• All PRs had 2+ review comments before merge

Premium boundary: core OSS (workspace orchestration primitives)

[laynepenney]

Ceremony review (Opus). 7 commits, all previously reviewed and merged to sprint-17 with 2+ reviews each. cargo fmt clean, 48 test suites pass (0 failures). Commit log matches PR descriptions. grip#401 (branch switch) and grip#429 (org URL) bug fixes verified with regression tests. gr2 apply link operations and glob patterns extend the materialization pipeline. Ready for ceremony merge.

[laynepenney]

Atlas second-pass review: one correctness risk in the new gr2 apply link path. PlanBuild records link ops with src/dest/kind, but not the unit path. Later guard_for_apply() validates link destinations by reading parameters["path"] and otherwise falling back to agents/{unit_name}. That means any unit with a non-default path can be validated against the wrong destination: false-negative if the real target already exists, or false-positive if agents/{name} exists but the real unit path is elsewhere. I think link ops need to carry the unit path explicitly (or validation should look it up from unit_spec the same way apply() does) before this ceremony merge.