fix(cli): update traceability tests to use relationships instead of links

[Copilot]

Summary

Fixes 2 failing CI tests introduced by the main → develop merge.

Root Cause

The merge commit (0a58c1e) brought packages/cli/tests/traceability/traceability.test.ts from main. This test file was written against the older ManifestLookupEntry interface that used links?: string[]. However, the develop branch had independently evolved symbol-extract.ts to use a richer relationships?: TraceabilityRelationship[] interface instead.

This caused a runtime mismatch: the tests passed { id: "...", links: [...] } entries to the manifest lookup, but the source code looked for entry.relationships (which was undefined), resulting in empty reqLinks arrays.

Failing Tests Fixed

• symbol-extract > uses manifest lookup ID when symbol matches sourceFile:title
• symbol-extract > manifest lookup distinguishes symbols by sourceFile not just title

A third test (inline directive links take precedence over manifest links) was also using the wrong links format but happened to pass because the inline directive overrides manifest links anyway — it was also updated for correctness.

Changes

• packages/cli/tests/traceability/traceability.test.ts: Replace links: string[] with relationships: TraceabilityRelationship[] ({ type: "implements", to: "..." }) in 3 test ManifestLookup fixtures to match the current ManifestLookupEntry interface.

[Copilot]

Pull request overview

This PR updates CLI traceability tests to match the current ManifestLookupEntry shape on develop, replacing the legacy links: string[] fixtures with relationships: { type, to }[] so the manifest lookup data is consumed correctly by symbol-extract.

Changes:

• Updated 3 ManifestLookup test fixtures to use relationships entries ({ type: "implements", to: "..." }) instead of links.
• Aligns traceability tests with the develop branch’s ManifestLookupEntry.relationships behavior, fixing CI failures from the main → develop merge.