Future: issue finder / opportunity surfacer for Known Issues & Resources

[elkraneo]

Context

As detail pages grow (notes, resources, known issues), manual curation will become slow.

Idea

Create an internal issue finder / opportunity surfacer pipeline that periodically discovers high-signal links for each component.

Candidate Sources

• Apple Developer Forums
• Stack Overflow
• GitHub issues/discussions (relevant repos)
• Public docs updates and WWDC references

Output

For each component ID:

• candidate link
• source type
• short reason/summary
• confidence score
• last seen date

Goal

Human-in-the-loop triage to decide what enters public Known issues and Resources.