Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

perf(discovery): slice-only docs reads lose recall on scattered questions

Cerrado
  • ¿Algo no está bien?
#6,487 1 comentario 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
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
markdown
Área
performance, search

Línea de trabajo

Start from the artifact introduced in #6348: the shared docs lookup skill /discovery:read-docs and its escalate_bytes (default 60 KB) and section-count (25%) escalation rules, plus the Phase 6 acceptance kit, note, cache and grader used for the confirmation run. Identify where the thresholds and the slice-reading procedure live, then run the measured comparison of default vs. lower threshold vs. procedure nudge vs. combination, reporting n per arm and the same interval rule as the confirmation run. Done means the slice-only versus escalated recall gap closes within noise at acceptable bytes/tokens cost, or the null result is recorded and defaults kept.

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

Descripción

needs-triage priority: medium

No related issue: measured follow-up to #6348 (part of #6020).

Summary

The shared docs lookup (/discovery:read-docs, #6348) returns verbatim sections and escalates to the whole page past a size or section-count threshold (escalate_bytes, default 60 KB; 25% of sections). The Phase 6 acceptance run showed that runs reading only slices lose recall on questions whose answer is scattered across a page:

  • Slice-only runs: new-core recall .838 (n=4).
  • Runs that escalated to the whole page: .927 (n=6).
  • The worst slice-only run scored .74; it never read 3 scattered sections.
  • The same direction appeared in the original batch (.93 vs .86).

The pre-registered confirmation passed (10 fresh runs, mean .891 vs the no-cache arm's .936, lower bound -.072 against a -.10 margin) and thresholds were kept at defaults, so this is an improvement, not a regression fix.

Fix

Candidates, each to be measured before adopting:

  1. Lower the escalate_bytes threshold so more reads return the whole page.
  2. Add a procedure nudge: when a question spans many sections, read the whole page instead of slices.

Verification

  • A measured comparison on the same acceptance kit (same questions, same note and cache, same grader) of the default, each candidate, and the combination.
  • Acceptance: the slice-only versus escalated recall gap closes (target: slice-only runs within the noise of escalated runs) without losing the cost benefit, measured as bytes or tokens read per run against the current default. Report n per arm and use the same interval rule as the confirmation run.
  • If neither candidate closes the gap at acceptable cost, record the result and keep the defaults.

Related

  • #6020 (umbrella)
  • #6348 (shared docs cache, fetcher, /discovery:read-docs)
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
5 h 11 min
PR fusionados (30 d)
838

Preparar el entorno

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 melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.