v0.5.0

Nested Service Spans

Generic (non-RF) spans whose parent is an RF KEYWORD span are now nested as children of that keyword in the Explorer tree, preserving the causal chain from RF keyword → backend service call.

What changed

• _build_keyword() and _build_test() in rf_model.py now include GENERIC children via _build_generic_keyword()
• all_span_ids parameter threaded through _build_suite(), _build_test(), _build_keyword(), and interpret_tree()
• New _collect_generic_roots() helper ensures SUITE/TEST-parented generics stay in Service Suites (not nested)
• No changes to tree.py or tree.js — the span tree already links correctly and the frontend already renders GENERIC keywords with service badges

Behavior

• Generic spans with a KEYWORD parent → nested under that keyword
• Generic spans with no parent, missing parent, or SUITE/TEST parent → remain in Service Suites
• Nested children sorted by start_time ascending
• Every input span appears exactly once in the output model