memory: version-currency rule covers inheriting existing pins (Aaron 2026-04-27)

[AceHack]

Summary

Files a lesson memory: Otto-247 version-currency rule (CLAUDE.md wake-time discipline #4) applies whenever a version pin LANDS in a new file, not just when proposing a fresh version number. Caught during the autonomous-loop tick fixing PR #25's gha-action-mutable-tag finding — Otto inherited actions/checkout@de0fac2... # v6.0.2 from gate.yml without WebSearch-verifying it was current. The pin happened to be correct (v6.0.2 IS latest per gh api repos/actions/checkout/releases/latest, published 2026-01-09), but skipping the discipline was the failure mode.

The memory captures the refined rule, the API-over-narrative verification preference, and a pre-mortem signature for next-Otto.

Test plan

• markdownlint passes
• memory/MEMORY.md row pairs with the new file (mandatory pair per CLAUDE.md memory-index-integrity rule)
• No Aaron-by-name attribution outside the closed-list history surfaces (memory/ is allowed)

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Copilot]

Pull request overview

Adds a new lesson-memory clarifying that the version-currency rule applies when copying an existing version pin into a new file (i.e., inheriting a pin still counts as asserting it’s current), and indexes that memory in memory/MEMORY.md.

Changes:

• Adds a new memory entry documenting the refined “version currency even on inherited pins” rule and a suggested verification workflow.
• Updates memory/MEMORY.md to include and summarize the new memory entry.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
memory/feedback_version_currency_covers_inheriting_existing_pins_not_just_fresh_assertions_aaron_2026_04_27.md	New memory write-up capturing the refined rule and suggested verification steps.
memory/MEMORY.md	Adds a new index bullet linking/summarizing the new memory entry.

[AceHack]

Closing as superseded by PR #681.

5-disciplines audit summary (per memory/feedback_destructive_git_op_5_pre_flight_disciplines_codex_gemini_2026_04_28.md):

• Discipline 1 (history preservation): branch acehack/memory/version-currency-inherit-pins-lesson-2026-04-27 survives this close. Content recoverable.
• Discipline 2 (per-blob subsumption): VERIFIED — memory/feedback_version_currency_covers_inheriting_existing_pins_not_just_fresh_assertions_aaron_2026_04_27.md IS on main as of PR memory(version-currency): inheriting existing pins counts as fresh assertion (rebased from #656) #681 (merged 2026-04-28T19:30:52Z), with the same 91-line content extracted from this branch's tip.
• Discipline 3 (commit messages): lineage preserved in PR memory(version-currency): inheriting existing pins counts as fresh assertion (rebased from #656) #681's commit message which references "Rebased from PR memory: version-currency rule covers inheriting existing pins (Aaron 2026-04-27) #656".
• Discipline 4 (force-with-lease): N/A — PR close is not a force-push.
• Discipline 5 (freshness): branch ref freshly fetched + verified.

Why rebased rather than merged directly: this PR's 4-commit history hit MEMORY.md conflict-cascade on each commit during rebase (the index-position of the new entry shifted with each subsequent landing). Clean-extracting from branch-tip + single new commit avoided the rebase-conflict resolution risk. Inline lesson logged in PR #681's commit message.