Add v0.9 plan baseline + verify repo health commands#68
Merged
jacuzzicoding merged 1 commit intoMay 3, 2026
Merged
Conversation
Codex created this pull request from a session on behalf of
jacuzzicoding
May 3, 2026 23:27
View session
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jacuzzicoding
merged commit 57967fc
into
feature/v09-phase-4-townmanager
2 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR establishes a clean baseline for bringing a peer agent into the v0.9.0-beta revamp workflow, where repo files (
CLAUDE.md,docs/v0.9-plan.md) are the shared, canonical context and locked decisions (notably game immutability post-create) must not be “corrected” during review.Context alignment
docs/v0.9-plan.mdincludes the locked decisions block (Decision 1–10), including TownManager implications and the explicit “no game<select>on edit” rule.Repo validation contract
npm run lint,npm test,npm run build(perpackage.jsonscripts).Example (repo’s validation surface):
{ "scripts": { "lint": "eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0", "test": "vitest run", "build": "tsc && vite build" } }