docs: define initial quest board stories

knowledge/user-stories/us-002-create-and-use-shared-quest-boards.md

@@ -0,0 +1,27 @@
+---
+type: User Story
+title: "US-002: Create and use shared quest boards"
+description: Let administrators establish persistent physical boards that expose one shared quest system.
+status: backlog
+---
+
+# US-002: Create and use shared quest boards
+
+As an **administrator**, I want to turn a targeted block into a quest board so that players can interact with quests at controlled physical locations.
+
+## Acceptance criteria
+
+- [ ] An authorized administrator can use `/questadmin createboard` to register the block they are targeting.
+- [ ] Creation rejects a missing, invalid, or already registered target without changing state.
+- [ ] Registered boards persist across server restarts with their world and block coordinates.
+- [ ] Interacting with any registered board opens the quest-board interface.
+- [ ] Every registered board exposes the same global quests and claimable items.
+- [ ] The interface uses Purpur's supported native dialog API and follows the interaction style of Spigot Base.
+- [ ] Ordinary block interaction is not intercepted at unregistered locations.
+- [ ] Administrative actions require the `spigotquestboard.admin` permission, granted to server operators by default.
+- [ ] Automated tests verify board registration, persistence, shared visibility, authorization, and interaction routing.
+
+## Related
+
+- [US-003: Create a block-delivery quest](us-003-create-a-block-delivery-quest.md)
+- [US-004: Browse available quests](us-004-browse-available-quests.md)