Thanks for the graphs. If I understood them correctly, there will be a period of time when using CGMiner as it is (no modifications) will allow YAC GPU mining (N=1024).
The hashing algorithm used in the OpenCL kernel for scrypt in cgminer has the wrong mixing and hash function to use it as-is. Litecoin uses scrypt+salsa20/8(1024,1,1) and YAC uses scrypt+chacha20/8(N,1,1). So, the mixing algorithm was changed to chacha, and the (intermediate) hash function was changed to SHA3 (Keccak). Unmodified cgminer scrypt kernel won't work for YAC even at N=1024. If it were just an issue of what N is, the value of N can be changed in the cgminer OpenCL scrypt kernel with just a couple tweaks (looking for all instances of 1024 in the OpenCL source gets you close). I think that's what most people were expecting prior to the coin's launch, that it would be identical to Litecoin's scrypt, just with a different N, and I think a ton of people had already modified N in cgminer in anticipation. I think the change to a completely different hash and mix caught everyone by surprise.
If someone modifies cgminer's OpenCL kernel in such a way that it would work at N=1024, it would actually work right now at N=64 too. There's definitely a
whole lot more to it, or else people would've claimed the bounty for a YAC cgminer within about 60 seconds!
I bet in June, there's going to be a bunch of people that try to fire up cgminer when N becomes 1024. Half of them are going to think it's working if they're solo mining (thus not expecting to hit blocks often and not getting obvious rejected shares that would tip them off to a problem). They'll never actually mine any blocks though with an unmodified cgminer (disclaimer: unless someone releases a modified cgminer between now and then, but then that wouldn't depend on N being 1024).