high-rank boundaries

[bennn]

Our rational programmer experiment for deep/shallow has some GREAT info that should be part of the docs.
(All hidden in a private repo for now.)

• add a boundary-profile script (modified ctc-profile)
• add a bnd-prf runner, for every point in the lattice
• rank IDs from the proflie; for each ID how often does it appear in any profile? what ID takes the most time?
• (optional) print top boundaries ... this is hard because the benchmarks need modification to avoid blaming the adaptor for everything

For example, take5 sends lots of IDs across boundaries but only a handful ever show up in the boundary profile:

1. --face
2. >-face
3. card3
4. configuration
5. create-card-pool
6. create-dealer
7. create-deck
8. create-player
9. player%