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

[Bug]: Greenfield T-002 seed still fails the inception schema gate after T-3948 (fw init path not covered)

Abierto Apto para principiantes
  • ¿Algo no está bien?
#86 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bash, shell
Área
cli

Línea de trabajo

Lee lib/seeds/tasks/greenfield/T-002-define-project-goals.md, lib/init.sh alrededor de la línea 714 y lib/inception_schema_backfill.py; compara la ruta de seed e init con la llamada de backfill en lib/upgrade.sh alrededor de la línea 1741. Añade cobertura para un proyecto recién inicializado en las pruebas Bats pertinentes y, después, verifica que T-002 supere su puerta de esquema de inception tras fw init.

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

Descripción

area:init bug severity:medium status:accepted status:released triaged
Bug Description

T-3948 (d20c996) fixed the deadlock on the inception schema gate for upgraded consumers: the gate now judges the post-edit file, and fw upgrade backfills target_blast_radius / voi_score. The fw init path was not covered: the greenfield seed for T-002 still ships without the two fields, so a freshly initialised project starts with an inception that fails the gate.

Evidence, 1.8.6 (1ea10441f):

  • lib/seeds/tasks/greenfield/T-002-define-project-goals.md: workflow_type: inception, no target_blast_radius, no voi_score. Last touched by 89bed4f (T-3636), before T-3948.
  • lib/init.sh copies the seed (line 714) and never calls lib/inception_schema_backfill.py; only lib/upgrade.sh does (line 1741).
  • tests/unit/t3948_inception_schema_upgrade.bats covers "fw upgrade of an initialised consumer backfills its old inception"; none of the eight tests in that file covers a project that is initialised and never upgraded (I did not search the other test files).
Steps to Reproduce
  1. fw init a greenfield project with provider claude.
  2. Open a Claude Code session in it and run fw work-on T-002.
  3. Ask the agent to tick an Agent AC or to fill in ## Recommendation in the T-002 task file.

Observed end to end on 1.8.3. On 1.8.6 this is read from the source; I have not run a fresh fw init.

Expected Behavior
  1. fw init a greenfield project with provider claude.
  2. Open a Claude Code session in it and run fw work-on T-002.
  3. Ask the agent to tick an Agent AC or to fill in ## Recommendation in the T-002 task file.

Observed end to end on 1.8.3. On 1.8.6 this is read from the source; I have not run a fresh fw init.

Actual Behavior
  1. fw init a greenfield project with provider claude.
  2. Open a Claude Code session in it and run fw work-on T-002.
  3. Ask the agent to tick an Agent AC or to fill in ## Recommendation in the T-002 task file.

Observed end to end on 1.8.3. On 1.8.6 this is read from the source; I have not run a fresh fw init.

fw doctor output
AI Agent

Claude Code

Operating System

Linux

Additional Context

Version: 1.8.6 (1ea10441f), vendored consumer. First seen on 1.8.3 (542623a3).

Suggestions:

  1. Add the two fields to the greenfield T-002 seed, or run the T-3948 backfill at the end of fw init.
  2. Add a check (test or fw doctor) that every seeded task passes the gates that apply to its workflow_type. T-2862 and T-3948 were both deadlocks on this same seeded task.
  3. In the block message, say that FW_ALLOW_INCEPTION_SCHEMA_DRIFT=1 is an operator action when the blocked call is a Write/Edit tool call: the agent cannot set an environment variable for a hook.
Lenguaje dominante
Shell
Estrellas
16
Forks
6
Merge medio
6 h 24 min
PR fusionados (30 d)
5

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 DimitriGeelen/agentic-engineering-framework

Todos los issues de DimitriGeelen/agentic-engineering-framework

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.