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
- ..
- invites
- access.rs
- account_deletion.rs
- admin.rs
- aliases.rs
- ask_tokens.rs
- avatars.rs
- crypto.rs
- deletion.rs
- deploy_keys.rs
- device.rs
- directory.rs
- dock.rs
- email.rs
- emails.rs
- github.rs
- invites.rs
- job_tokens.rs
- lib.rs
- members.rs
- oauth.rs
- paid.rs
- people.rs
- privacy.rs
- profiles.rs
- purge_job.sql
- purge_jobs.rs
- rename.rs
- run_credentials.rs
- security.rs
- shared_invites.rs
- sounds.rs
- suspension.rs
- teams.rs
- throttle.rs
- token_reach.rs
- tokens.rs
- two_factor.rs
- workspaces.rs