docs(opsx): fix /opsx:sync description and add detailed documentation

[HowardYan888]

Issue

The /opsx:sync command has inconsistent description and missing documentation in opsx.md:

• Description uses "Sync" instead of "Merge" (inconsistent with other docs)
• Description is unclear: "to main" vs "into main specs"
• Missing detailed Usage section documentation

Changes

1. Fixed command table description (line 167):

   • Before: "Sync delta specs to main (default workflow, optional)"
   • After: "Merge delta specs into main specs (optional)"

2. Added detailed Usage section:

   • Explains what the command does
   • Lists when to use it
   • Provides context for users

Rationale

• Consistency: Now matches commands.md and migration-guide.md
• Clarity: "Merge" is more accurate than "Sync" for this operation
• Completeness: Usage section now documents all commands in the table
• User experience: Users can find detailed information in opsx.md

Impact

Documentation-only change, no functional impact.

Related

• PR docs(migration-guide): fix inconsistent /opsx:sync description #1059: Fixed similar issue in migration-guide.md

Summary by CodeRabbit

• Documentation
  • Clarified /opsx:sync behavior: now described as merging delta specs into main specs and marked optional.
  • Added a new "Sync delta specs" usage section explaining merge behavior, when to use the command, and prompts to sync before archiving.

[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

Run ID: fec7ee09-6af5-4611-a460-bc3d0944e816

📥 Commits

Reviewing files that changed from the base of the PR and between 555eb74 and 073ec6d.

📒 Files selected for processing (1)

• docs/opsx.md

✅ Files skipped from review due to trivial changes (1)

• docs/opsx.md

---

📝 Walkthrough

Walkthrough

Updated docs/opsx.md: the Commands table now describes /opsx:sync as merging delta specs into main specs and marks it optional; a new "Sync delta specs" Usage section documents command behavior, example, and when to use it.

Changes

Documentation Update: /opsx:sync Command

Layer / File(s)	Summary
Commands table docs/opsx.md	Commands table entry for /opsx:sync changed to "merges delta specs into main specs" and marked as optional instead of default.
Usage / Example docs/opsx.md	New "Sync delta specs" section added with example /opsx:sync, details on merging delta specs into openspec/specs/, note that sync keeps specs active (non-archival), and guidance on when to use the command.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Fission-AI/OpenSpec#514: Related changes touching opsx delta-spec sync flow and prompts before archiving.
• Fission-AI/OpenSpec#1059: Similar documentation change aligning /opsx:sync wording.
• Fission-AI/OpenSpec#450: Implements/registers the /opsx:sync command and underlying specs-sync logic.

Suggested reviewers

• TabishB
• alfred-openspec

Poem

A rabbit hops through lines of text,
Merging deltas—what comes next?
Optional sync, gentle and bright,
Specs align by morning light. 🐰✨

🚥 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 accurately describes the main changes: fixing the /opsx:sync description and adding detailed documentation to docs/opsx.md, which aligns with the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/opsx.md`:
- Around line 212-214: The fenced code block containing the command "/opsx:sync"
is missing a language identifier; update the fenced block around "/opsx:sync" to
include a language tag (e.g., change the fence to ```text) so markdownlint MD040
is satisfied and the lint warning is removed.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d40a97e9-a63d-4b07-9243-1f1302ceb9b2

📥 Commits

Reviewing files that changed from the base of the PR and between 053d8a5 and cbfb276.

📒 Files selected for processing (1)

• docs/opsx.md