Spec: Define a documented convention for pairing short and long option names in specs (#374)

[warp-factories]

Summary

• Adds the product and technical specifications for the option-name pairing convention requested in Define a documented convention for pairing short and long option names in specs #374.
• Recommends README.md as the canonical contributor-facing location, with the command-spec skill linking to it.
• Defines complete alias references for exclusiveOn, opportunistic migration, and the BSD/macOS platform caveat without changing runtime behavior.

Open questions

• Whether exclusiveOn should be carried into the runtime and enforced in a separate change.
• Whether a future presubmit check should enforce alias grouping and complete exclusivity references after the convention has been adopted.

[warp-factories]

This PR was generated with Warp.

Comment @warp-factory on this PR to send it follow-up work.

  

[vikvang]

@warp-factory spec approved

[warp-agent-staging]

No Factory you can access is connected to warpdotdev/command-signatures. Connect this repository to a Factory or ask a Factory admin for access, then mention @warp-factory again.

[warp-factories]

Spec approval recorded — thanks. plan-approved clears the spec gate for #374.

Implementation is still gated separately: it needs ready-to-implement on #374, which is a maintainer-only label the factory won't apply itself. Add it there and the factory will pick up implementation against this approved spec.

The two open questions in the description (runtime enforcement of exclusiveOn, and a possible presubmit for alias grouping) are deliberately left out of scope — they're yours to route separately.

Responding as Warp for OSS: Open session · View run