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

docs(conventions): limit which route rows a routing-as-data team file may add

Cerrado
  • ¿Algo no está bien?
#6,642 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
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
json, yaml
Área
authorization, documentation

Línea de trabajo

Start in the Team layer section of docs/conventions/routing-as-data/README.md, where routing.rows and the kind: tool row are described, and read the team-file JSON Schema guidance and the convention CHANGELOG policy next. Done means the section states which row ids a team file may re-rank or add, excludes new kind: tool rows, the schema guidance matches, and a CHANGELOG entry records the right version bump. The DX lane (#6302) must co-sign, so expect to resolve the bump and wording with maintainers first.

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

Descripción

needs-human needs-triage

Problem

The routing-as-data convention (docs/conventions/routing-as-data/README.md, Team layer, added in
#6640) lets a consumer repo's <home>/<plugin>.yaml add route rows through routing.rows. A
kind: tool row has a free-form id, and /user-interface:design says "for a tool route, call that
tool". If an adopter implements the team layer as written, a cloned, untrusted repo can add a row
that steers the agent at any tool or skill. The doc frames the team file as data, but an added row
is more than look and conventions.

Nothing reads a team file yet, and every tool call still passes the session's permissions, so there
is no exposure today. The limit should be in the convention before the first adopter implements the
team layer.

Source: the security review run before #6640 was marked ready (OWASP A04 design note, medium
confidence, prospective).

Proposed change

State in the Team layer section that routing.rows may only re-rank or add rows whose id matches a
bundled row or an installed plugin or skill, and that a team file may not add a new kind: tool
row. Add the matching rule to the team-file JSON Schema guidance. The rule decides whether the doc
needs a major or minor version bump, per its CHANGELOG policy.

Acceptance criteria

  • The Team layer section states which rows a team file may add, and excludes new kind: tool rows.
  • The convention CHANGELOG records the change with the right version bump.
  • The DX lane (#6302) co-signs, since it adopts the same team layer.

Related

  • #6640 (adds the convention), #6483 (its issue)
  • #6302 (DX), #6306 (user-experience), #5906 (customization home)
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
6 h 58 min
PR fusionados (30 d)
951

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.