From the Unicode side, we probably have no problem with the allocation changing. This script is very far into the process - this font test is probably the last step before UTC approval. We also changed the SMP roadmap because of this proposal at the last UTC, so it is highly unlikely it will move. The documents being created are only for testing anyway, so if the mapping changes, we haven't let the cat out of the bag.
As far as shaping, the font has <calt>, <curs>, <dlig>, <ccmp>, <mark>, <mkmk>, <rlig>, and <kern>, although I don't know if that's appropriate for a contextual single adjustment. It has 31 substitution and 20 positioning lookups, so it is pretty complex. The allocation space is 173 code points (11 columns + 1 supplemental punctuation), and 1562 glyphs + about a dozen pre-existing glyphs (ZW(N)J, diacritics, etc) and a Last Resort glyph.
I basically just need to be able to test the encoging model. If I can do that using PUA code points, that's a fairly easy fix, although it would require making a new keyboard layout. If I need to get ahold of a custom version of uniscribe, I may be able to use my contacts. If the only workable solution is to use the preview window and print the screen, then that's what I'll do, even if it is a pain-in-the-rear.
