rom24-quickmud-python 2.13.29__tar.gz → 2.13.31__tar.gz

{rom24_quickmud_python-2.13.29 → rom24_quickmud_python-2.13.31}/CHANGELOG.md

@@ -5,6 +5,40 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.13.31] — 2026-06-08
+
+### Changed
+
+- **Repo cleanup**: ~83 historical root-level and `docs/parity/` files archived to
+  `docs/archive/` via `git mv` — history preserved, working tree decluttered. Root
+  now contains only active files (AGENT*.md, AGENTS.md, CLAUDE.md, CHANGELOG.md,
+  README.md, requirements*.txt). `docs/validation/` directory removed (contents
+  archived).
+- **`ROM_C_SUBSYSTEM_AUDIT_TRACKER.md`**: prominent scope-caveat block added at top
+  explaining per-file-only coverage; four-layer verification stack table with links
+  to cross-file invariants, divergence roster, and differential harness.
+- **`docs/ROM_PARITY_VERIFICATION_GUIDE.md`**: updated to v2.0; new "Full Verification
+  Stack" section added as entry point covering all four layers (per-file audit,
+  cross-file invariants, divergence class roster, differential harness); original
+  three-level model now scoped as "per-file only".
+- **README**: Verification Status section replaced with four-layer table; Developer
+  Documentation section expanded with integration-test coverage tracker link.
+- **AGENTS.md**: dead link to `FUNCTION_COMPLETION_AGENT.md` (already removed) fixed.
+- **`ROM_2.4B6_PARITY_CERTIFICATION.md`** and **`ROM_API_COMPLETION_REPORT.md`**
+  moved from root to `docs/`; README links updated.
+
+## [2.13.30] — 2026-06-08
+
+### Changed
+
+- **README**: reframed project stage as "parity beta" — feature-complete and playable,
+  parity fidelity systematically hardening. Replaced internal "trust rebuild" language
+  with player/contributor-facing clarity. Badge updated from "revalidation in progress"
+  to "parity beta".
+- **ROM_C_SUBSYSTEM_AUDIT_TRACKER.md**: `handler.c` row updated — `affect_join` was
+  the last partial gap; affects system now 100% (11/11 functions). Function count
+  corrected to 75 (74 + `affect_join`).
+
 ## [2.13.29] — 2026-06-08
 
 ### Fixed

{rom24_quickmud_python-2.13.29/rom24_quickmud_python.egg-info → rom24_quickmud_python-2.13.31}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rom24-quickmud-python
-Version: 2.13.29
+Version: 2.13.31
 Summary: A modern Python port of the ROM 2.4b6 MUD engine with full telnet server and JSON world loading
 Author-email: Mark Jedrzejczyk <mark.jedrzejczyk@gmail.com>
 Maintainer-email: Mark Jedrzejczyk <mark.jedrzejczyk@gmail.com>
@@ -59,15 +59,15 @@ Dynamic: license-file
 
 # QuickMUD - A Modern ROM 2.4 Python Port
 
-[![Version](https://img.shields.io/badge/version-2.13.29-blue.svg)](https://github.com/Nostoi/rom24-quickmud-python)
+[![Version](https://img.shields.io/badge/version-2.13.31-blue.svg)](https://github.com/Nostoi/rom24-quickmud-python)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Tests](https://img.shields.io/badge/tests-5451%20passing-brightgreen.svg)](https://github.com/Nostoi/rom24-quickmud-python)
-[![ROM 2.4b Parity](https://img.shields.io/badge/ROM%202.4b%20Parity-revalidation%20in%20progress-orange.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
+[![ROM 2.4b Parity](https://img.shields.io/badge/ROM%202.4b%20Parity-parity%20beta-blue.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
 [![ROM C Audit](https://img.shields.io/badge/ROM%20C%20Audit-43%2F43%20audited-success.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
 [![Integration Tests](https://img.shields.io/badge/integration%20tests-1000%2B-brightgreen.svg)](tests/integration/)
 
-**QuickMUD is a modern Python port of the legendary ROM 2.4b6 MUD engine**, derived from ROM 2.4b6, Merc 2.1 and DikuMUD. This is a complete rewrite that brings the classic text-based MMORPG experience to modern Python with async networking and JSON world data. The engine currently has a green suite and broad ROM audit coverage, but **parity trust rebuild / revalidation is in progress** after live bugs exposed gaps in observable-behavior verification.
+**QuickMUD is a modern Python port of the legendary ROM 2.4b6 MUD engine**, derived from ROM 2.4b6, Merc 2.1 and DikuMUD. This is a complete rewrite that brings the classic text-based MMORPG experience to modern Python with async networking and JSON world data. The engine is **feature-complete and playable** — all 255 ROM commands, combat, spells, and world systems are implemented and green. Parity fidelity is in a **beta hardening phase**: high confidence on audited + test-covered surfaces, with a systematic methodology (per-file audits → cross-file invariants → differential harness) closing the remaining behavioral tail.
 
 ## 🎮 What is a MUD?
 
@@ -75,7 +75,7 @@ A "[Multi-User Dungeon](https://en.wikipedia.org/wiki/MUD)" (MUD) is a text-base
 
 ## ✨ Key Features
 
-- **🎯 ROM parity trust rebuild in progress**: audit coverage is broad, but user-visible command/session surfaces are being revalidated against stricter ROM-exact tests
+- **🎯 Parity beta**: feature-complete and playable; all 255 ROM commands implemented; parity fidelity is systematically hardened surface-by-surface via per-file audits, cross-file invariant tests, and a live differential harness against the original C engine
 - **🚀 Modern Python Architecture**: Fully async/await networking with SQLAlchemy ORM
 - **📡 Multiple Connection Options**: Telnet, WebSocket, and SSH server support
 - **🗺️ JSON World Loading**: Easy-to-edit world data with 352+ room resets
@@ -83,7 +83,7 @@ A "[Multi-User Dungeon](https://en.wikipedia.org/wiki/MUD)" (MUD) is a text-base
 - **⚔️ ROM Combat System**: Classic ROM combat mechanics and skill system
 - **👥 Social Features**: Say, tell, shout, and 100+ social interactions
 - **🛠️ Admin Commands**: Teleport, spawn, ban management, and OLC building
-- **📊 Comprehensive Testing**: 5,329 passing tests across unit, integration, and command-registry suites
+- **📊 Comprehensive Testing**: 5,451 passing tests across unit, integration, and command-registry suites
 - **🔧 ROM C-Compatible API**: Public API wrappers for external tools and scripts (27 functions)
 
 ## 📦 Installation
@@ -222,42 +222,38 @@ python -m mud  # Start development server
 
 ## 🎯 Project Status
 
-**Honest one-line summary:** broad implementation and audit coverage of ROM 2.4b6
-is complete and the test suite is green, but the project is in a **verification
-trust-rebuild phase** — "audited" means a per-file audit document exists, not that
-behavior is proven bug-free, and a small number of parity gaps remain open.
-
-- **Version**: 2.13.29
-- **ROM 2.4b Gameplay Parity**: ⚠️ **broadly implemented, verification hardening in
-  progress** — combat, skills, spells, movement, communication, world/db, save/load,
-  mob programs, and all 255 ROM commands are implemented and pass their tests. However,
-  some surfaces that were previously marked "verified" were only smoke-tested, and are
-  being rechecked with ROM-exact assertions. Treat the audit coverage below as
-  *process completeness*, not a guarantee of bit-for-bit correctness.
-- **ROM C Source Audit**: ✅ **100% audit-bound coverage** — 43 of 43 applicable ROM C
-  files have a completed audit document, with 3 additional ROM files intentionally N/A
-  (`recycle.c`, `mem.c`, `imc.c`). This tracks that every applicable file has been
-  *reviewed and documented*; it does not by itself certify behavioral parity (three
-  production bugs this year shipped against files marked ≥95% audited — see the
-  cross-file invariants tracker for why per-file audits are necessary but not
-  sufficient). See
+**Stage: parity beta** — feature-complete and playable; parity fidelity is being
+systematically hardened toward ROM-exact behavioral equivalence.
+
+- **Version**: 2.13.31
+- **Playability**: ✅ All 255 ROM commands implemented. Combat, spells, skills,
+  movement, shops, mob programs, OLC building, and admin tools work and pass their
+  tests. You can run a server and play today.
+- **Parity confidence**: high on audited + test-covered surfaces; moderate on the
+  uncovered tail (surfaces not yet reached by the differential harness). "Parity beta"
+  means: the engine behaves like ROM on everything we've checked; there may be
+  edge-case divergences we haven't checked yet. The standard stages (alpha/beta/GA)
+  measure feature completeness — for a port the meaningful axis is *parity confidence*,
+  not whether features exist.
+- **ROM C Source Audit**: ✅ **43 / 43 files audited** — every applicable ROM C file
+  has a completed audit document (3 intentional N/A: `recycle.c`, `mem.c`, `imc.c`).
+  Per-file audits confirm *what was reviewed*; they don't by themselves certify
+  bit-for-bit behavioral parity. See
   [`docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md`](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md).
-  Notable: `handler.c` affects system is now **100% complete** (11/11 functions,
-  including `affect_join` merge semantics — 2026-06-08).
-- **Cross-file Invariants**: ✅ **25/25 enforced** — message delivery, prompt clamping,
-  registry membership, same-room combat, death/connection behavior, RNG determinism,
-  persistence coherence, and room-flag survival (`.are`→JSON→runtime) are locked by
-  dedicated regression tests. This layer exists specifically to catch the contract
-  violations that per-file audits miss.
-- **Open parity gaps**: a small backlog of identified divergences is tracked and being
-  closed one failing-test-first commit at a time. Open gaps are logged in the per-file
-  `docs/parity/*_C_AUDIT.md` documents.
-- **Test Suite**: ✅ **5451 passed, 4 skipped** (full `pytest` run, ~150s parallel).
-  Three layers — unit (`tests/test_*.py`), integration (`tests/integration/`), and
-  command-registry (`test_all_commands.py`).
-- **Active focus**: trust rebuild — replacing weak smoke assertions with ROM-exact
-  output, boundary, and runtime-path tests on the highest-risk user-visible surfaces,
-  and closing the remaining documented parity gaps.
+- **Cross-file Invariants**: ✅ **25 / 25 enforced** — contracts that span modules
+  (message delivery, prompt clamping, registry membership, same-room combat,
+  death/reconnect ordering, RNG determinism, persistence coherence, room-flag survival)
+  are each locked by a dedicated regression test. This layer catches the class of bug
+  that per-file audits structurally miss.
+- **Differential harness**: ✅ live — the original ROM 2.4b6 C engine and the Python
+  port are run through identical scripted scenarios and their observable state is
+  diffed. Any behavioral divergence surfaces mechanically rather than requiring a
+  hand-written assertion. Coverage is growing; uncovered surfaces are the remaining
+  parity-confidence gap.
+- **Test Suite**: ✅ **5,451 passed, 4 skipped** (full `pytest` run, ~150s parallel).
+  Unit, integration, command-registry, and differential-harness layers.
+- **Active focus**: expanding differential harness scenario coverage and closing the
+  identified gap backlog (tracked in `docs/parity/*_C_AUDIT.md`).
 - **Compatibility**: Python 3.10+, cross-platform
 
 ## 🏛️ Architecture
@@ -279,9 +275,18 @@ Contributions are welcome! Please read our [Contributing Guidelines](CONTRIBUTIN
 ## 📚 Documentation
 
 ### Verification Status
-- [ROM C subsystem tracker](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md) - canonical audit surface
-- [ROM parity verification guide](docs/ROM_PARITY_VERIFICATION_GUIDE.md) - current verification standard
-- [ROM 2.4b6 Parity Certification](ROM_2.4B6_PARITY_CERTIFICATION.md) - historical certification document; claims are being revalidated
+
+The parity verification stack has four layers — consult all four, not just the first:
+
+| Layer | What it measures | Document |
+|-------|-----------------|----------|
+| Per-file audit | Every ROM C function has a Python equivalent | [ROM C subsystem tracker](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md) |
+| Cross-file invariants | Contracts spanning modules (message delivery, registry, RNG, identity, …) | [Cross-file invariants tracker](docs/parity/CROSS_FILE_INVARIANTS_TRACKER.md) — 25 enforced |
+| Divergence class roster | Structural C↔Python gaps (async, int-math, pointer identity, …) | [Divergence class roster](docs/parity/DIVERGENCE_CLASS_ROSTER.md) |
+| Differential harness | C engine vs Python port, identical scenarios, state diffed | [Diff harness findings](tools/diff_harness/FINDINGS.md) |
+
+- [ROM parity verification guide](docs/ROM_PARITY_VERIFICATION_GUIDE.md) — methodology, confidence tiers, when to use each layer
+- [ROM 2.4b6 Parity Certification](docs/ROM_2.4B6_PARITY_CERTIFICATION.md) — historical document; predates cross-file invariants methodology
 
 ### User Documentation
 - [User Guide](docs/USER_GUIDE.md) - Player and server operator documentation
@@ -289,8 +294,9 @@ Contributions are welcome! Please read our [Contributing Guidelines](CONTRIBUTIN
 - [Builder Migration Guide](docs/BUILDER_MIGRATION_GUIDE.md) - For ROM builders transitioning to QuickMUD
 
 ### Developer Documentation
-- [ROM Parity Feature Tracker](docs/parity/ROM_PARITY_FEATURE_TRACKER.md) - Detailed parity status
-- [ROM API Reference](ROM_API_COMPLETION_REPORT.md) - ROM C-compatible public API
+- [ROM Parity Feature Tracker](docs/parity/ROM_PARITY_FEATURE_TRACKER.md) - Feature-level parity backlog
+- [Integration Test Coverage Tracker](docs/parity/INTEGRATION_TEST_COVERAGE_TRACKER.md) - Coverage by gameplay system
+- [ROM API Reference](docs/ROM_API_COMPLETION_REPORT.md) - ROM C-compatible public API
 - [Installation Guide](docs/installation.md)
 - [Configuration](docs/configuration.md)
 - [World Building](docs/world-building.md)

{rom24_quickmud_python-2.13.29 → rom24_quickmud_python-2.13.31}/README.md

@@ -1,14 +1,14 @@
 # QuickMUD - A Modern ROM 2.4 Python Port
 
-[![Version](https://img.shields.io/badge/version-2.13.29-blue.svg)](https://github.com/Nostoi/rom24-quickmud-python)
+[![Version](https://img.shields.io/badge/version-2.13.31-blue.svg)](https://github.com/Nostoi/rom24-quickmud-python)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Tests](https://img.shields.io/badge/tests-5451%20passing-brightgreen.svg)](https://github.com/Nostoi/rom24-quickmud-python)
-[![ROM 2.4b Parity](https://img.shields.io/badge/ROM%202.4b%20Parity-revalidation%20in%20progress-orange.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
+[![ROM 2.4b Parity](https://img.shields.io/badge/ROM%202.4b%20Parity-parity%20beta-blue.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
 [![ROM C Audit](https://img.shields.io/badge/ROM%20C%20Audit-43%2F43%20audited-success.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
 [![Integration Tests](https://img.shields.io/badge/integration%20tests-1000%2B-brightgreen.svg)](tests/integration/)
 
-**QuickMUD is a modern Python port of the legendary ROM 2.4b6 MUD engine**, derived from ROM 2.4b6, Merc 2.1 and DikuMUD. This is a complete rewrite that brings the classic text-based MMORPG experience to modern Python with async networking and JSON world data. The engine currently has a green suite and broad ROM audit coverage, but **parity trust rebuild / revalidation is in progress** after live bugs exposed gaps in observable-behavior verification.
+**QuickMUD is a modern Python port of the legendary ROM 2.4b6 MUD engine**, derived from ROM 2.4b6, Merc 2.1 and DikuMUD. This is a complete rewrite that brings the classic text-based MMORPG experience to modern Python with async networking and JSON world data. The engine is **feature-complete and playable** — all 255 ROM commands, combat, spells, and world systems are implemented and green. Parity fidelity is in a **beta hardening phase**: high confidence on audited + test-covered surfaces, with a systematic methodology (per-file audits → cross-file invariants → differential harness) closing the remaining behavioral tail.
 
 ## 🎮 What is a MUD?
 
@@ -16,7 +16,7 @@ A "[Multi-User Dungeon](https://en.wikipedia.org/wiki/MUD)" (MUD) is a text-base
 
 ## ✨ Key Features
 
-- **🎯 ROM parity trust rebuild in progress**: audit coverage is broad, but user-visible command/session surfaces are being revalidated against stricter ROM-exact tests
+- **🎯 Parity beta**: feature-complete and playable; all 255 ROM commands implemented; parity fidelity is systematically hardened surface-by-surface via per-file audits, cross-file invariant tests, and a live differential harness against the original C engine
 - **🚀 Modern Python Architecture**: Fully async/await networking with SQLAlchemy ORM
 - **📡 Multiple Connection Options**: Telnet, WebSocket, and SSH server support
 - **🗺️ JSON World Loading**: Easy-to-edit world data with 352+ room resets
@@ -24,7 +24,7 @@ A "[Multi-User Dungeon](https://en.wikipedia.org/wiki/MUD)" (MUD) is a text-base
 - **⚔️ ROM Combat System**: Classic ROM combat mechanics and skill system
 - **👥 Social Features**: Say, tell, shout, and 100+ social interactions
 - **🛠️ Admin Commands**: Teleport, spawn, ban management, and OLC building
-- **📊 Comprehensive Testing**: 5,329 passing tests across unit, integration, and command-registry suites
+- **📊 Comprehensive Testing**: 5,451 passing tests across unit, integration, and command-registry suites
 - **🔧 ROM C-Compatible API**: Public API wrappers for external tools and scripts (27 functions)
 
 ## 📦 Installation
@@ -163,42 +163,38 @@ python -m mud  # Start development server
 
 ## 🎯 Project Status
 
-**Honest one-line summary:** broad implementation and audit coverage of ROM 2.4b6
-is complete and the test suite is green, but the project is in a **verification
-trust-rebuild phase** — "audited" means a per-file audit document exists, not that
-behavior is proven bug-free, and a small number of parity gaps remain open.
-
-- **Version**: 2.13.29
-- **ROM 2.4b Gameplay Parity**: ⚠️ **broadly implemented, verification hardening in
-  progress** — combat, skills, spells, movement, communication, world/db, save/load,
-  mob programs, and all 255 ROM commands are implemented and pass their tests. However,
-  some surfaces that were previously marked "verified" were only smoke-tested, and are
-  being rechecked with ROM-exact assertions. Treat the audit coverage below as
-  *process completeness*, not a guarantee of bit-for-bit correctness.
-- **ROM C Source Audit**: ✅ **100% audit-bound coverage** — 43 of 43 applicable ROM C
-  files have a completed audit document, with 3 additional ROM files intentionally N/A
-  (`recycle.c`, `mem.c`, `imc.c`). This tracks that every applicable file has been
-  *reviewed and documented*; it does not by itself certify behavioral parity (three
-  production bugs this year shipped against files marked ≥95% audited — see the
-  cross-file invariants tracker for why per-file audits are necessary but not
-  sufficient). See
+**Stage: parity beta** — feature-complete and playable; parity fidelity is being
+systematically hardened toward ROM-exact behavioral equivalence.
+
+- **Version**: 2.13.31
+- **Playability**: ✅ All 255 ROM commands implemented. Combat, spells, skills,
+  movement, shops, mob programs, OLC building, and admin tools work and pass their
+  tests. You can run a server and play today.
+- **Parity confidence**: high on audited + test-covered surfaces; moderate on the
+  uncovered tail (surfaces not yet reached by the differential harness). "Parity beta"
+  means: the engine behaves like ROM on everything we've checked; there may be
+  edge-case divergences we haven't checked yet. The standard stages (alpha/beta/GA)
+  measure feature completeness — for a port the meaningful axis is *parity confidence*,
+  not whether features exist.
+- **ROM C Source Audit**: ✅ **43 / 43 files audited** — every applicable ROM C file
+  has a completed audit document (3 intentional N/A: `recycle.c`, `mem.c`, `imc.c`).
+  Per-file audits confirm *what was reviewed*; they don't by themselves certify
+  bit-for-bit behavioral parity. See
   [`docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md`](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md).
-  Notable: `handler.c` affects system is now **100% complete** (11/11 functions,
-  including `affect_join` merge semantics — 2026-06-08).
-- **Cross-file Invariants**: ✅ **25/25 enforced** — message delivery, prompt clamping,
-  registry membership, same-room combat, death/connection behavior, RNG determinism,
-  persistence coherence, and room-flag survival (`.are`→JSON→runtime) are locked by
-  dedicated regression tests. This layer exists specifically to catch the contract
-  violations that per-file audits miss.
-- **Open parity gaps**: a small backlog of identified divergences is tracked and being
-  closed one failing-test-first commit at a time. Open gaps are logged in the per-file
-  `docs/parity/*_C_AUDIT.md` documents.
-- **Test Suite**: ✅ **5451 passed, 4 skipped** (full `pytest` run, ~150s parallel).
-  Three layers — unit (`tests/test_*.py`), integration (`tests/integration/`), and
-  command-registry (`test_all_commands.py`).
-- **Active focus**: trust rebuild — replacing weak smoke assertions with ROM-exact
-  output, boundary, and runtime-path tests on the highest-risk user-visible surfaces,
-  and closing the remaining documented parity gaps.
+- **Cross-file Invariants**: ✅ **25 / 25 enforced** — contracts that span modules
+  (message delivery, prompt clamping, registry membership, same-room combat,
+  death/reconnect ordering, RNG determinism, persistence coherence, room-flag survival)
+  are each locked by a dedicated regression test. This layer catches the class of bug
+  that per-file audits structurally miss.
+- **Differential harness**: ✅ live — the original ROM 2.4b6 C engine and the Python
+  port are run through identical scripted scenarios and their observable state is
+  diffed. Any behavioral divergence surfaces mechanically rather than requiring a
+  hand-written assertion. Coverage is growing; uncovered surfaces are the remaining
+  parity-confidence gap.
+- **Test Suite**: ✅ **5,451 passed, 4 skipped** (full `pytest` run, ~150s parallel).
+  Unit, integration, command-registry, and differential-harness layers.
+- **Active focus**: expanding differential harness scenario coverage and closing the
+  identified gap backlog (tracked in `docs/parity/*_C_AUDIT.md`).
 - **Compatibility**: Python 3.10+, cross-platform
 
 ## 🏛️ Architecture
@@ -220,9 +216,18 @@ Contributions are welcome! Please read our [Contributing Guidelines](CONTRIBUTIN
 ## 📚 Documentation
 
 ### Verification Status
-- [ROM C subsystem tracker](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md) - canonical audit surface
-- [ROM parity verification guide](docs/ROM_PARITY_VERIFICATION_GUIDE.md) - current verification standard
-- [ROM 2.4b6 Parity Certification](ROM_2.4B6_PARITY_CERTIFICATION.md) - historical certification document; claims are being revalidated
+
+The parity verification stack has four layers — consult all four, not just the first:
+
+| Layer | What it measures | Document |
+|-------|-----------------|----------|
+| Per-file audit | Every ROM C function has a Python equivalent | [ROM C subsystem tracker](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md) |
+| Cross-file invariants | Contracts spanning modules (message delivery, registry, RNG, identity, …) | [Cross-file invariants tracker](docs/parity/CROSS_FILE_INVARIANTS_TRACKER.md) — 25 enforced |
+| Divergence class roster | Structural C↔Python gaps (async, int-math, pointer identity, …) | [Divergence class roster](docs/parity/DIVERGENCE_CLASS_ROSTER.md) |
+| Differential harness | C engine vs Python port, identical scenarios, state diffed | [Diff harness findings](tools/diff_harness/FINDINGS.md) |
+
+- [ROM parity verification guide](docs/ROM_PARITY_VERIFICATION_GUIDE.md) — methodology, confidence tiers, when to use each layer
+- [ROM 2.4b6 Parity Certification](docs/ROM_2.4B6_PARITY_CERTIFICATION.md) — historical document; predates cross-file invariants methodology
 
 ### User Documentation
 - [User Guide](docs/USER_GUIDE.md) - Player and server operator documentation
@@ -230,8 +235,9 @@ Contributions are welcome! Please read our [Contributing Guidelines](CONTRIBUTIN
 - [Builder Migration Guide](docs/BUILDER_MIGRATION_GUIDE.md) - For ROM builders transitioning to QuickMUD
 
 ### Developer Documentation
-- [ROM Parity Feature Tracker](docs/parity/ROM_PARITY_FEATURE_TRACKER.md) - Detailed parity status
-- [ROM API Reference](ROM_API_COMPLETION_REPORT.md) - ROM C-compatible public API
+- [ROM Parity Feature Tracker](docs/parity/ROM_PARITY_FEATURE_TRACKER.md) - Feature-level parity backlog
+- [Integration Test Coverage Tracker](docs/parity/INTEGRATION_TEST_COVERAGE_TRACKER.md) - Coverage by gameplay system
+- [ROM API Reference](docs/ROM_API_COMPLETION_REPORT.md) - ROM C-compatible public API
 - [Installation Guide](docs/installation.md)
 - [Configuration](docs/configuration.md)
 - [World Building](docs/world-building.md)

{rom24_quickmud_python-2.13.29 → rom24_quickmud_python-2.13.31}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "rom24-quickmud-python"
-version = "2.13.29"
+version = "2.13.31"
 description = "A modern Python port of the ROM 2.4b6 MUD engine with full telnet server and JSON world loading"
 readme = "README.md"
 license = "MIT"

{rom24_quickmud_python-2.13.29 → rom24_quickmud_python-2.13.31/rom24_quickmud_python.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rom24-quickmud-python
-Version: 2.13.29
+Version: 2.13.31
 Summary: A modern Python port of the ROM 2.4b6 MUD engine with full telnet server and JSON world loading
 Author-email: Mark Jedrzejczyk <mark.jedrzejczyk@gmail.com>
 Maintainer-email: Mark Jedrzejczyk <mark.jedrzejczyk@gmail.com>
@@ -59,15 +59,15 @@ Dynamic: license-file
 
 # QuickMUD - A Modern ROM 2.4 Python Port
 
-[![Version](https://img.shields.io/badge/version-2.13.29-blue.svg)](https://github.com/Nostoi/rom24-quickmud-python)
+[![Version](https://img.shields.io/badge/version-2.13.31-blue.svg)](https://github.com/Nostoi/rom24-quickmud-python)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Tests](https://img.shields.io/badge/tests-5451%20passing-brightgreen.svg)](https://github.com/Nostoi/rom24-quickmud-python)
-[![ROM 2.4b Parity](https://img.shields.io/badge/ROM%202.4b%20Parity-revalidation%20in%20progress-orange.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
+[![ROM 2.4b Parity](https://img.shields.io/badge/ROM%202.4b%20Parity-parity%20beta-blue.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
 [![ROM C Audit](https://img.shields.io/badge/ROM%20C%20Audit-43%2F43%20audited-success.svg)](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md)
 [![Integration Tests](https://img.shields.io/badge/integration%20tests-1000%2B-brightgreen.svg)](tests/integration/)
 
-**QuickMUD is a modern Python port of the legendary ROM 2.4b6 MUD engine**, derived from ROM 2.4b6, Merc 2.1 and DikuMUD. This is a complete rewrite that brings the classic text-based MMORPG experience to modern Python with async networking and JSON world data. The engine currently has a green suite and broad ROM audit coverage, but **parity trust rebuild / revalidation is in progress** after live bugs exposed gaps in observable-behavior verification.
+**QuickMUD is a modern Python port of the legendary ROM 2.4b6 MUD engine**, derived from ROM 2.4b6, Merc 2.1 and DikuMUD. This is a complete rewrite that brings the classic text-based MMORPG experience to modern Python with async networking and JSON world data. The engine is **feature-complete and playable** — all 255 ROM commands, combat, spells, and world systems are implemented and green. Parity fidelity is in a **beta hardening phase**: high confidence on audited + test-covered surfaces, with a systematic methodology (per-file audits → cross-file invariants → differential harness) closing the remaining behavioral tail.
 
 ## 🎮 What is a MUD?
 
@@ -75,7 +75,7 @@ A "[Multi-User Dungeon](https://en.wikipedia.org/wiki/MUD)" (MUD) is a text-base
 
 ## ✨ Key Features
 
-- **🎯 ROM parity trust rebuild in progress**: audit coverage is broad, but user-visible command/session surfaces are being revalidated against stricter ROM-exact tests
+- **🎯 Parity beta**: feature-complete and playable; all 255 ROM commands implemented; parity fidelity is systematically hardened surface-by-surface via per-file audits, cross-file invariant tests, and a live differential harness against the original C engine
 - **🚀 Modern Python Architecture**: Fully async/await networking with SQLAlchemy ORM
 - **📡 Multiple Connection Options**: Telnet, WebSocket, and SSH server support
 - **🗺️ JSON World Loading**: Easy-to-edit world data with 352+ room resets
@@ -83,7 +83,7 @@ A "[Multi-User Dungeon](https://en.wikipedia.org/wiki/MUD)" (MUD) is a text-base
 - **⚔️ ROM Combat System**: Classic ROM combat mechanics and skill system
 - **👥 Social Features**: Say, tell, shout, and 100+ social interactions
 - **🛠️ Admin Commands**: Teleport, spawn, ban management, and OLC building
-- **📊 Comprehensive Testing**: 5,329 passing tests across unit, integration, and command-registry suites
+- **📊 Comprehensive Testing**: 5,451 passing tests across unit, integration, and command-registry suites
 - **🔧 ROM C-Compatible API**: Public API wrappers for external tools and scripts (27 functions)
 
 ## 📦 Installation
@@ -222,42 +222,38 @@ python -m mud  # Start development server
 
 ## 🎯 Project Status
 
-**Honest one-line summary:** broad implementation and audit coverage of ROM 2.4b6
-is complete and the test suite is green, but the project is in a **verification
-trust-rebuild phase** — "audited" means a per-file audit document exists, not that
-behavior is proven bug-free, and a small number of parity gaps remain open.
-
-- **Version**: 2.13.29
-- **ROM 2.4b Gameplay Parity**: ⚠️ **broadly implemented, verification hardening in
-  progress** — combat, skills, spells, movement, communication, world/db, save/load,
-  mob programs, and all 255 ROM commands are implemented and pass their tests. However,
-  some surfaces that were previously marked "verified" were only smoke-tested, and are
-  being rechecked with ROM-exact assertions. Treat the audit coverage below as
-  *process completeness*, not a guarantee of bit-for-bit correctness.
-- **ROM C Source Audit**: ✅ **100% audit-bound coverage** — 43 of 43 applicable ROM C
-  files have a completed audit document, with 3 additional ROM files intentionally N/A
-  (`recycle.c`, `mem.c`, `imc.c`). This tracks that every applicable file has been
-  *reviewed and documented*; it does not by itself certify behavioral parity (three
-  production bugs this year shipped against files marked ≥95% audited — see the
-  cross-file invariants tracker for why per-file audits are necessary but not
-  sufficient). See
+**Stage: parity beta** — feature-complete and playable; parity fidelity is being
+systematically hardened toward ROM-exact behavioral equivalence.
+
+- **Version**: 2.13.31
+- **Playability**: ✅ All 255 ROM commands implemented. Combat, spells, skills,
+  movement, shops, mob programs, OLC building, and admin tools work and pass their
+  tests. You can run a server and play today.
+- **Parity confidence**: high on audited + test-covered surfaces; moderate on the
+  uncovered tail (surfaces not yet reached by the differential harness). "Parity beta"
+  means: the engine behaves like ROM on everything we've checked; there may be
+  edge-case divergences we haven't checked yet. The standard stages (alpha/beta/GA)
+  measure feature completeness — for a port the meaningful axis is *parity confidence*,
+  not whether features exist.
+- **ROM C Source Audit**: ✅ **43 / 43 files audited** — every applicable ROM C file
+  has a completed audit document (3 intentional N/A: `recycle.c`, `mem.c`, `imc.c`).
+  Per-file audits confirm *what was reviewed*; they don't by themselves certify
+  bit-for-bit behavioral parity. See
   [`docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md`](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md).
-  Notable: `handler.c` affects system is now **100% complete** (11/11 functions,
-  including `affect_join` merge semantics — 2026-06-08).
-- **Cross-file Invariants**: ✅ **25/25 enforced** — message delivery, prompt clamping,
-  registry membership, same-room combat, death/connection behavior, RNG determinism,
-  persistence coherence, and room-flag survival (`.are`→JSON→runtime) are locked by
-  dedicated regression tests. This layer exists specifically to catch the contract
-  violations that per-file audits miss.
-- **Open parity gaps**: a small backlog of identified divergences is tracked and being
-  closed one failing-test-first commit at a time. Open gaps are logged in the per-file
-  `docs/parity/*_C_AUDIT.md` documents.
-- **Test Suite**: ✅ **5451 passed, 4 skipped** (full `pytest` run, ~150s parallel).
-  Three layers — unit (`tests/test_*.py`), integration (`tests/integration/`), and
-  command-registry (`test_all_commands.py`).
-- **Active focus**: trust rebuild — replacing weak smoke assertions with ROM-exact
-  output, boundary, and runtime-path tests on the highest-risk user-visible surfaces,
-  and closing the remaining documented parity gaps.
+- **Cross-file Invariants**: ✅ **25 / 25 enforced** — contracts that span modules
+  (message delivery, prompt clamping, registry membership, same-room combat,
+  death/reconnect ordering, RNG determinism, persistence coherence, room-flag survival)
+  are each locked by a dedicated regression test. This layer catches the class of bug
+  that per-file audits structurally miss.
+- **Differential harness**: ✅ live — the original ROM 2.4b6 C engine and the Python
+  port are run through identical scripted scenarios and their observable state is
+  diffed. Any behavioral divergence surfaces mechanically rather than requiring a
+  hand-written assertion. Coverage is growing; uncovered surfaces are the remaining
+  parity-confidence gap.
+- **Test Suite**: ✅ **5,451 passed, 4 skipped** (full `pytest` run, ~150s parallel).
+  Unit, integration, command-registry, and differential-harness layers.
+- **Active focus**: expanding differential harness scenario coverage and closing the
+  identified gap backlog (tracked in `docs/parity/*_C_AUDIT.md`).
 - **Compatibility**: Python 3.10+, cross-platform
 
 ## 🏛️ Architecture
@@ -279,9 +275,18 @@ Contributions are welcome! Please read our [Contributing Guidelines](CONTRIBUTIN
 ## 📚 Documentation
 
 ### Verification Status
-- [ROM C subsystem tracker](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md) - canonical audit surface
-- [ROM parity verification guide](docs/ROM_PARITY_VERIFICATION_GUIDE.md) - current verification standard
-- [ROM 2.4b6 Parity Certification](ROM_2.4B6_PARITY_CERTIFICATION.md) - historical certification document; claims are being revalidated
+
+The parity verification stack has four layers — consult all four, not just the first:
+
+| Layer | What it measures | Document |
+|-------|-----------------|----------|
+| Per-file audit | Every ROM C function has a Python equivalent | [ROM C subsystem tracker](docs/parity/ROM_C_SUBSYSTEM_AUDIT_TRACKER.md) |
+| Cross-file invariants | Contracts spanning modules (message delivery, registry, RNG, identity, …) | [Cross-file invariants tracker](docs/parity/CROSS_FILE_INVARIANTS_TRACKER.md) — 25 enforced |
+| Divergence class roster | Structural C↔Python gaps (async, int-math, pointer identity, …) | [Divergence class roster](docs/parity/DIVERGENCE_CLASS_ROSTER.md) |
+| Differential harness | C engine vs Python port, identical scenarios, state diffed | [Diff harness findings](tools/diff_harness/FINDINGS.md) |
+
+- [ROM parity verification guide](docs/ROM_PARITY_VERIFICATION_GUIDE.md) — methodology, confidence tiers, when to use each layer
+- [ROM 2.4b6 Parity Certification](docs/ROM_2.4B6_PARITY_CERTIFICATION.md) — historical document; predates cross-file invariants methodology
 
 ### User Documentation
 - [User Guide](docs/USER_GUIDE.md) - Player and server operator documentation
@@ -289,8 +294,9 @@ Contributions are welcome! Please read our [Contributing Guidelines](CONTRIBUTIN
 - [Builder Migration Guide](docs/BUILDER_MIGRATION_GUIDE.md) - For ROM builders transitioning to QuickMUD
 
 ### Developer Documentation
-- [ROM Parity Feature Tracker](docs/parity/ROM_PARITY_FEATURE_TRACKER.md) - Detailed parity status
-- [ROM API Reference](ROM_API_COMPLETION_REPORT.md) - ROM C-compatible public API
+- [ROM Parity Feature Tracker](docs/parity/ROM_PARITY_FEATURE_TRACKER.md) - Feature-level parity backlog
+- [Integration Test Coverage Tracker](docs/parity/INTEGRATION_TEST_COVERAGE_TRACKER.md) - Coverage by gameplay system
+- [ROM API Reference](docs/ROM_API_COMPLETION_REPORT.md) - ROM C-compatible public API
 - [Installation Guide](docs/installation.md)
 - [Configuration](docs/configuration.md)
 - [World Building](docs/world-building.md)