concore.read() API break: tuple return is breaking existing Python studies and generated templates

[avinxshKD]

concore.read() now returns (data, ok), but a lot of existing code still expects just data.
That mismatch is breaking loops and data handling in real study scripts.

This is not a corner case, it impacts demos, tools, and init-generated starter code.

What is needed:

Keep backward compatibility for value = concore.read(...) callers.
Provide/keep an explicit status-aware path for new code.
Update generated templates so new projects don’t start broken.
Add regression tests for both calling styles.

[avinxshKD]

@pradeeban @Rahuljagwani @mayureshkothare What do you think of this ? would appreciate your take.
read() is core runtime API surface, so breakage here propagates to study execution.

[pradeeban]

Yes, that is a critical bug.

[avinxshKD]

@pradeeban Thanks for confirming. I’ll start working on a backward-compatible fix with tests :p