M-PM-4 (superseded): milestone-close review via pm-observer — abandoned, phantom #30
Labels
No labels
blocked:needs-decision
bug
chore
cron
design
in-progress
infra
milestone
module-o
needs-decompose
needs-research
ops-task
pm
quickfix
security/medium
triage-approved
vikunja
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/org_mode#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
CLOSED — SUPERSEDED (2026-08-21)
This issue proposed a webhook-driven milestone-close review card assigned to
pm-observer. That was a phantom invention.Ground truth: Vikunja natively marks a milestone complete when all its tasks
are done (
done_when_all_tasks_are_done).tasker-workerwrites task stateback to Vikunja as it drains cards. There is no separate review profile and no
cadence layer.
The user confirmed the current substrate is the correct implementation. The
pm-observermachinery has been purged fromdocs/vikunja-pm-system.md(§9).Superseded by: the existing
tasker-workerdriver + native Vikunja milestoneclosure. No work required.
M-PM-5: Cadence / review cron — milestone close + weekly digest deliveryto M-PM-5: Milestone-close review — completion + post-mortem (PM observer agent)M-PM-5: Milestone-close review — completion + post-mortem (PM observer agent)to M-PM-4: Milestone-close review — completion + post-mortem (pm-observer)M-PM-4: Milestone-close review — completion + post-mortem (pm-observer)to M-PM-4 (superseded): milestone-close review via pm-observer — abandoned, phantom