v1 plan: fix TestPinAndUnpin event assertion (positions -> order and content); note the finding

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-25 04:05:02 -07:00
parent 0874e00bdd
commit 29b3a5c38e
2 changed files with 25 additions and 2 deletions
@@ -77,3 +77,9 @@ tools/run-plan.sh docs/plans/v1          # from a clean checkout on master
  files were protected and the rule was to stop. Owner's fault for the conflict; the model's
  deviation is noted. The corrected files now sit in `_files/internal/config/` as the reference
  copies for the reviewer's byte-exact check.
+- 2026-09-25, task 04: my `TestPinAndUnpin` asserted the pin event at exactly `len-3` and the
+  release event at `len-1`, but the task's own rules make acquires under a pin record events too,
+  so a faithful implementation produces `[new pin pin new new release]` and the assertion cannot
+  hold. Ornith spent its first ten minutes puzzling over exactly that. Test fault (mine): the
+  assertion now checks order and content (a pin event naming beta, followed later by a release),
+  not positions.