Ручная проверка
Installed 0.1.20 cumulative acceptance
Состояние: accepted
Что подтверждает: Exact 0.1.20+1.21.1 installed acceptance ended as a partial PASS, not a full release acceptance. Text, STT, Chat, TTS, Voice Chat, Operator Lore scopes, restart, rollback-world loading and most synchronized gameplay scenarios passed. Release defects remained and became later release gates.
Открыть доказательство ↗
Ручная проверка
Installed 0.1.21 startup blocker and safe rollback
Состояние: failed
Что подтверждает: Exact 0.1.21+1.21.1 failed during startup before world and gameplay acceptance because the production tombstone target could not be resolved. Safe rollback restored service with persistent hashes preserved. This historical negative evidence remains explicit.
Открыть доказательство ↗
Автоматическое доказательство
Corrective PRs #99–#102
Состояние: merged
Что подтверждает: PRs #99–#102 preserve vanilla water path positioning, retain filled-tombstone data, enforce exact embedded release identity and replace the production-unsafe tombstone Mixin with direct owned-source wiring. Exact-head repository, Fabric/NeoForge, remapped-package, security and applicable supply-chain gates passed.
Открыть доказательство ↗
Автоматическое доказательство
M11 Phase A risk-based acceptance PR #103
Состояние: merged
Что подтверждает: PR #103 introduced the risk-based acceptance catalogue and isolated real-server Fabric GameTests. This is development GameTest evidence, not by itself an installed release or cumulative operator acceptance.
Открыть доказательство ↗
Автоматическое доказательство
M11 Phase B production-JAR acceptance PR #104
Состояние: merged
Что подтверждает: PR #104 installed the exact remapped Fabric candidate into an isolated production server outside the Loom development classpath, reached the ready marker in separate JVM runs and preserved canonical stores across restart. This remains a bounded automated installed proof.
Открыть доказательство ↗
Автоматическое доказательство
Tombstone inventory ownership fix PR #105
Состояние: merged
Что подтверждает: PR #105 corrected the installed inventory-loss defect by serializing a captured NPC while its inventory is intact and preserving the existing drop fallback when no valid tombstone owns the body. Exact-head CI, production startup/restart, GameTests and package gates passed.
Открыть доказательство ↗
Автоматическое доказательство
Exact 0.1.25 release gate PR #107
Состояние: published
Что подтверждает: PR #107 published immutable 0.1.25+1.21.1 after the exact post-merge production gate. It is retained as historical release evidence and is superseded by later official releases.
Открыть доказательство ↗
Автоматическое доказательство
Deterministic provider acceptance PR #108
Состояние: merged
Что подтверждает: PR #108 exercised production Chat, STT and TTS HTTP clients against deterministic literal-loopback servers without external providers or public network calls. It proves a bounded protocol/client boundary, not subjective provider quality.
Открыть доказательство ↗
Автоматическое доказательство
Release and configuration-cache gate hardening PR #109
Состояние: merged
Что подтверждает: PR #109 repaired configuration-cache-safe refmap verification and scoped release requests to actual release changes. It changes build/release correctness only and does not change production runtime behavior.
Открыть доказательство ↗
Автоматическое доказательство
M11 Phase C shared orchestration deadline PR #110
Состояние: merged
Что подтверждает: PR #110 was merged after exact-head CI proved one monotonic STT → Chat retries → optional TTS deadline and exactly-once dialogue/relationship effects with production HTTP clients and loopback providers. Physical microphone, real Voice Chat playback and subjective provider quality remain separate installed/manual evidence categories.
Открыть доказательство ↗
Автоматическое доказательство
Official 0.2.0+1.21.1 release and exact candidate
Состояние: published
Что подтверждает: Release 0.2.0+1.21.1 is the accepted Memory 2.0 installed baseline at immutable release commit e426f588efefa6aa48a6e536c4a998421bbda241. The published/final candidate JAR is byte-identical to the installed candidate SHA-256 56293f86634b50b2def044429aac6f2cf0d197eb16ac1e60224708f7b3333aee. Installed clean-world required cases ended 7 PASS / 0 FAIL; VAI-M2-INST-005 remains NOT TESTED / automated evidence only and VAI-CONCUR-004 remains NOT TESTED / DEFERRED.
Открыть доказательство ↗
Ручная проверка
Installed 0.2.0 clean-world Memory 2.0 acceptance
Состояние: accepted
Что подтверждает: The byte-identical 0.2.0 candidate passed all seven required installed clean-world Memory 2.0 cases with 0 FAIL. The physical STT seed normalization silver-fox-482 → SilverFox482 is recorded as a non-blocking STT-quality observation rather than a persistence failure. VAI-M2-INST-005 and VAI-CONCUR-004 remain explicitly NOT TESTED.
Открыть доказательство ↗
Автоматическое доказательство
Controlled Semantic Memory BELIEF admission PR #123
Состояние: merged
Что подтверждает: PR #123 merged a provenance-safe BELIEF admission contract. PLAYER_TOLD/NPC_TOLD/INFERRED remain BELIEF paths tied to persisted source evidence; SYSTEM_OBSERVED cannot enter through the BELIEF API and FACT still requires server-owned SYSTEM_OBSERVED evidence. Candidate extraction is deliberately separate from admission and authority.
Открыть доказательство ↗
Автоматическое доказательство
PLAYER_TOLD BELIEF candidate extraction PR #125
Состояние: merged
Что подтверждает: PR #125 is merged bounded source evidence for PLAYER_TOLD BELIEF candidate extraction. Server-owned provenance and FACT authority remain unchanged. This source capability does not expand the installed 0.2.0 acceptance set or resolve deferred installed boundaries.
Открыть доказательство ↗
Автоматическое доказательство
Causal NPC↔NPC social mutation PR #153
Состояние: merged
Что подтверждает: PR #153 merged causal nearby NPC-to-NPC social influence with the full source acceptance suite green (620/620 tests and 146 gates). This is post-release source capability only; the accepted installed Memory 2.0 baseline remains 0.2.0+1.21.1 with 7 PASS / 0 FAIL and the documented NOT TESTED boundaries.
Открыть доказательство ↗
Автоматическое доказательство
Personality / social snapshot PR #155
Состояние: merged
Что подтверждает: PR #155 merged bounded read-only MCA personality/direct NPC-pair social snapshot source capability at merge a04e76dcf3ca6a07126e4e4b46f4d417a857a10f. Exact-head CI, Production Soak and Release dry-run passed while github-release publication was skipped. It is source evidence only; accepted installed Memory 2.0 baseline remains 0.2.0+1.21.1 at 7 PASS / 0 FAIL with VAI-M2-INST-005 and VAI-CONCUR-004 still explicit NOT TESTED boundaries.
Открыть доказательство ↗
Автоматическое доказательство
Personality/social dialogue integration PR #158
Состояние: merged
Что подтверждает: PR #158 merged personality/social dialogue integration at f6d8139cd1164653507ded8030b28c7c28e47cc2. Security #2456, CI #2821, Production Soak #490 and release dry-run #823 passed; release publication was skipped. This is source evidence only and not an installed-acceptance claim.
Открыть доказательство ↗
Автоматическое доказательство
0.3 dialogue integration state reconciliation PR #159
Состояние: merged
Что подтверждает: PR #159 reconciled the 0.3 dialogue integration source state at 889d7ed7303250878b6afb42385f3a02ab169084. Repository security, CI, Production Soak and release dry-run passed while publication was skipped. It made no new release/install claim.
Открыть доказательство ↗
Автоматическое доказательство
0.3 release convergence contract PR #160
Состояние: merged
Что подтверждает: PR #160 merged the 0.3 release convergence contract at 03ccb2d5d047ca551a5ac6be6b927de4404f09cf. Repository security #2498, CI #2862, Production Soak #509 and release dry-run #842 passed; github-release publication was skipped. This was not itself a release or installed-acceptance claim.
Открыть доказательство ↗
Автоматическое доказательство
Official 0.3.1+1.21.1 corrective release
Состояние: published
Что подтверждает: Official 0.3.1+1.21.1 was published from immutable release commit bc7c68ac2f3a4f761aa3b03a2f5c1fe1201745ab. The Fabric JAR SHA-256 is f7f40b920c6f72a0e9af864795f48a0f90479db42a145081f43923b71a95e29f. Automated release and post-release acceptance were green, but installed corrective VAI-PCM-MULTI-001 still required real server evidence.
Открыть доказательство ↗
Автоматическое доказательство
0.3.1 targeted Memory 2.0 recall correction PR #165
Состояние: merged
Что подтверждает: PR #165 restored bounded query-aware recall for retained older eligible Memory 2.0 dialogue while preserving NPC/player isolation and the existing 32-candidate and 6-entry prompt bounds. Automated CI, security, production soak, persistence recovery, GameTests, supported-loader builds and release dry-run passed. Installed VAI-PCM-MULTI-001 was explicitly left pending the official 0.3.1 JAR.
Открыть доказательство ↗
Автоматическое доказательство
0.3.1 installed corrective acceptance handoff PR #167
Состояние: merged
Что подтверждает: PR #167 records the exact 0.3.1 release identity and the remaining installed corrective canary procedure. It preserves the retained 0.3.0 world/history, uses exact text as the decisive retrieval oracle, keeps cross-NPC isolation and duplicate-persistence checks, and explicitly leaves VAI-M2-INST-005 and VAI-CONCUR-004 deferred. No installed PASS was claimed before real server evidence existed.
Открыть доказательство ↗
Ручная проверка
Installed 0.3.1 VAI-PCM-MULTI-001 corrective canary
Состояние: failed
Что подтверждает: The exact official 0.3.1 Fabric JAR with SHA-256 f7f40b920c6f72a0e9af864795f48a0f90479db42a145081f43923b71a95e29f was installed on the retained LinuxGSM world and VAI-PCM-MULTI-001 failed: Muammer retained owner-local amber-pine-314 but did not recall it after the required exact query. Nurey recalled violet-river-926; startup, persistence validity, event uniqueness and cross-NPC isolation passed. This is negative installed evidence, not installed acceptance.
Открыть доказательство ↗
Автоматическое доказательство
0.3.2 targeted recall ranking correction PR #169
Состояние: merged
Что подтверждает: PR #169 merged as 101c74d178ec29ca15f67ebd6041ef256a339f31 after the installed 0.3.1 trigger exposed final rank-to-6 starvation. The fix keeps exact NPC/player eligibility, the 32-candidate and 6-result bounds, provider call count, persistence schema and FACT/BELIEF authority unchanged while adding a narrow deterministic fallback for explicit marker recall. It does not claim installed acceptance.
Открыть доказательство ↗
Автоматическое доказательство
Official 0.3.2+1.21.1 corrective release
Состояние: published
Что подтверждает: Official 0.3.2+1.21.1 is published from release merge 3bb39e7ed126163efcdf971e85c89a4a5efd3111. The official Fabric asset villaigence-fabric-0.3.2+1.21.1.jar has SHA-256 b51cfcf3f46718fac9620586cf8b5aae53356c600d5ac375ca3280050befe015 and release run 31879227075 succeeded. Automated release evidence is not installed acceptance; VAI-PCM-MULTI-001 remains PENDING.
Открыть доказательство ↗
Автоматическое доказательство
0.3.2 installed corrective test plan PR #171
Состояние: merged
Что подтверждает: PR #171 merged as 9ff6e6bc56946db55f9dfd788bd049875a81466f and fixes the exact retained-world operator contract for the official 0.3.2 JAR: immutable artifact identity, backup and persistence hashes, Muammer/Nurey marker baseline, exact recall prompts, cross-NPC isolation and duplicate-event integrity. VAI-PCM-MULTI-001 remains PENDING; VAI-M2-INST-005 and VAI-CONCUR-004 remain NOT TESTED/deferred; 0.4 stays blocked until real installed PASS and repository reconciliation.
Открыть доказательство ↗