Skip to content

feat(port): a derived move follows its handler's hand-over - #128

Open
sp00ktober wants to merge 2 commits into
mainfrom
port/handovers
Open

sp00ktober wants to merge 2 commits into
mainfrom
port/handovers

Conversation

@sp00ktober

Copy link
Copy Markdown
Contributor

A derived own move now continues into the pair its donor handler hands over to, instead of ending there; derived moves equal in every field share one slot.

  • brain/own.py: follow (each donor pair derived once; [brain.pairs] names win; a ring, an incomplete or unmapped follow-up is not followed: P3_OWN_NEXT) and share (equal tails merged to a fixed point; anchored names kept).
  • mhfu-port own lists each chain across its hand-overs.
  • Zinogre: 11 of 12 hand-overs followed ((7,65) -> (8,0) not: the donor has no clip 0); own moves 89 -> 93 of 96, turn keys 4642 -> 4701. Brute unchanged.
  • Ten twin pairs (7,70/71, 79-82, 116-119) play their twin's chain, not their own hand-over (ELSEWHERE in test_zinogre_brain.py): deriving them needs 125 own moves.

Tests: framework 658, mhfu 1647, mhfu-port 1037, studio/monster 1638 passed (data set).

🤖 Generated with Claude Code

sp00ktober and others added 2 commits October 23, 2026 01:35
A pair whose handler ends into one other pair hands over to its move, as MHP3rd
does, and moves equal but for their label are one (own.share). The Zinogre's own
moves go from 89 to 93 of 96; the hand-over to pair 8,0 is not followed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each step shows the pair it comes from, a step shared with an earlier chain is
marked once, and the header counts the own moves against the framework's.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant