Friction cluster: agents-md-logbook-lifecycle (1 report)

[hcross]

Friction cluster: agents-md-logbook-lifecycle

1 friction tagged across the harness-friction wing (2026-05-14 (single day)). Routed to https://github.com/hcross/crewrig.

Pattern

Reports span room process. The common subcategory anchor is agents-md-logbook-lifecycle.

Frictions

1. AGENTS.md does not specify that logbook issues must be closed when implementation is complete
   • Reported by: claude-code
   • Severity: med
   • Room: process
   • Evidence: AGENTS.md
   • Suggestion (from reporter): AGENTS.md documents the logbook issue creation contract (every PR must be linked to a logbook issue) but says nothing about the closing lifecycle. As a result, agents never close logbook issues after merge, leaving them as permanent open noise. The fix is a one-line addition to the "Logbook Issues" section of AGENTS.md: "Close the logbook issue after the PR is merged and the feature issue (if any) is closed." The pr-logbook skill should also reflect this — when composing the squash-merge commit message or post-merge summary, it should close the logbook issue.

Suggested resolution

All reporters converge on: AGENTS.md documents the logbook issue creation contract (every PR must be linked to a logbook issue) but says nothing about the closing lifecycle. As a result, agents never close logbook issues after merge, leaving them as permanent open noise. The fix is a one-line addition to the "Logbook Issues" section of AGENTS.md: "Close the logbook issue after the PR is merged and the feature issue (if any) is closed." The pr-logbook skill should also reflect this — when composing the squash-merge commit message or post-merge summary, it should close the logbook issue.

Out of scope

This issue was auto-generated by the Harness Curator (V0). It is descriptive only — a follow-up MR (human-authored, or via the auto-fix mode tracked in #42) will close it with the actual diff.

[hcross]

2026-05-14 — Logbook closing lifecycle codified

Context: PR fix/issue-103-logbook-closing-lifecycle implementing #103. The friction was that logbook issues were piling up in the open state after merge because no rule said who closes them or when.

What was tried: Added a short closing-lifecycle clause to AGENTS.md (3 lines) and a new §7 "Post-merge cleanup" to the three pr-logbook SKILL.md mirrors (.claude/, .gemini/, community-config/). §7 instructs the agent to close the logbook issue via gh issue close --reason completed or the GitHub MCP issue_write tool, and — when the §4 upstream-check path was used — to verify the feature issue's auto-close rather than create a redundant close. Provenance version bumped on the canonical source (community-config/skills/pr-logbook/SKILL.md).

Outcome: Green — diff is 4 files, +57/−3, scoped strictly to the lifecycle clause (see git show 19587c0 --stat). No behavioural code changed; this is a contract clarification.

Lesson: Lifecycle rules belong both in AGENTS.md (project-wide visibility) and in the skill that executes them (point-of-use). Documenting in only one spot leaves the other audience blind — agents read SKILL.md, humans read AGENTS.md.

Post-merge action (per §7 of the very rule introduced here): this issue will be closed with state_reason: completed once the PR squash-merges into main.