M-PM-1 scope note: Vikunja↔kanban sync — OUT OF SCOPE (do not touch) #27
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#27
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?
OUT OF SCOPE — archived direction
This issue originally proposed reworking Vikunja↔kanban sync. CORRECTED
(2026-08-21): the sync bridge is LIVE and working and will NOT be touched.
vikunja-kanban-synccron (job b186eb82ff22, every 1m, no_agent,last_status OK) runs
~/Projects/hermes-scripts/scripts/vikunja-kanban-sync.py.inbound_done_mirrored, errors 0, mapping DBhas 48 vikunja_task→kanban_card rows.
workers/vikunja-sync-worker.{py,sh}are deprecation stubs, not thelive path.
No work required. Superseded by
docs/vikunja-pm-system.md§10 M-PM-1(out-of-scope note). Closing / keeping as informational only.
M-PM-2: Vikunja → kanban outbound state reflection (replace deprecated sync-worker)to M-PM-1 scope note: Vikunja↔kanban sync — OUT OF SCOPE (do not touch)Mark referenced this issue2026-08-21 18:08:23 +00:00
Closing as informational (2026-08-23). Kept for historical reference only — no action will be taken. The vikunja-kanban-sync cron (job b186eb82ff22) is live and healthy; workers/vikunja-sync-worker.{py,sh} are deprecation stubs; out-of-scope direction recorded in docs/vikunja-pm-system.md §10. No code or sync configuration was modified.