It'd be a good idea to begin making an EAP7 / WF10 server adapter pair, or at least preparing.
Looking at the versions of jars that we care about for management commands, Jars in EAP7 current DR3 are:
These jars are identical to those in WF9-CR1 except for wildfly-protocol and wildfly-controller-client, which are at 1.0.0.CR1 in wf9. So wildfly-core (repository) has undergone a 'major' version bump, and is likely undergoing significant API cleanup. It would be smart to expect that we probably will require a new management plugin on our side to compensate.
Also, it's worth noting that in WF8 / WF 8.1, these jars are actually versioned 8.0 / 8.1 respectively, and so the version has actually decreased as we've moved forward. I've brought this up on wildfly-dev, though it may be a bit late since WF is already ar RC3.