Job chat doesn't really know about lazy state and that's important

[josephjclark]

Working through some code generation with the assistant I've hit some issues that need invesigation

• The assitant is using dataValue() from the adaptor. Didn't we undocument that to stop this very problem? It's very possible that, even if we did, we only did it on common, and the docs for eg dhis2 stll include dataValue as the function to read state. In fact I can see in Lightning's (very broken) docs, dataValue is listed and it shouldn't be really
• When I told the assistant to use $.data instead, it used it like a JSON path: import('CREATE_AND_UPDATE', '$.data');. Also wrong!

So I think we need to build into the prompt a) don't ever use data value, b) use $ to read from state

[josephjclark]

I think this is for me to update the job writing guide