good work. I do have a concern though. There's a lot of files involved, and this kind of renders the lockscreen usable only for the framework version it was designed for, since further changes (or backwards compatibility) could pose a problem. Do you think it would be possible to have the android.policy instead call on a separate program and launch a custom lockscreen, making it, thus, slightly more modular. Cyanogen's builds are a moving target and, though his framework hasn't changed much lately, i do feel it's going to be useless once he gets more work into donut and abandons cupcake for good.
Best reference thread ever: Learn to compile your own AOSP build
(for sapphire, but applies to dream too)