Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Chiusa Adatta ai principianti
  • Qualcosa non va?
#86 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
bash, shell
Ambito
cli

Direzione di ricerca

Leggi lib/seeds/tasks/greenfield/T-002-define-project-goals.md, lib/init.sh intorno alla riga 714 e lib/inception_schema_backfill.py; confronta il percorso di seed e init con la chiamata di backfill in lib/upgrade.sh intorno alla riga 1741. Aggiungi la copertura per un progetto appena inizializzato nei test Bats pertinenti, quindi verifica che T-002 superi il controllo dello schema di inception dopo fw init.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Shell
Stelle
16
Fork
6
Merge medio
6h 24m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DimitriGeelen/agentic-engineering-framework

Tutte le issue di DimitriGeelen/agentic-engineering-framework

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.