Repository navigation
memory: v4.42.1 shipped and rolled out; the family-upgrade worktree rule becomes a Key Decision - #16
Merged
Merged
Conversation
…ion 2026-10-04-164714 [Claude Code]) Release v4.42.1 tagged on 5c24afb and published; Mode B 4.42.0 → 4.42.1 via throwaway worktrees: mercury-composable #505, mercury #353, mercury-python #39, mercury-nodejs #107 — all merged, post-merge agent-memory floor green on all four. Re-copied files were stock 4.42.0 everywhere; every target protocol byte-identical to the 4.42.0 template (re-copied). Local consulted-reference conventions left to their maintainer. First log here under the v4.42.1 rule: references declare facts relied on, not only edited. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ion 2026-10-04-165030 [Claude Code]) The rule — every family-repo upgrade runs in a throwaway git worktree of origin/main, unconditionally — lived only in the 2026-09-18 session logs, so the v4.42.1 rollout had to recover it from them. New fact family-upgrade-worktree-path: the rule, the v4.41.1 stale-snapshot incident behind it, and the mechanics (fresh agent-memory-v<version> branch, --forge github, hook item checked in the main checkout, worktree removed after push, local branch deleted after merge only on an ancestry or squash tree-equality check). No live or archived fact mentions worktrees. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
acn-ericlaw
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Session log
memory/sessions/2026-10-04-164714.mdrecording the v4.42.1 release and its rollout:Release: PR v4.42.1: declare a fact consulted to make a decision; check for declaration gaps before archiving one #15 merged as
5c24afb; tagv4.42.1on the merge commit; release published and marked Latest; post-mergedocs/tests/agent-memorygreen.Rollout (Mode B 4.42.0 → 4.42.1, throwaway worktrees, no checkout touched): chore(agent-memory): upgrade 4.42.0 → 4.42.1 — declare a fact consulted to make a decision; check for declaration gaps before archiving one mercury-composable#505, chore(agent-memory): upgrade 4.42.0 → 4.42.1 — declare a fact consulted to make a decision; check for declaration gaps before archiving one mercury#353, chore(agent-memory): upgrade 4.42.0 → 4.42.1 — declare a fact consulted to make a decision; check for declaration gaps before archiving one mercury-python#39, chore(agent-memory): upgrade 4.42.0 → 4.42.1 — declare a fact consulted to make a decision; check for declaration gaps before archiving one mercury-nodejs#107 — all merged; post-merge
agent-memoryfloor green on all four. Re-copiedDECAY.md/REVIEW.md/.agent/schema.mdwere stock 4.42.0 everywhere; every target protocol was byte-identical to the 4.42.0 template and was re-copied.The two local consulted-reference conventions (mercury-composable, mercury) left untouched — pointer-shrink is their maintainer's call.
Key Decision
family-upgrade-worktree-path(second commit, session2026-10-04-165030.md, at the maintainer's request): every family-repo upgrade runs in a throwawaygit worktreeoforigin/main, unconditionally — the rule, the v4.41.1 stale-snapshot incident behind it, and the mechanics (--forge github, the hook item checked in the main checkout, worktree removed after push, local branch deleted after merge only on an ancestry or squash tree-equality check). It had lived only in the 2026-09-18 session logs.No other continuity edit: the status line already reads v4.42.1.
Why
The release and rollout are project-state events, and this is the first log in the tool's own repo written under the rule v4.42.1 ships — its
## Memory Referencesdeclare the facts the rollout relied on to decide (protocol propagation, the warn-before-clobber check, scope, the org-home workflow), not only facts it edited. It also leaves the next review its first candidates for the new step-6 subject read (four facts already[overdue]). The worktree rule is the operational lesson behind three clean rollouts, and an agent should find it in the per-session read path rather than dig it out of logs.Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
🤖 Generated with Claude Code