[ROSETTA] modernization-flow-review.md references nonexistent source-code-specs files

[isolomatov-gd]

`instructions/r3/core/workflows/modernization-flow-review.md` (Phase 7) requires: "MUST review ALL `docs/source-code-specs-<lib/project>.md` files together" — but no phase in the modernization-flow ever creates a `source-code-specs-` file. The actual artifacts created are `reference-code-specs-` (Phase 1), `original-code-specs-` (Phase 2), and `target-code-specs-` (Phase 6). The same dangling reference exists in `instructions/r2/core/workflows/modernization-flow-review.md`. An executing agent would hunt for a file that never exists. Likely fix: rename to `original-code-specs-*` (the closest matching real artifact) in both r3 and r2.

Note: edits under `instructions/r3/**` ripple into generated plugin directories (`plugins/core-*`) — regenerate via `scripts/pre_commit.py` after the fix.

[github-actions]

Rosetta Triage

Classification: bug, instructions — dangling artifact-name reference in a golden workflow instruction file (instructions/r3/**), not application code or docs.
Priority assessment: Medium — Phase 7 is written in strict MUST/MUST-NOT imperative style with an explicit "MUST NOT proceed if not addressed" gate, so a literal-minded executing agent can stall hunting for a file class that is never created, or falsely report a missing artifact. No repo-level Priority labels exist to apply.

Findings:

• Verified: docs/source-code-specs-<lib/project>.md is never created by any phase in either r3 or r2. Confirmed dangling reference at instructions/r3/core/workflows/modernization-flow-review.md:37 and instructions/r2/core/workflows/modernization-flow-review.md:35.
• Verified phase mapping matches the issue exactly: Phase 1 (modernization-flow-reuse.md) creates reference-code-specs-*, Phase 2 (modernization-flow-analysis.md) creates original-code-specs-*, Phase 6 (modernization-flow-mapping.md) creates target-code-specs-*, Phase 7 (modernization-flow-review.md) is the file with the stale reference.
• Proposed fix (rename source-code-specs → original-code-specs on both lines) is correct and complete — it makes the three MUST-review bullets exactly cover the three real artifact types with no gap or duplication.
• No other stale references to source-code-specs exist elsewhere in instructions/r3 or instructions/r2.
• The same stale line is mirrored verbatim into all 7 generated plugin copies (plugins/core-claude, core-cursor, core-cursor-standalone, core-copilot, core-copilot-standalone, core-codex, core-antigravity), confirming the issue's own note that a scripts/pre_commit.py regen is required after the source fix.

Suggestions:

• Apply the one-line rename in both r3 and r2 modernization-flow-review.md, then regenerate plugins via venv/bin/python scripts/pre_commit.py per docs/ARCHITECTURE.md guidance so plugins/core-* stay in sync.

This is well-scoped and actionable as filed — good first issue candidate.

Automated triage by Rosetta agent