docs: define initial quest board stories

knowledge/user-stories/us-008-control-player-quest-commands.md

@@ -0,0 +1,27 @@
+---
+type: User Story
+title: "US-008: Control player quest commands"
+description: Let administrators require physical-board interaction by controlling access to player quest commands.
+status: backlog
+---
+
+# US-008: Control player quest commands
+
+As an **administrator**, I want to enable or disable player quest commands so that I can require players to use physical quest boards.
+
+## Acceptance criteria
+
+- [ ] Player `/quests` commands are disabled by default.
+- [ ] An authorized administrator can use `/questadmin commands enable|disable` with contextual autocomplete.
+- [ ] The command setting persists across server restarts.
+- [ ] When disabled, `/quests`, `list`, `create`, `complete`, `cancel`, and `claim` reject execution with a clear message directing the player to a quest board.
+- [ ] Disabling commands does not prevent any equivalent action through a registered board.
+- [ ] `/questadmin` remains available to authorized administrators regardless of the player-command setting.
+- [ ] Unauthorized users cannot change the setting.
+- [ ] Automated tests verify the default, persistence, authorization, every gated subcommand, and autocomplete.
+
+## Related
+
+- [US-002: Create and use shared quest boards](us-002-create-and-use-shared-quest-boards.md)
+- [US-003: Create a block-delivery quest](us-003-create-a-block-delivery-quest.md)
+- [US-007: Expire quests and claim held items](us-007-expire-quests-and-claim-held-items.md)