Xcode documentation generation: part of an open source library?

I'm running into some interesting issues with Xcode's documentation generator. I've reported the issues using bugreport.apple.com, but I'm wondering if there's an open source component I should file for as well? Anyone know what may be used to generate the inline documentation in Xcode?

Issue I'm seeing is this:

/// <#Description#>
///
/// - initialized: <#initialized description#>
/// - resumed: <#resumed description#>
/// - suspended: <#suspended description#>
/// - cancelled: <#cancelled description#>
/// - :returntrue: <#:returntrue description#>
/// - : <# description#>
/// - :returnfalse: <#:returnfalse description#>
/// - : <# description#>
/// - : <# description#>
/// - : <# description#>
/// - : <# description#>
/// - :returnfalse: <#:returnfalse description#>
public enum State {
    case initialized, resumed, suspended, cancelled

    func canTransitionTo(_ state: State) -> Bool {
        switch (self, state) {
        case (.initialized, _): return true
        case (_, .initialized), (.cancelled, _): return false
        case (.resumed, .cancelled), (.suspended, .cancelled),
             (.resumed, .suspended), (.suspended, .resumed): return true
        case (.suspended, .suspended), (.resumed, .resumed): return false
        }
    }
}

Which is rather hilariously bizarre, as the generator seems to be evaluating the function. I've also noticed that enums with sub enums will have docs generated for the combined cases all of enums, which is a bit much.

This is in Xcode unfortunately - I noticed a recent jira/PR to move it into the refactoring engine (a fairly big job) but it got cancelled in favor of the Xcode version.

Xcode is at odds with Swift about how enum cases ought be documented -- Swift prefers the doc comment prior to the case; Xcode's approach of putting them in a bullet list attached to the enum decl is fragile/wrong, look at what happens in quick help if you have an enum case called 'warning' ...