Update module base path to git.eeqj.de/sneak/rgoue

go.mod, term/ and cmd/ imports, the ARCHITECTURE.md module references,
and the in-game version string. User request; the repo already lives
at this remote.

TODO.md

@@ -29,11 +29,14 @@ Refactor ground rules:
 
 # Next Step
 
-Update the module base path to git.eeqj.de/sneak/rgoue (user request
-2026-07-06): go.mod, all imports in term/ and cmd/, and doc references.
+Adopt the house Go linting standards: copy .golangci.yml from the
+prompts repo and bring game/, term/, and cmd/ lint-clean (the port is
+greenfield code, so no exemptions apply).
 
 # Completed Steps
 
+- 2026-07-06 Module base path updated to git.eeqj.de/sneak/rgoue
+  (go.mod, term/ and cmd/ imports, ARCHITECTURE.md, version string).
 - 2026-07-06 Refactor step 3 (refactor/object-fields): Object.Arm split
   into ArmorClass/Charges/GoldValue/Bonus (rings); Stats.Arm →
   ArmorClass; damage strings parsed once into DiceSpec at table
@@ -73,48 +76,45 @@ Update the module base path to git.eeqj.de/sneak/rgoue (user request
 
 # Future Steps
 
-1. Adopt the house Go linting standards: copy .golangci.yml from the
-   prompts repo and bring game/, term/, and cmd/ lint-clean (the port
-   is greenfield code, so no exemptions apply).
-2. Refactor step 4: method renames, movement/world subsystem
+1. Refactor step 4: method renames, movement/world subsystem
    (doMove→moveHero, beTrapped→springTrap, rndmove→randomStep,
    doRooms/doPassages/doMaze→digRooms/digPassages/digMaze,
    chgStr→changeStrength, ...); remove the goto/label flows in doMove,
    dispatch, and saveGame in favor of loops and helpers.
-3. Refactor step 5: method renames, items/combat/UI subsystems
+2. Refactor step 5: method renames, items/combat/UI subsystems
    (invName→inventoryName, rollEm→rollAttacks, doPot→applyPotionFuse,
    getItem→promptPackItem returning (obj, ok), getDir→promptDirection);
    int status codes (attack returning -1) become named results. Two or
    three commits, one subsystem each.
-4. Refactor step 6: extract types from the god object — MessageLine
+3. Refactor step 6: extract types from the god object — MessageLine
    owns the msg/addmsg/endmsg machinery; pack/inventory operations move
    onto *Player; monster/object list management and map queries
    consolidate onto *Level; RogueGame keeps turn orchestration and
    cross-system effects only.
-5. Refactor step 7: effects dispatch — the giant quaff/readScroll/doZap
+4. Refactor step 7: effects dispatch — the giant quaff/readScroll/doZap
    switches become per-kind handler tables of small named methods,
    keeping effect order and RNG call sequence identical.
-6. Refactor step 8: constructor and style pass per the house
+5. Refactor step 8: constructor and style pass per the house
    styleguide — game.New(game.Params{...}) replacing NewGame(Config);
    replace the gameEnd panic unwind with error-based turn results where
    feasible; 77-column wrap sweep.
-7. Docs refresh: update ARCHITECTURE.md Part 2 and README.md for the
+6. Docs refresh: update ARCHITECTURE.md Part 2 and README.md for the
    post-refactor names; add the C name → Go name rename table.
-8. Playtest hardening pass: play several full games with the tcell
+7. Playtest hardening pass: play several full games with the tcell
     binary and extend run_test.go to script a deeper multi-level
     playthrough (descend past level 5, use potions, scrolls, zapping,
     save/restore). Fix any panics, message mismatches, or divergences
     from the C behavior that this uncovers, with regression tests.
-9. Verify the seed-compatibility claim against the C reference on
+8. Verify the seed-compatibility claim against the C reference on
     c-master: same seed, same dungeon, same item tables, for several
     seeds.
-10. Broaden unit test coverage where playtesting finds thin spots
+9. Broaden unit test coverage where playtesting finds thin spots
     (rings, sticks, wizard commands).
-11. Tag a release once a full game (Amulet retrieval and score entry)
+10. Tag a release once a full game (Amulet retrieval and score entry)
     completes without defects.
-12. Full-terminal-size support (deferred by explicit decision
+11. Full-terminal-size support (deferred by explicit decision
     2026-07-06): per-game dungeon dimensions instead of the 80x24
     constants; open design questions are resize policy, gameplay
     tuning at larger sizes, and a --classic 80x24 mode.
-13. Note: this repo is exempt from the standard policy scaffold. Do not
+12. Note: this repo is exempt from the standard policy scaffold. Do not
     add Makefile, Dockerfile, or REPO_POLICIES.md.