REVIEW ships without its review-daily/weekly/monthly workflows, so /review waits forever

Abierto
#2,766 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 5 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bun, typescript, yaml
Área
backend, tooling

Línea de trabajo

Read PULSE/modules/review.ts, REVIEW/Health.ts, and the USER workflow template tree, starting with statusline-refresh.workflow.yaml to see how shipped workflows are defined. Check how the installer and /review page handle missing workflow schedules. Done means fresh installs have working review schedules and the empty state explains when no weekly review is scheduled; the issue also identifies related learning jobs whose setup may need investigation.

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

Descripción

What happens

A fresh install ships LIFEOS/REVIEW/ and the Pulse /review page, but nothing schedules the reviews. On a new install the page reads "Nothing is waiting on you. New decisions appear here after the weekly review." indefinitely, although no weekly review will ever run.

Evidence (v8.761.0, also main at f6ab5e02)

  • PULSE/modules/review.ts nextRuns() reads USER/WORKFLOWS/review-{daily,weekly,monthly}.workflow.yaml, and REVIEW/Health.ts LEARNING_JOBS expects workflows review-daily, review-weekly, review-monthly.
  • The release's USER/WORKFLOWS/ holds only statusline-refresh.workflow.yaml.
  • No Setup.md, installer step (InstallAll.ts, Doctor.ts, ScaffoldUser.ts), Services.ts entry or doc tells the user to create them. REVIEW/README.md lists the commands but not who runs them.
  • The empty-state line in Observability/src/app/review/page.tsx falls back to "after the weekly review" exactly when the workflow is missing, so the gap looks like a quiet week.
  • The same holds for the other LEARNING_JOBS (errata-daily, errata-weekly, errata-misses-daily, errata-impact-weekly, ideal-reconcile, ideal-recommend); ErrataSystem.md describes errata-daily as a step of delta-daily, which is not shipped either.

Suggested fix

Ship the three review-* definitions in the USER template tree (like statusline-refresh), or a REVIEW Setup section with them, and have the empty state say "No weekly review is scheduled" when next_runs.weekly is null.

What we did locally: three command workflows running bun LIFEOS/REVIEW/Review.ts <cadence> --json on schedule triggers (daily 06:45, weekly Sunday 08:00, monthly day 1 08:30), which the dispatcher fires and /review now reports as the next run.

Lenguaje dominante
TypeScript
Estrellas
19.9k
Forks
2.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 danielmiessler/LifeOS

Todos los issues de danielmiessler/LifeOS

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.