Stop the Markdown hardness run failing on three known stop-sync cases #329
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!329
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-364-kanban-stopped"
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?
The Markdown hardness run found three things while the 0.6.0 release was being tested (NEC-362). None of them is a plugin change. This PR makes the run stop testing what it can't hold the plugin to, and records each case in
docs/sync-limitations.md.KANBAN_STALE_SAVE_MSbefore it touches a board in that state, and the case is documented. The harness's word delete now keeps the line break that ends a note's properties.stopSyncto become async, which is left to the card.Verified:
Task: NEC-364
Task: NEC-366
Task: NEC-367
Changelog
NONE
🤖 Generated with Claude Code
https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B