Adopt cli-guard passthrough: audited git verbs incl. concurrency-safe commit #59

New issue

Closed

opened 2026-06-06 04:05:53 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-06 04:05:53 +00:00

Owner

Summary

Adopt cli-guard's passthrough framework to give ward audited git verbs for contributors, including coily's concurrency-safe git commit.

Motivation

Ward gates build/test/vet/lint/tidy/cover but not the git operations a contributor actually performs to land work. coily wraps git {status,log,diff,show,add,fetch,pull,push,branch,checkout,stash,restore} as audited passthroughs and ships a dedicated, concurrency-safe git commit verb (private GIT_INDEX_FILE seeded from HEAD, editor forbidden, named paths only) so two sessions sharing one working tree cannot cross-contaminate the index or commit message. That commit-safety property is exactly what a multi-agent contributor gate needs.

Scope

Import cli-guard/passthrough.
Add audited ward git passthrough verbs for the read/safe set (status,log,diff,show,add,fetch,pull,push,branch,checkout,stash,restore).
Port the concurrency-safe git commit verb (ward git commit -m "msg" -- <path>...).
Audit rows under the existing ~/.coily/audit/<repo>.jsonl scheme, git.* verb prefix.
Update docs/FEATURES.md.

Out of scope

coily ops gh (gh lives operator-side; ward grows no ops verbs). Org-resolution / dispatch machinery.

Boundary check

Contributor-safe: git is the contributor's core dev surface. Depends conceptually on the gittree work (#gittree) for the dirty/synced gating that several of these verbs respect.

## Summary Adopt cli-guard's `passthrough` framework to give ward audited `git` verbs for contributors, including coily's concurrency-safe `git commit`. ## Motivation Ward gates `build`/`test`/`vet`/`lint`/`tidy`/`cover` but not the git operations a contributor actually performs to land work. coily wraps `git {status,log,diff,show,add,fetch,pull,push,branch,checkout,stash,restore}` as audited passthroughs and ships a dedicated, concurrency-safe `git commit` verb (private `GIT_INDEX_FILE` seeded from HEAD, editor forbidden, named paths only) so two sessions sharing one working tree cannot cross-contaminate the index or commit message. That commit-safety property is exactly what a multi-agent contributor gate needs. ## Scope - Import `cli-guard/passthrough`. - Add audited `ward git` passthrough verbs for the read/safe set (`status,log,diff,show,add,fetch,pull,push,branch,checkout,stash,restore`). - Port the concurrency-safe `git commit` verb (`ward git commit -m "msg" -- <path>...`). - Audit rows under the existing `~/.coily/audit/<repo>.jsonl` scheme, `git.*` verb prefix. - Update `docs/FEATURES.md`. ## Out of scope `coily ops gh` (gh lives operator-side; ward grows no ops verbs). Org-resolution / dispatch machinery. ## Boundary check Contributor-safe: git is the contributor's core dev surface. Depends conceptually on the gittree work (#gittree) for the dirty/synced gating that several of these verbs respect.

coilysiren added the

sunday-sprint

labels

2026-06-06 04:16:40 +00:00

coilysiren referenced this issue from a commit

2026-06-06 05:06:42 +00:00

feat(git): add audited git verbs incl. concurrency-safe commit

coilysiren closed this issue

2026-06-06 05:06:42 +00:00