chore(memory): consolidate stranded agent-memory commit from merged worktrees

[drmoisan]

Suggested title

chore(memory): consolidate stranded agent-memory commit from merged worktrees

Summary

• Consolidates one stranded agent-memory commit onto a dedicated documentationandmemories branch so it can land on main before the source worktree/branch is deleted.
• The commit was appended to worktree-agent-a3af2b2b1cd3149ba after that branch's feature content had already merged, so it was never reachable from main.
• No production code, tests, or build configuration are touched; this is a documentation/agent-memory-only change.
• Produced by the /cleanup-merged-worktrees workflow's editorial triage and consolidation step, run against local branches/worktrees on 2026-08-28.

Why

Several drm-copilot-wt-*/agent worktree branches accumulated documentation or agent-memory commits after their feature work had already merged into main. Deleting those branches outright would silently drop that content. The cleanup workflow requires such content to be consolidated onto main before the source branches are removed.

What Changed

Docs/agent-memory:

• .claude/agent-memory/orchestrator/MEMORY.md — adds one index line pointing to the new memory entry below.
• .claude/agent-memory/orchestrator/prepared-epic-child-invalidated-by-sibling-merge.md (new) — records the lesson that a prepared epic child can be invalidated by a sibling's merge.

No other files are touched.

Architecture / How It Fits Together

This branch was created off main in a dedicated worktree and received exactly one cherry-picked commit (-x provenance preserved) from the stranded source branch. It carries no other history changes.

Three additional candidate commits from a second stranded branch (worktree-agent-ab754ef5080070b0e) were evaluated and deliberately excluded:

• Two touched docs/features/active/quickfiler-keyboard-action-defects-444/{plan,spec}.md — early drafts of a feature-doc folder that already exists on main in a far more complete, closed-out form (issue, plan, spec, audits, evidence). Cherry-picking one of them produced a real conflict against that existing folder, confirming the content was superseded rather than missing.
• One touched .claude/agent-memory/orchestrator/prd-feature-hook-longest-path-token.md — the same underlying lesson is already recorded on main under prd-feature-hook-parses-prompt-paths.md, in more detail and with a documented incident. Consolidating the duplicate was judged not worthwhile.

Verification

Completed:

• git merge-base --is-ancestor / cherry-pick applied cleanly for the one consolidated commit (confirmed via git log on the consolidation branch).
• Diff reviewed: 2 files changed, 40 insertions(+), 0 deletions(-), both under .claude/agent-memory/.

Recommended:

• No code toolchain applies (docs/memory-only change); no build, lint, or test run is required.

Backward Compatibility / Migration Notes

None. No production code, schema, or public API is touched.

Risks and Mitigations

• Risk: none identified — the change is additive documentation content with no runtime effect.
• Mitigation: N/A.

Review Guide

• Single-commit diff; review MEMORY.md's one added line and the new memory file in full — both are short.

Follow-ups

• After this PR merges, the source worktree/branch worktree-agent-a3af2b2b1cd3149ba (and the other now-fully-classified branches from this cleanup pass) become eligible for deletion via bash scripts/bash/cleanup-worktrees.sh --apply.

GitHub Auto-close

• None (GitHub CLI unavailable in this environment; no verified or author-asserted autoclose issues in context).