[ROSETTA] Align prompt-authoring workflow handoff identifiers

[isolomatov-gd]

In instructions/r3/core/workflows/coding-agents-prompting-flow.md, the state path omits .md while every phase updates the .md form, and validation consumes Candidate Prompt Set although the prior phase produces Prompt Set. Normalize both producer-consumer identifiers, simulate the seven-step handoff, and regenerate all plugins.

[github-actions]

Rosetta Triage

Classification: bug, bug, instructions — R3 prompt-workflow contract defect.
Priority assessment: High — the defect affects workflow resume and the final validation handoff in every generated plugin distribution.

Findings:

• Confirmed: the only absolute state path omits .md, while the workflow purpose, all seven phase updates, and the checklist use coding-agents-prompting-flow-state.md. An executor can create or resume a different state artifact.
• Confirmed: step 5 produces Prompt Set; step 6 consumes it; step 7 instead requires unproduced Candidate Prompt Set. This breaks the final validation contract.
• The generated Codex workflow carries both defects, and the checked-in plugin representations carry the same tokens. The correction must be made in the R3 source, then propagated by regenerating all plugin targets.

Simulation:

1. Discover produces Discovery Notes and Reference Set.
2. Extract/intake produces Prompt Brief and Open Questions.
3. Blueprint produces Blueprint.
4. Draft produces Draft Prompt Set.
5. Harden/edit produces Prompt Set.
6. Simulate consumes Prompt Set and produces Simulation Notes.
7. Validate must consume Prompt Set with Prompt Brief, Blueprint, and Simulation Notes; it currently names an artifact that no prior phase produces.

Caveats:

• Open Questions is an unconsumed step-2 output. Decide whether it needs an explicit resolution or persistence contract; this is secondary to the reported defects.

Suggestions:

• Normalize the state path to agents/TEMP/<FEATURE>/coding-agents-prompting-flow-state.md and the validation input to Prompt Set.
• Add a content-level propagation test for the canonical workflow and generated Codex skill. Structural parity alone cannot detect these identifier contracts.
• Regenerate all R3 plugin outputs and inspect each generated workflow representation for the corrected state path and artifact handoff.

Actionable next step: apply the two source corrections, add the contract coverage, regenerate plugins, and validate all generated targets.

Automated triage by Rosetta agent