The entry cited `ddb38f37`, which does not exist on this branch. My instruction to the implementer asked a commit to record its own SHA — a git impossibility, since a commit hash covers its own content. The implementer committed, then amended the SHA into the text, and the amend necessarily produced a different final hash; it flagged the contradiction rather than leaving it to be discovered. Corrected to the real commit and recorded here as its own docs commit, which is the pattern #314 already uses (fix commit, then a separate closing note citing it). A wrong SHA in ISSUES.md is worse than no SHA: it is a citation a later session trusts and cannot resolve. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
aaf0811f18
commit
30d3d114b0
1 changed files with 1 additions and 1 deletions
|
|
@ -148,7 +148,7 @@ split result places normally instead of throwing.
|
|||
|
||||
## #315 — `runTeleportHook` builds a `Func<bool>` closure per network packet
|
||||
|
||||
**Status:** CLOSED 2026-08-04 by `ddb38f37` — the OnPosition collapse
|
||||
**Status:** CLOSED 2026-08-04 by `aaf0811f` — the OnPosition collapse
|
||||
converged the three `RunRemoteArmTail` call sites into one, which is what
|
||||
made caching worthwhile. The one remaining call site now passes two
|
||||
delegates cached ONCE at construction (`RemoteArmCallbacks`, a small nested
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue