Approve MVP technical and acceptance plans

.labyricorn/project/AGENTS.md

@@ -0,0 +1,33 @@
+# Instructions for the Labyricorn project record
+
+These instructions supplement `.labyricorn/AGENTS.md` and apply to the
+`project/` directory.
+
+## Record structure
+
+- Maintain exactly one project record at `project/contents.lr` using
+  `_model: project` and `schema_version: 1`.
+- Keep `project_id` stable. It is the durable identity used by the importer and
+  public URL.
+- Ask before changing the repository URL, default branch, project status,
+  author, start date, or project identity.
+- Store project-owned images in this directory and reference them by filename
+  from `contents.lr`. Only PNG, JPEG, and WebP images are accepted.
+
+## Editorial guidance
+
+- Write the exhibition page as a concise project narrative, not as a copy of
+  the repository README or as release documentation.
+- Verify technical and status claims against the repository before editing.
+- Distinguish completed work, formal design work, experiments, and future work.
+- Do not manually add repository-derived commit, license, language, release,
+  issue, star, or fork metadata. The Labyricorn importer owns those values.
+- Keep the summary suitable for listings and social previews.
+
+## Review requirements
+
+- Confirm all required project fields are present and any image reference stays
+  inside `project/`.
+- Check Markdown links are intentional HTTPS links and prose makes no unsupported
+  claims.
+- Validate the record and run `git diff --check` before committing.

.labyricorn/project/contents.lr

@@ -18,7 +18,7 @@ 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
+tags: Twitch, Twitch Extension, RPGJS, Twurple, TypeScript, game design, pre-development, PRD, MVP, planning, architecture, acceptance testing, documentation
 ---
 body:
 
@@ -45,8 +45,15 @@ 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
+The product 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.
+The approved
+[technical specification](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_Technical_Specification.md)
+defines the authoritative architecture and game behavior. The
+[acceptance-test and build checklist](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_Acceptance_Test_and_Build_Checklist.md)
+sequences implementation and maps evidence to all 33 MVP success criteria.
+
+The project remains in pre-implementation planning. These documents establish
+the build baseline, but they do not claim that runtime behavior, Twitch
+integration, or viewer validation is complete. Future records will document
+implementation, testing, release preparation, and maintenance as they occur.