Document Twungeon MVP and initialize Labyricorn publishing

.labyricorn/README.md

@@ -0,0 +1,11 @@
+# Labyricorn project publishing
+
+This repository owns the public project page and development log for Twungeon.
+
+- `.labyricorn/project/contents.lr` is the project exhibition record.
+- `.labyricorn/devlog/contents.lr` is the development-log index.
+- Each directory below `.labyricorn/devlog/` is one chronological entry.
+
+The project is currently in pre-development. The PRD and MVP definition are
+complete; future work should add dated devlog entries as the project moves
+through planning, implementation, testing, release, and maintenance.

.labyricorn/devlog/contents.lr

@@ -0,0 +1,8 @@
+_model: devlog
+---
+schema_version: 1
+---
+title: Twungeon development log
+---
+summary: The public record of Twungeon from pre-development through MVP delivery and beyond.
+

.labyricorn/devlog/prd-mvp-complete/contents.lr

@@ -0,0 +1,51 @@
+_model: devlog-entry
+---
+schema_version: 1
+---
+title: Twungeon begins with a shared design conversation
+---
+date: 2026-08-17
+---
+author: ChatGPT 5.6 Sol High Reasoning and Christopher Chambers
+---
+summary: An extensive design conversation between ChatGPT 5.6 Sol High Reasoning and Labyricorn (Christopher Chambers) shaped the Twungeon concept, narrowed its MVP, and produced the current product requirements document.
+---
+tags: pre-development, PRD, MVP, planning, documentation, game design, Twitch, architecture
+---
+body:
+
+Twungeon's first phase was an extensive design conversation between ChatGPT 5.6
+Sol High Reasoning and Labyricorn (Christopher Chambers). The conversation
+turned an early game idea into a testable product boundary: a shared dungeon
+where Twitch viewers watch the stream, join with `!spawn`, and control their
+own characters through a Twitch Extension.
+
+The resulting MVP is intentionally a proof of the social interaction loop. A
+party of viewers receives two action points per player phase and can move,
+attack, heal, or pass. One Goblin Guard protects the exit on a small,
+procedurally varied two-room floor. Players may fight it or run past it. Death
+matters for the current floor, Bits can provide an immediate resurrection, and
+reaching the exit brings the party forward while a total-party wipe resets the
+run.
+
+Several design decisions protect the experiment from premature complexity. The
+game remains dormant rather than resetting when no players are active. Twitch
+chat identity and Extension identity must resolve to the same stable Twitch
+user ID. The stream view needs only a temporary but understandable three-part
+layout, including a chronological action log. Balance, production art,
+progression, multiple classes, advanced enemies, anti-exploit systems, and
+long-term persistence are explicitly deferred.
+
+The conversation also made operator readiness part of the MVP. A clean checkout
+must be connectable to a Twitch channel using documented dependencies,
+credentials, Extension configuration, EventSub/chat setup, follower checks,
+identity binding, Bits events, startup steps, and troubleshooting guidance.
+The technical direction is RPGJS, Twurple, and a Twitch Extension, while the
+game rules should remain portable enough to survive a later engine change.
+
+The complete boundary and its 33 success criteria are recorded in the
+[current Twungeon MVP PRD](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_PRD_Current.md).
+This entry marks the end of product definition, not the beginning of
+implementation. Future devlog entries will record technical planning, build
+phases, validation evidence, scope changes, and what is learned from real
+viewers.

.labyricorn/project/contents.lr

@@ -0,0 +1,52 @@
+_model: project
+---
+schema_version: 1
+---
+project_id: twungeon
+---
+title: Twungeon
+---
+summary: A Twitch-controlled cooperative dungeon game where viewers share a live world, control individual characters, and discover whether the core loop is worth building into a full game.
+---
+status: active
+---
+started: 2026-08-17
+---
+author: Christopher Chambers
+---
+repository_url: https://git.labyricorn.com/Labyricorn/Twungeon
+---
+default_branch: main
+---
+tags: Twitch, Twitch Extension, RPGJS, Twurple, TypeScript, game design, pre-development, PRD, MVP, planning, architecture, documentation
+---
+body:
+
+Twungeon is a Twitch-controlled cooperative dungeon game. Viewers watch a
+shared dungeon on the stream while controlling their own characters through a
+Twitch Extension. Followers join intentionally with `!spawn`, take turns using
+simple action points, fight or evade a Goblin Guard, and cooperate to reach the
+exit.
+
+The MVP is designed to prove the complete interaction loop with real Twitch
+viewers: eligibility, identity binding, spawning, movement, combat, healing,
+death, Bits resurrection, floor advancement, and total-party reset. It uses a
+deliberately small two-room floor with one Goblin Guard so the project can test
+the social game idea before investing in balance, polish, progression, or
+production art.
+
+The stream-facing experience has three required regions: a compact
+control/status area, the shared game view, and a running action log. When no
+players are active, the current floor remains loaded in a dormant state and
+invites an eligible follower to type `!spawn`.
+
+The initial technical direction is RPGJS for the prototype game environment,
+Twurple for Twitch integration, and a Twitch Extension for player controls.
+The design keeps Twungeon's game rules separate from RPGJS where practical so
+the prototype can be replaced without discarding the validated concept.
+
+The current source of truth is the
+[Twungeon MVP Product Requirements Document](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_PRD_Current.md).
+The project is in pre-development: the PRD and MVP definition are complete,
+and this repository will document the transition through technical planning,
+implementation, testing, release preparation, and maintenance.