`isComplete: true` in status output is confusing agents about the actual situation of a change-proposal

[bnenu]

Almost every other time when i am creating changes with opsx-propose and afterwards run opsx-apply the agent is either running openspec status command or openspec instructions apply --change --json. Now these commands have a isComplete key that marks the change as complete as in ready to be implemented but it also confuses the LLM most of the time as I get this kind of thinking output:

Thinking: Wait, the status shows isComplete: true but that doesn't make sense - the tasks haven't been implemented yet. Let me check the apply instructions to see what's happening.

Now it does not happen every time but it did happen while using different LLMs. When it does happen the next step becomes non-deterministic, sometimes it is ignored and the execution continues, sometimes it triggers additional tool-calls and in a few occasions it stopped and asked how to proceed.

Please consider renaming that prop to something else that is appropriate, maybe isReady.
Fro reference, this is what I am talking about

{
  "changeName": "add-dark-mode",
  "schemaName": "spec-driven",
  "isComplete": true,
  "applyRequires": ["tasks"],
  ...
}