fix(config): label the update workflow in the picker; drop "expanded-profile" wording

[clay-good]

Status: LGTM — closes #1627. All affected tests pass; no new failures introduced.

What was wrong

Two small, related defects surfaced in a profile-naming audit:

1. Unlabeled update row in the config picker. openspec config → edit workflows shows a checklist of all 12 workflows. WORKFLOW_PROMPT_META in src/commands/config.ts had friendly labels for 11 of them but was missing update, so that row fell back to the raw id update with a placeholder Workflow: update description. Because update is one of the six core workflows, every user who opens the picker saw it.

2. "expanded-profile" survives in template strings. The update-change workflow template called /opsx:continue and /opsx:new "expanded-profile" workflows. There is no "expanded" profile — the only profile values the product stores are core and custom — so an agent or user looking for one finds nothing.

How it was fixed

• Added the missing update entry to WORKFLOW_PROMPT_META → the row now reads Update change / Revise the planning artifacts of an existing change.
• Reworded the four template strings in src/core/templates/workflows/update-change.ts from "expanded-profile workflow" to "optional workflow".
• Regenerated the committed skills.sh mirror (skills/openspec-update-change/SKILL.md) via pnpm generate:skills and the parity hashes via pnpm regen:parity-hashes so the generated-file parity tests stay green.

Proof it works

• New regression guard (test/commands/config.test.ts): asserts every ALL_WORKFLOWS id has real picker metadata — no name equal to the raw id, no Workflow: placeholder — so adding a future workflow can't silently reintroduce the fallback. Reverting the update entry makes it fail.
• End-to-end label check against the built dist output confirms 0 raw-id fallbacks across all 12 workflows.
• Updated the three existing tests that pinned the old "expanded-profile" wording (init.test.ts, update-change.test.ts).
• Full suite: 2854 passed. The only failures (config-profile, artifact-workflow) reproduce on a clean stash of main — pre-existing and unrelated; tsc --noEmit and eslint src/ are clean.

Scope / notes

• A drift audit of every other workflow-keyed lookup table (skill dirs, command refs, skill/command templates, legacy maps) confirmed all are complete at 12/12 — this was the only affected table.
• Deliberately kept out of scope: broader docs prose that informally calls the optional commands "expanded" (a separate stylistic sweep). This PR fixes the shipped code + agent-facing template strings only.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Workflow Updates

  • Identified /opsx:continue and /opsx:new as optional workflows.
  • Added availability checks before recommending optional commands.
  • Added clear names and descriptions for the update workflow.

• Quality Improvements

  • Ensured configured workflows display complete, user-friendly metadata.
  • Updated guidance and generated workflow content to reflect revised recommendations.
  • Improved consistency between workflow guidance, commands, and generated content.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9c62caa9-3754-4540-bac4-588c1543eb75

📥 Commits

Reviewing files that changed from the base of the PR and between 03b287c and 275f2d5.

📒 Files selected for processing (2)

• skills/openspec-update-change/SKILL.md
• test/core/templates/skill-templates-parity.test.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• test/core/templates/skill-templates-parity.test.ts

---

📝 Walkthrough

Walkthrough

The update workflow now has picker metadata. Update-change guidance treats /opsx:continue and /opsx:new as optional workflows and verifies availability before recommendation. Tests cover metadata, guidance wording, and template parity.

Changes

Update workflow

Layer / File(s)	Summary
Register update workflow metadata src/commands/config.ts, test/commands/config.test.ts	Exports WORKFLOW_PROMPT_META, adds update display metadata, and validates metadata for every configured workflow.
Align optional workflow guidance skills/openspec-update-change/SKILL.md, src/core/templates/workflows/update-change.ts, test/core/init.test.ts, test/core/templates/update-change.test.ts, test/core/templates/skill-templates-parity.test.ts	Replaces “expanded-profile” wording with “optional workflow” wording and updates related generated-content expectations and hashes.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• Fission-AI/OpenSpec#1437: Updates overlapping update-change guidance to treat optional workflows as availability-dependent.
• Fission-AI/OpenSpec#1500: Modifies related update workflow guidance and tests around optional workflow wording.
• Fission-AI/OpenSpec#1278: Introduces related update workflow template and metadata behavior.

Suggested reviewers: tabishb, alfred-openspec

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes both main changes: labeling the update workflow and replacing expanded-profile wording.
Linked Issues check	✅ Passed	The changes satisfy issue #1627 by adding update workflow metadata and replacing expanded-profile wording with optional workflow guidance.
Out of Scope Changes check	✅ Passed	All code, template, mirror, hash, and test changes directly support the objectives in issue #1627.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/issue-1627-fix-dc2b41

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[alfred-openspec]

The picker metadata and optional-workflow wording look sound, and the focused generation/parity tests pass. This head currently conflicts with main in test/core/templates/skill-templates-parity.test.ts, so please rebase and resolve the conflict, then let the new exact-head matrix finish before approval.

[clay-good]

Rebased onto current main. The only conflict was the generated parity-hash file test/core/templates/skill-templates-parity.test.ts (a recurring collision from other merged PRs regenerating skills/hashes). Resolved by regenerating rather than hand-merging: took main's base, then ran generate:skills + regen:parity-hashes so the committed skills and 3 parity hashes reflect both main's current templates and this PR's update-change template change.

Verification: npm run build clean; full vitest run = 3951 passed. The parity test and this PR's own tests (config.test.ts, update-change.test.ts, init.test.ts) all pass. The only 2 failures are the known pre-existing ones on main (config-profile.test.ts:389, artifact-workflow.test.ts:1226), unrelated to this change. Intent intact: the update workflow row is labeled in the config picker and "expanded-profile" wording is dropped from the update-change template/skill. No longer DIRTY.

[alfred-openspec]

The rebase resolves the conflict cleanly, generated skills and parity hashes are current, the focused 164-test suite plus build and lint pass locally, and the full hosted matrix is green. Approved.