Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Derive the walkthrough from exploration with lexvm solve --write

Open
  • Is something wrong?
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
49/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript, yaml
Domain
cli, tooling

Research direction

Start with packages/engine/src/explore.ts to see how shortestWin is produced, then read packages/cli/src/commands/check.ts and packages/cli/src/generate/pipeline.ts to follow CLI commands and the verify gate. Check docs/spec/content-pack.md section 14 and docs/authoring/pipeline.md for the authoring rules. Done when solve can print and safely write a winning path, generate can derive one, and the documented acceptance criteria pass.

Written by the indexing model from the issue text.

Description

area: cli area: engine area: pipeline priority: high type: feature

Context

Every pack must ship a walkthrough, and lexvm check replays it. Writing a correct 60-90 step walkthrough requires simulating the game state over the whole story. That is the hardest part of pack generation for LLMs, and the part repair loops converge on most slowly: the model must predict a path the engine can compute exactly. explore already finds the shortest winning path using only actions the player UI offers (ExploreReport.shortestWin): 69 steps for the noir pack against its authored 74, and 11 for the demo pack against 17.

Scope

  • New CLI command lexvm solve <pack> [--write] [--max-states N]: runs exploration and prints the shortest winning path as canonical commands; with --write it replaces walkthrough in the pack source (the file that defines it), preserving the rest of the YAML.
  • lexvm generate: option to skip the walkthrough in the logic stage and fill it with solve before the verify gate. The generated walkthrough is still replayed by check.
  • Prompt kit and authoring guide: document that an authored walkthrough remains the intended solution and is preferred when present; solve is the fallback for generated packs.
  • Diagnostic when an authored walkthrough is much longer than the shortest win (possible detours) as info.

Acceptance criteria

  • lexvm solve packs/locked-study prints a winning path that check replays successfully.
  • --write produces a pack whose check result is unchanged apart from the walkthrough length.
  • Incomplete exploration without a win reports a clear error and does not write.
  • lexvm generate can run with walkthrough derivation enabled; tests with a fake LLM cover it.
  • Spec, authoring guide and pipeline docs updated; prompts regenerated.

References

  • packages/engine/src/explore.ts
  • packages/cli/src/commands/check.ts
  • packages/cli/src/generate/pipeline.ts
  • docs/spec/content-pack.md (section 14)
  • docs/authoring/pipeline.md
Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
28m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nullthrone/lexvm

All issues in nullthrone/lexvm

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.