explore: should edits to existing change artifacts go through update-change? #2057

When a change already exists, explore can edit its artifacts once the user confirms. It never mentions openspec-update-change (/opsx:update), though. Is that intended?

What explore seems to do (1.14.1)

• It reads the change's existing artifacts and offers to capture decisions in them. For example, a design decision goes in design.md and a scope change goes in proposal.md.
• It gives no steps for making the edit itself. Its only write steps are for creating a new change, which were added in fix(explore): scaffold changes before capturing artifacts #1503.

What update-change covers that explore doesn't

• It checks an edit against the change's other artifacts, in either direction.
• It edits only existing output files, never a glob output path.
• It confirms each artifact separately.
• It points to apply when the change is already implemented.

Both skills are in the core profile, so a default install has both.

Question: is it intended that explore edits existing artifacts on its own? If not, could explore run update-change when it's installed, or at least point the user to it, once the user is ready to write? #1503 kept explore's handling of existing changes unchanged, so this may have been left open on purpose.

Related: #2058