VS-29: sync ROADMAP.md after VS-3 file-tunnel landed #49
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/roadmap-sync-vs3-done-vs-29"
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?
VS-29: sync ROADMAP.md with verified state after VS-3 landed
The prior VS-29 sync (
a5cc159, merged #44) was immediately followed by VS-3 merging (#45, the per-device file tunnel). That left ROADMAP.md stale again: VS-3 still showed as In Progress under "Remaining work", and VS-3's edits tolib.rsshifted the AMT route line numbers cited for VS-15.This pass re-verifies every kept claim against current
main(issue states checked against YouTrack 2026-06-06).Changes
yt issue get-field VS-3 State= Done): removed its Tractable row, added it to the "landed since" bullet, recounted the previous snapshot as 14 Done (VS-1 through VS-14) / only VS-16 remaining.lib.rs:587-589(ipkvm / commander / apf) and:617(oneclickrecovery), replacing the old contiguous:586-616.SmsSender::send(sms.rs:53-107) has shipped real handlers for all three providers since the initial commit. The actual residual is the stale crate doc header atsms.rs:3-6. Reworded to reflect that it is a stale comment, not a missing feature.Verified unchanged (refs still match
main)user_session.rs:1639(amtsetupbin), VS-17meshcentral-auth/src/saml.rs, VS-18meshcentral-codesign/src/lib.rs.main.rs:3-58stale header / 22 implementedCmdverbs (counted).crates/).ChannelWindowAdjustsession.rs:275,ServerUpdateuser_session.rs:4626.Acceptance criteria
main.Closes after human merge; issue stays In Progress until then.
🤖 Generated with Claude Code