hermes - 💡(How to fix) Fix kanban create --priority should accept human-readable strings (high/medium/low) in addition to integers [1 pull requests]

Description

The hermes kanban create and hermes kanban swarm commands accept only integer values for --priority:

--priority type=int, default=0, help="Priority tiebreaker"

This forces scripts and users to remember that 3 = high, 2 = medium, 1 = low, which is not intuitive. String values like --priority high are rejected by argparse with a type error.

Expected Behavior

--priority should accept both:

• Strings: "high" / "h" → 3, "medium" / "m" → 2, "low" / "l" → 1
• Integers: 3, 2, 1, 0 (current behavior, preserved)

This is a minor UX improvement that makes scripts and interactive use more readable. The SkillOpt pipeline's seed-board.sh script already uses --priority high (string), which fails at runtime.

Impact

• Low: existing integer usage is unchanged
• Positive: scripts become self-documenting (--priority high vs --priority 3)
• Positive: reduces the documentation burden — users don't need to memorize the int↔priority mapping

Related

Documented as a pitfall in the SkillOpt skill:

"Using string values like --priority high will silently fail or produce unexpected priority levels."