llama 3.3 70b q4 generates valid typescript but wrong interface names past 21k context....
tested yesterday at 21.3k context with a codebase that has 14 typescript interfaces defined in context. generated code that uses interfaces but references ones that dont exist in the actual codebase.... like it references `UserProfile` when the actual interface is `IUserProfile` or hallucinates `ApiResponse` when we use `ResponsePayload`. the typescript syntax is perfect, compiles fine if you add the hallucinated interfaces, but the names are just wrong this matches the sql table name issue from #523 and the python exception issue from #548.... seems like past ~20k llama 3.3 70b q4 maintains syntax but loses track of specific identifiers that were defined earlier in context
lol how is the context extension this broken. past 21k it gets the syntax right but just picks random interface names that don't exist in the codebase. we hit this at 22k yesterday and it was generating imports for IUserProfile when the actual interface is IUser