"restrictive" is default, don't repeat it.  don't be wordy about masturbation.  this is a SUMMARY not a description.

Avoid the filter overhead of randomRelatedSlave when all we really want to know is whether ANY slave meets the condition.

1. Add a new release rule to control whether development facility leaders (Nurse, Attendant, Matron, Warden, and Schoolteacher) are allowed to have sex with the slave.  Does not affect production facility leaders.
2. Determine employee-leader sexual contact before running slave reports at all, and adjust need and counters based only on ACTUAL sex, not hypotheticals.  Fixes bugs for Cellblock and Clinic even without no rules changes, but also accounts for the new rule.  Counters for both slaves are always adjusted on the *employee* end.
3. Friends may satisfy sexual needs in the clinic, if they're allowed to under general release rules; if relationship rules are *also* permissive, their relationship will advance automatically to FWB.
4. Fix many instances of counter mismatch throughout these scenarios.  Use seX() where it makes sense to do so.
5. Add hints to Slave Interact to describe the release rules in more detail.  Doesn't look great but should get the message across.  Someone's welcome to reformat these if they want.

1. Make areRelated and relativeTerm work regardless of familyTesting.  This fixes some bugs right away, since they are already used unchecked a few places, and it makes it a lot easier to write generic descriptions and event text without breaking things.
2. Extend relativeTerm to handle sole parent and grandparent/grandchild cases.
3. Make relativeTerm return null instead of "some unknown blood relation" if no relationship could be found between two slaves.  This was never OK to output (i.e. "$his some unknown blood relation" doesn't read right), so it ended up just being tested for everywhere (which can be done more easily with null).
4. Remove duplicate code based on familyTesting when the only difference was whether areRelated and relativeTerm or their legacy alternatives were used.  There is a lot of this.
5. Remove hasRelationP entirely (it is superseded in all use cases by areRelated).

Add a group of utility functions for determining how a slave is actually getting release (as opposed to how they are allowed to do so).