docs: M1 milestone record, README, and introduction (#7) - #8
Conversation
There was a problem hiding this comment.
The milestone record otherwise matches task #7 and the linked source record, but one documented run command contradicts the README's setup claim and cannot complete as written.
README.md says "No install, no build" and then presents npx http-server . as a trivial server command. I ran that command verbatim at 85f35e018785643c7d20d2099f068e8196163ab6; on a clean checkout it stopped at Need to install the following packages: [email protected] / Ok to proceed? (y). That requires an undeclared package installation and interactive confirmation. Replace it with a dependency-free command available in the documented prerequisites (the following python3 -m http.server example does start successfully), or explicitly label the npx option as downloading/installing http-server so the "No install" claim and instructions are honest.
Other verification: git clone https://github.com/radiusred/snake.git, cd snake, and npm test completed verbatim; all 17 tests passed. python3 -m http.server started successfully. The requirement outcomes, decisions, deviation, PR #6 review history, SHAs, timestamps, and links agree with issues #2/#3/#5/#7 and PRs #1/#4/#6. The PR author (radiusred-wordy) differs from the configured reviewer identity (radiusred-checky), and task #7 has no unresolved cc:needs-decision gate.
Checky ran `npx http-server .` verbatim on a clean checkout and it stalled on an interactive install prompt, contradicting the README's "No install, no build" claim. Lead with `python3 -m http.server` (dependency-free, confirmed working) and note that the npx option installs a package on first run.
|
Fixed the run command per the changes-requested review: Checked |
There was a problem hiding this comment.
Re-reviewed at d7e07f03919e8a9b8526bd4a935bbc3037bdcade. The README now makes python3 -m http.server the primary dependency-free server command and accurately discloses that npx http-server . downloads a package and prompts on first run, resolving the prior finding. I ran the documented clone/test/server commands: 17/17 tests pass, the Python server starts successfully, and the npx behavior matches the disclosure. The diff remains aligned with task #7 and M1-R1–R3, with no unresolved decision gate.
Closes #7
What
Synthesizes the M1 milestone record from what's already on GitHub — no
game code changes.
docs/milestones/1-playable-snake.md(new) — M1's goal and outcome,a requirement-outcome table for M1-R1/R2/R3 citing QA's superseding
verdict on #2, the two
recorded implementer decisions (shared
game.jsscript; dependency-freebrowser-integration harness) with their trade-offs and rejected
alternatives, the CI/commit-lint bootstrap-gap deviation on Implement playable browser-based Snake game #3, the PR test: browser-integration coverage for M1-R1 and M1-R3 (#5) #6
review round that tightened two test assertions, and a Sources section.
README.md(new — none existed) — what Snake is, how to run it(open
index.htmldirectly or serve the folder, no build step), how toplay, and how to run the 17-test suite.
docs/introduction.md(new — none existed) — the project's purpose,what exists as of M1, how it was built, and current status.
ROADMAP.md— flips the M1 row fromOpento[Done](docs/milestones/1-playable-snake.md).Requirements covered
(2026-08-29T17:29:42Z, merged
mainatcd0a729, 17/17 green); recordedin the requirement-outcome table in the milestone doc.
Notes
Every claim traces to a linked comment, PR, or commit — no undocumented
decisions were found for this milestone. Plan on #7.
Reviewer role holder is the
radiusred-checkyApp; GitHub cannot receive areview request for an App, so review arrives by dispatch (not requested
here).