vms: plan the next GUI VM runs over all features #12

Merged

asxpi merged 1 commit from vms/plan into main

2026-11-09 00:49:15 +00:00

asxpi commented

2026-11-09 00:44:53 +00:00

Member

vms/PLAN.md: every feature the repo tracks (198) sorted into vm / vm-recheck / vm-done / headless / n/a, with peers, servers, a scenario per VM feature and four batches (162 runs) for the next VM run agents, plus the harness pieces each batch still needs.

🤖 Generated with Claude Code

`vms/PLAN.md`: every feature the repo tracks (198) sorted into vm / vm-recheck / vm-done / headless / n/a, with peers, servers, a scenario per VM feature and four batches (162 runs) for the next VM run agents, plus the harness pieces each batch still needs. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

asxpi added 1 commit

2026-11-09 00:44:53 +00:00

vms: plan the next VM runs by feature and batch

/ check (pull_request) Successful in 4m20s

Details

5abb80cdeb

The 13 VM-tested features are a small part of the 198 the repo tracks,
and the next run agents need to know which of the rest a GUI run can
prove and which the headless runs already cover. Classify each feature
(vm, vm-recheck, vm-done, headless, n/a) from anotherim-js rc9's UI,
libtacky v1.2.3 and the Gajim 2.6, Dino 0.5.1 and Kaidan 0.16 support,
and group the 51 VM features into four batches ordered by the open
bugs of #1 and #9 they re-check (162 runs), with the per-client actions
and harness pieces each batch still lacks.

Assisted-by: Claude:opus-5-5

asxpi merged commit b5deaca921 into main

2026-11-09 00:49:15 +00:00

asxpi referenced this pull request from a commit

2026-11-09 00:49:16 +00:00

Merge pull request 'vms: plan the next GUI VM runs over all features' (#12) from vms/plan into main

asxpi referenced this pull request from a commit

2026-11-09 05:30:17 +00:00

Merge origin/main into vms/consolidate