syntaqxThe g1t CLI is 0.3.3: any harness reads and acknowledges its coordination updates. `g1t session updates [ID]` lists what other sessions did that concerns this one (claims, overlaps, dependency changes, decisions, merge queue results), which reading never clears; `g1t session acknowledge ID... --note TEXT` records the decision about them and clears exactly those IDs for this session (`--session` names another of yours), and says when an ID was not this session's. `session updates`, `acknowledge` and `heartbeat` first say which files the working copy changed (git status), so another session changing the same files is an overlap.detected for both, whatever harness either runs in (G1T_TOUCH=0 turns it off). The CLI guide lists both commands. Checked: cargo test -p g1t (105 and 44, the command reference current).22641e9History
- ..
- activity.test.ts
- activity.ts
- answer.test.ts
- answer.ts
- cards.test.ts
- cards.ts
- clear.test.ts
- clear.ts
- emoji.test.ts
- emoji.ts
- erasure.ts
- g1t.test.ts
- g1t.ts
- index.ts
- internal.test.ts
- internal.ts
- mentions.test.ts
- mentions.ts
- messages.test.ts
- messages.ts
- names.test.ts
- names.ts
- notify.test.ts
- notify.ts
- room.ts
- settings.test.ts
- settings.ts
- standard-emoji.ts
- unread.test.ts
- unread.ts