Score stated upstreams that fail to resolve (an actionable origin-link gap)

Abierto
#754 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, backend

Línea de trabajo

Start from reconcileSameAs, where stated evidence fails to match, and recordCompleteness, which runs in the cron beside the database and can do the grouped count in one query. Read the /v1/status response builder and the gap-report script to see how per-provider tallies are served; the report reads /v1/models and must take the same number from /v1/status or the row. Done when /v1/status shows the per-provider count of stated upstreams whose namespace resolves but link is null, the gap report agrees, and the case-sensitivity decision is recorded.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

After #754 origin links are a count, not a score, because the old score charged providers for links the service can never write. The real, fixable gap is narrower: a provider STATES an upstream (models.upstream_provider is set) and reconcileSameAs finds no row for it. Example: Fireworks states moonshotai/Kimi-K3 and Moonshot lists kimi-k3, so nothing links because stated-tier matching is case-sensitive. Nothing shows these today: unresolved stated evidence is stored but never served.

Ask

  • Count, per provider, live rows with stated evidence whose namespace resolves to a catalogued provider and whose link is null. Evidence whose namespace no provider claims (OpenRouter meta-llama/...) is not a gap: no maker row exists.
  • recordCompleteness runs in the cron next to the database, so it can compute this with one grouped query and no row-shape change. The gap-report script reads /v1/models and cannot: either it reads the tally from /v1/status, or the evidence is served on the row. Keep one scorer.
  • Decide whether stated-tier matching should be case-insensitive, as the name tier already is. That alone would resolve the Kimi and GLM rows on Fireworks, Together and Hugging Face.

Acceptance

  • /v1/status shows, per provider, how many stated upstreams did not resolve.
  • The gap report shows the same number.
Lenguaje dominante
TypeScript
Estrellas
0
Forks
1
Merge medio
5 h 40 min
PR fusionados (30 d)
193

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TanStack/schemas

Todos los issues de TanStack/schemas

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.