Inline Commands Directions (Retired)

Route new selection and action features to native application surfaces rather than the retired Obsidian inline framework.

When to use

user asks to add an action formerly modeled as an Obsidian inline command

Directions

Do not extend work_buddy/inline/ or add another #wb/cmd/* scanner. Place the action on the owning native surface and call its domain API. Preserve the domain's consent, CAS/idempotency, privacy, and provenance rules. If a legacy file must be inspected for migration, use a bounded operator path; do not turn the importer into a recurring product feature.