/opsx:continue does not reflect spec.md changes after design.md and tasks.md deletion

[yhwelcome1981-debug]

Description:

When I modify an existing spec.md file within a change, then delete the corresponding design.md and tasks.md files, and subsequently run /opsx:continue, the newly generated design.md and tasks.md do not reflect the changes made to the spec.md. It appears that /opsx:continue might be using an outdated context or cache of the spec.md when regenerating these artifacts.

Steps to Reproduce:

Start a new change (e.g., using /opsx:propose or /opsx:new).
Allow spec.md, design.md, and tasks.md to be generated.
Open the spec.md file (e.g., openspec/changes//specs//spec.md) and make a significant modification (e.g., add a new requirement, change a key detail). Save the spec.md.
Delete the design.md file (e.g., openspec/changes//design.md).
Delete the tasks.md file (e.g., openspec/changes//tasks.md).
Run the command /opsx:continue within the change directory.
Observe the newly generated design.md and tasks.md.
Expected Behavior:

The newly generated design.md and tasks.md should incorporate and reflect the latest changes made to the spec.md file. The /opsx:continue command should re-evaluate the current state of the spec.md when regenerating dependent artifacts.

Actual Behavior:

The newly generated design.md and tasks.md appear to be based on the original content of the spec.md (before the modification in step 3), completely ignoring the recent changes. This forces manual re-creation or extensive manual editing to align design.md and tasks.md with the updated spec.md.