Skip to content

chore(memory): salvage uncommitted agent-memory and #317 audit artifacts from stale worktrees#362

Merged
drmoisan merged 2 commits into
mainfrom
chore/salvage-worktree-memories
Jul 19, 2026
Merged

chore(memory): salvage uncommitted agent-memory and #317 audit artifacts from stale worktrees#362
drmoisan merged 2 commits into
mainfrom
chore/salvage-worktree-memories

Conversation

@drmoisan

@drmoisan drmoisan commented Jul 19, 2026

Copy link
Copy Markdown
Owner

chore(memory): salvage uncommitted agent-memory and #317 audit artifacts from stale worktrees

Summary

  • Recovers 15 files of agent-memory and audit-trail evidence that were left uncommitted in completed, merged worktrees before those worktrees are deleted.
  • Adds the three timestamped feature-review audit artifacts (policy-audit, code-review, feature-audit, all 2026-07-11T22-30) for collection-lock-recursion-coverage-317, which were authored in the feature worktree but never committed.
  • Adds six new agent-memory notes (feature-review x2, atomic-planner x1, task-researcher x1, orchestrator x1, atomic-executor x1) and their index entries, recovered from seven .claude/worktrees/agent-* worktree locations and the feature/store-disable-service-261 branch.
  • Extends orchestrator-state-validator-divergence.md with a confirmed finding about --require-complete behavior on resumed epic-child checkpoints (Feature: swordfish-raw-usage-cleanup #310 run).
  • No production code, test code, or build configuration is changed.

Why

Worktree cleanup found these files present only in worktrees whose branches are fully merged. The repository convention is that all audit-trail evidence and agent-memory must be committed; deleting the worktrees without this salvage would have discarded the content permanently.

What Changed

Architecture / How It Fits Together

Not applicable — documentation and agent-memory only; no runtime components are affected.

Verification

Backward Compatibility / Migration Notes

None. Additive documentation and memory files only.

Risks and Mitigations

  • Risk: memory index entries could duplicate existing entries. Mitigation: each new note was verified absent from main (git cat-file -e) before inclusion; index conflicts were resolved by keeping both sides.
  • Rollback: revert the single commit.

Review Guide

  1. docs/features/active/collection-lock-recursion-coverage-317/*.2026-07-11T22-30.md — audit artifacts, largest files.
  2. .claude/agent-memory/** — six new notes plus six index/addendum edits.

Follow-ups

  • Delete the now-redundant worktrees and merged branches (performed in the same cleanup session after this PR merges).

GitHub Auto-close

  • None

drmoisan and others added 2 commits July 18, 2026 21:04
…cts from stale worktrees

Recovered before worktree cleanup: feature-review, atomic-planner,
task-researcher, and orchestrator memory entries left uncommitted in
completed agent worktrees, plus the 2026-07-11T22-30 feature-review
audit artifacts for collection-lock-recursion-coverage-317.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…on note from orphaned worktree directory

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@drmoisan
drmoisan merged commit bd43572 into main Jul 19, 2026
2 checks passed
@drmoisan
drmoisan deleted the chore/salvage-worktree-memories branch July 19, 2026 01:16
drmoisan added a commit that referenced this pull request Jul 20, 2026
…egration branch before final PR

# Conflicts:
#	.claude/agent-memory/feature-review/MEMORY.md
#	.claude/agent-memory/orchestrator/MEMORY.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant