event/view parser order

Trap: calling parseSlashSeparatedArg() first in event/view.ts looks consistent with other org/project targets, but it misclassifies valid project/<hex-event-id> input as an incomplete org/project target and throws ContextError. Fix: always run parseSingleArg() first, then parseSlashSeparatedArg(), because the event command’s two-part form has distinct grammar.