Document how circuitmux works

circuitmux is a critical abstraction; we should document it in itself and as a part of our key dataflow.

changed milestone to %Tor: 0.2.9.x-final

added TorCoreTeam201610 actualpoints::.5 component::core tor/tor milestone::Tor: 0.2.9.x-final owner::nickm parent::14683 points::1 priority::medium resolution::implemented severity::normal sponsor::U-can status::closed tor-doc-modules tor-docs-dev type::defect labels

Trac:
Milestone: N/A to Tor: 0.2.9.x-final
Sponsor: N/A to SponsorU-can
Component: - Select a component to Core Tor/Tor
Keywords: N/A deleted, tor-doc-modules, tor-docs-dev added

Trac:
Status: new to assigned
Owner: N/A to nickm

Defer target for these doc fixes to 0.3.0 (though of course they can go into 0.2.9 if they're done on time.)

Trac:
Milestone: Tor: 0.2.9.x-final to Tor: 0.3.0.x-final
Keywords: N/A deleted, TorCoreTeam201610 added

56933787d55f74c667f364ae58cd277d79d9fc27 and 84829e336c3f72e4926e90d6f2e58eed0a538bce do this.

Trac:
Status: assigned to closed
Resolution: N/A to implemented
Actualpoints: N/A to .5
Milestone: Tor: 0.3.0.x-final to Tor: 0.2.9.x-final

closed

changed time estimate to 8h

added 4h of time spent

moved to tpo/core/tor#19287 (closed)