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

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

Abierto
  • ¿Algo no está bien?
#47 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
shell
Área
cli, developer-experience

Línea de trabajo

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.

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

Descripción

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

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.