Will Veracity support any form of hunk selection like darcs/hg record?

An alternative approach would be to take advantage of Veracity's ability to easily have multiple working directories/checkouts. Simply create a new working directory (do a fresh checkout somewhere else on the disk) referencing the same changeset/baseline in your original working directory and then move over the changes that you want for the first logical commit; test and commit that. And repeat. Then discard (or revert/update) your original working directory.

With this method you can split up your changes into N logical changesets. You have the choice of making them completely independent (all starting from the same original changeset so you can merge them together later) or dependent (building sequentially upon the previous one).

Granted, this is a manual approach. But you can use DiffMerge (outside of 'vv') to compare the 2 working directories and help you move over the individual changes within a file.

There is a relatively easy way to add support for hg record-like functionality to any VCS supporting status, cat and commit with explicit filenames. Algorithm is the following (grabbed from hg record and then implemented in aurum vim plugin):

1. Get list of modified files
2. Prompt user whether he choses to include specific file in the upcoming commit completely, exclude it or include partly.
3. If user have chosen to include completely, just remember the name.
4. If user have chosen to include partly, remember the name, move original file to {old-filename}.orig and prompt user about which changes he wants to include. Here is why cat command is needed: you can do like hg record and just throw away some hunks, reapplying modified diff to file contents and saving it to {old-filename}, like git add --interactive with ability to modify hunks, not just including/throwing them away, like aurum displaying file in a diffsplit and saving left window in {old-filename} or invent something own.
5. Save modified file to {old-filename}.
6. Run a commit with remembered names.
7. Move all {old-filename}.orig back to {old-filename}.

This has nothing really VCS-dependent, only names of the commands. One can work on supporting veracity in my plugin if he needs to reuse existing implementation. I currently don’t know any other cross-VCS record implementations, but nobody says there are no.