basquetWi + New ticket

Survey lezama for shared-mutable-file contention between agents (incl. CLAUDE.md, commons .md, pm/)

Done normal nlnw-lezama-cc

HOST: lezama. Elazar GO 2026-08-31, child of OPS-156. SURVEY YOUR OWN HOST for the contention pattern OPS-156 describes, then FILE YOUR FINDINGS AS CHILD ITEMS UNDER OPS-156 (one child per distinct contended surface, not one child for the whole survey) so each gets tracked and closed on its own. WHAT TO LOOK FOR: any file or directory that more than one agent writes, with no isolation between them. The signal is agents coordinating ABOUT the file instead of the file being safe to edit - DMs saying "do not touch X while I am in it", "pull before you edit", "I left changes in Y", stray uncommitted entries belonging to another lane, or a documented convention that exists only to stop two agents colliding. SURFACES EXPLICITLY IN SCOPE, including pure-.md ones - a docs collision is the same defect and costs the same coordination: - global CLAUDE.md and the ~/.claude/*.md rule files (note: on venus these are TRACKED SYMLINKS into sh.git, so editing one is editing the shared repo) - per-project commons/shared .md, design docs, guides - pm/ directories and PM-owned planning files - any shared checkout, shared state dir, shared sqlite, or shared config that two agents write - shared systemd unit dirs and .llmmsg-env style overlays FOR EACH FINDING RECORD: the path; which agents write it; how collisions are currently prevented (convention, DM, lock, luck); whether a collision has actually occurred and the evidence; and whether the fix is isolation (separate trees/files per agent), single-ownership (one named writer, everyone else read-only), or generation (the file is built from a source, not hand-edited). A NIL RETURN IS A RESULT, BUT IT MUST BE EVIDENCED. "No contention on this host" needs to say what you looked at and what you did NOT exercise. Absence of a reported collision is not absence of contention - most of these are invisible until two agents happen to write in the same minute. Do not fix anything under this item without saying so on its child first; some of these have an owner who has not been asked.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • wi-cli-venus created · 6w ago
    parent=#3095
  • wi-cli-venus completed · 6w ago
    Surveyed lezama. Two children filed under OPS-156: OPS-169 (sh.git ~/.local/bin - same shape as parent, evidenced version-string collision 2026-08-30 on rutap-watch.sh) and OPS-170 (systemd --user unit dir - shared namespace, nil collision evidenced via list-units/list-timers + mtime cross-check, ownership lane already covered by maintainer registry). CHECKED per the two-correction warning: ~/.claude/*.md ARE tracked symlinks into sh.git on lezama too (verified via ls -la, not just assumed - readlink shows agent-conventions.md/maintainer-agents.md/measurement-discipline.md/etc pointing into ~/.local/bin), confirming the parent case's exact shape here, not just on venus. host-checks.sh (~/.local/state/sys-check/, not git-tracked) checked and cleared: single owner via maintainer registry (my row, backup bin-lezama-cc), not multi-writer. .claude/settings.local.json: git-tracked, bin-lezama-cc has a blocking action in flight per your note - not touched, not surveyed further, deferring to that lane. No GCABA-side surface found in scope this survey.
audit
6w ago by wi-cli-venus
6w ago
2026-08-31 04:40