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

fw task update: no verb for appending an Updates note without a status transition

Aperta
  • Qualcosa non va?
#47 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
58/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
shell
Ambito
cli, developer-experience

Direzione di ricerca

Start by reading the fw task update implementation and update-task.sh, then trace how status transitions append entries to ## Updates and set last_update:. Add a note-only path that appends a timestamped entry without changing status:; done when notes can be added without --status and existing status-update behavior remains intact.

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

Descrizione

Context

  • Framework version: 1.6.769
  • Project: 1409-sprind (shared-tooling mode)
  • Reported: 2026-09-21T15:59:10Z

Description

Symptom

There is no way to append a note to a task's ## Updates section without also passing
--status <value> to fw task update / update-task.sh. Every write path to the Updates
section goes through the status-transition machinery, even when the note is pure
documentation and the task's status is not actually changing.

Three independent instances (field reports, same class)

  1. T-1102 round 1 (procAsFit worker): needed to repair T-1051's Updates section after a
    templating corruption, with T-1051's status unchanged. Worked around it with a direct Edit
    to the task file.
  2. T-1102 round 2 (procAsFit worker): needed to add a progress note to T-1056 while it stayed
    started-work (no status change warranted). Same workaround.
  3. T-1102 round 3 (procAsFit worker, this report): needs to record a TermLink dispatch-manifest
    finding (WR2-04, whether --isolate was exercised) in T-1102's own Updates section, while
    T-1102 itself stays started-work. Same workaround, third time.

All three are legitimate uses (repair, progress note, orchestration bookkeeping) that have
nothing to do with a status transition, forced through a direct file edit because no narrower
verb exists.

Suggested fix

Add fw task note T-<id> "message" (or update-task.sh --note "message" without requiring
--status) that appends a timestamped entry to ## Updates and updates last_update:, without
touching status:. This removes the only reason field agents currently reach for a raw Edit
on a governance-relevant file for a routine, low-risk operation.

Context

Filed from SPRIND Streichliste (1409-sprind), a shared-tooling-mode project running AEF
1.6.769. .agentic-framework/ is vendored/read-only there (T-1017), so this report is filed
rather than patched locally.

Reported via fw upstream report from field installation

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.