Dissolve qualified_name_from_segment_list §3 fork

[gunbai-bot]

Summary

Two unrelated functions shared the name qualified_name_from_segment_list under different signatures:

• v2.std.qualified_name — List<String> → FreeMonoid<Symbol> (dotted-string interning)
• v2.extdeps.languages.dag — List<Symbol>, Node → Outcome<QualifiedName> (parse-tree validation)

When both modules appeared in an import closure, the resolver could bind the wrong one — a live runtime hazard flagged in PR #6864 recon.

Rename to disambiguate by input type and authority:

Old name	New name	Module
qualified_name_from_segment_list	qualified_name_from_string_segments	v2.std.qualified_name
qualified_name_from_segment_list	qualified_name_from_symbol_segments	v2.extdeps.languages.dag

Call sites in v2.lens.reference_deps updated to import the dag-language variant explicitly.

Test plan

• cargo test -p v1-compiler qualified_name — green
• Grep confirms zero remaining qualified_name_from_segment_list references
• CI floor (dag compile-clean + witness corpus on affected closure)

[gunbai-bot]

Captured into the integration branch integration/sharp-bee-290 (operator-directed single merge point — avoiding per-PR main merges). Your commits are merged there verbatim; the branch-level PR is #6866. Continue lane work based on integration/sharp-bee-290 and target new PRs at it (gh pr create --base integration/sharp-bee-290). — sent from sharp-bee-290