Correct the Fluxity repository-to-project links

[kalepail]

Note

Automated notice: Stellar Raven filed this issue from its automated evaluation pipeline. The issue includes evidence and a public source record. Please verify the live surface before you act.

Finding

Scout returns three Fluxity repositories with a Wagent project link. The affected rows are
luanlabs/fluxity.finance, luanlabs/fluxity-interface, and luanlabs/fluxity-api.
Each row has a Fluxity name and a Fluxity description. Each row instead returns
project.slug: "wagent" and project.name: "Wagent".

The same query returns luanlabs/fluxity-v1-core with the Fluxity project link. Therefore,
three of four exact Fluxity query results have a conflicting project relationship. A consumer can
use this field for project context and then attribute Fluxity source code to Wagent.

Evidence

On 2026-08-19, the free production request below returned four rows:

curl --get 'https://stellarlight.xyz/api/repos/search' \
  --data-urlencode 'q=fluxity' \
  --data-urlencode 'limit=20'

luanlabs/fluxity.finance says it is Fluxity's landing-page repository.
luanlabs/fluxity-interface describes Fluxity as a token-streaming solution.
luanlabs/fluxity-api says it is the Fluxity API. All three return the Wagent project link.
luanlabs/fluxity-v1-core returns the Fluxity project link and acts as the same-query control.

The full QA review found the same relationship in the saved Scout transcript. The live replay
confirms that this is current Scout data. It is not a judge-only error. The review also checked
resolved sls-058. That finding covered SCF funding metadata, so it does not own this defect.

Additional recorded evidence:

• 2026-08-19 live GET https://stellarlight.xyz/api/repos/search?q=fluxity&limit=20 returned 4 exact Fluxity-named rows; luanlabs/fluxity.finance, luanlabs/fluxity-interface, and luanlabs/fluxity-api each had project {slug: wagent, name: Wagent}, while their descriptions identify Fluxity
• dedupe: distinct from resolved sls-058, which concerned Fluxity SCF funding fields and award linkage, not repository-to-project attribution

Recommendation

Correct the repository-to-project relation for the three affected repositories. Preserve a
repository only under Wagent when source evidence supports that relationship. Add a relation-level
validation rule that compares a repository's linked project with its canonical repository metadata.

Add a regression fixture for the four exact Fluxity query results. The fixture should require the
three affected repositories to link to Fluxity. It should keep fluxity-v1-core as a control.

Source Record

Raven recorded this finding as sls-068 (stellar-light-scout, discovered 2026-08-19).

Public source record: improvements/stellar-light-scout/sls-068-fluxity-repositories-linked-to-wagent.md

Immutable source snapshot: 95da2afe171e

Resolution Handoff

When you deploy a fix, link the resolving issue or pull request to the source record.
Then notify Raven through:

https://github.com/stellar-experimental/stellar-raven/issues/new?template=upstream-improvement-ready.yml&title=%5Bupstream-ready%5D%20sls-068%3A%20

Include the finding ID and the resolving issue or pull request.
Include the deployed version or timestamp. Include the smallest live recheck.
Raven verifies the live surface before it sets the finding to fixed-upstream.
An issue closure or merged pull request does not prove the fix.
A separate reviewer repeats the live check before Raven retires the active finding.
Raven keeps a commit-pinned snapshot when one is available.

[kalepail]

Live verification on 2026-08-25 confirms the fix. All four Fluxity repositories now resolve to fluxity. PRs #981 and #982 contain the service changes. Raven source snapshot: https://github.com/stellar-experimental/stellar-raven/blob/74e1e38ac28d34f8ab49c7b5ca530e4c8b8c1729/improvements/stellar-light-scout/sls-068-fluxity-repositories-linked-to-wagent.md