Organize for Later Legibility

[mmore500]

• [x] fix CI
• [ ] reorganize longevity ordering: naive -> grundy, descending -> hadamard
  • [x] plug in Grundy bit magic implementation from OEIS: return n>>((~(n+1)&n).bit_length()+1)
• [ ] rename value -> term
• [ ] make project status notes in manuscript
  • [x] make a glossary with "term", "index", "position", "incidence", "reservation", "fractional", "incrementing", "invasion/invader"
• [ ] should get_* rungs algo helpers be renamed calc_*?
• [ ] factor out and refactor site selection strategy support and tests
• [ ] factor out site selection strategy algorithms and tests
  • [ ] hanoi_grundy_order_incidence_rungs_algo
  • [ ] hanoi_grundy_order_term_rungs_algo
  • [ ] hanoi_hadamard_order_term_rungs_algo
  • [ ] hanoi_hadamard_order_site_rungs_algo
• [x] add dummy entries for BitSurface and StructSurface

[mmore500]

• [x] surface rank capacity should be a first-class policy method

[mmore500]

Order of operations:

1. Move existing code into '_enact/_impt' from 'Invar', and accordingly, move existing implementation.
2. Transfer support for helpers back from 'calc resident deposition _rank' to 'hsurf'; move '_enact/_impt' to 'impl' on an as-needed basis.
3. Transfer 'hanoi cooltuk order _term rungs algo'; move helpers out of 'hanoi hadamard order_site_rungs_algo' as needed.

** Remember to move tests!

[mmore500]

Rename order algorithms to layout?

[mmore500]

• [x] add job for heavy tests

[mmore500]

• [x] why is test_pick_deposition_site using so much memory?

[mmore500]

• term: should be used in the future to describe a value in a sequence
• index: used to refer to the semantic position of a reservation in an incidence reservation ring buffer
• position: used to refer to the physical location of an incidence reservation ring buffer
• incidence: the zero-indexed ocurrence count of a hanoi value (multiple incidence are the same hanoi value multiple times)
• reservation (incidence reservation): a space used to store hanoi values, sequentially... grows in size and decreases in count as more hanoi values added
• fractional: breaking down a the reservation ring buffer in fractions that are smaller than half (e.g., one at a time)
• incrementing: the more coarse strategy to break down a reservation ring buffer half at a time
• invasion: the process through which new hanoi values are written into a reservation ring buffer; invader refers to the hanoi value that is incursing
• rung: how reservation buffers are broken down
  • incidence: entire half of reservations dropped at once (very rough)
  • term: entire half of reservations for a particular hanoi value dropped at once (ie incrementing)
  • site: individual sites for a particular hanoi value dropped (ie fractional)

[mmore500]

the term/incrementing algorithm can be achieved by disabling get_fractional_downgrade_state to always return None