Skip to content

v11.4.1 — Phase 1.5: hologram-mode verification + honest closure

Choose a tag to compare

@Ruso-0 Ruso-0 released this 19 May 23:28
· 10 commits to master since this release

Summary

Closes the test-coverage gap from v11.4.0 honestly. No runtime change — v11.4.1 strictly adds tests and documentation on top of v11.4.0.

Why

A post-v11.4.0 self-audit (docs/v11.4.0-self-exploration.md) flagged two real problems:

  1. Phase 1 tests ran only in project mode. The MCP server's default is hologram (detectMode(cwd) in src/index.ts:308). The per-transaction captureBaseline(filesToEvaluate, mode) scoping in hologram could in principle leak pre-existing errors that the project-mode suite would not catch.
  2. The "TS1259-style" test in v11.4.0 empirically dispatched TS1192, not TS1259. A TS-compiler probe showed TS1259 specifically requires esModuleInterop:true + allowSyntheticDefaultImports:false + export = source — none of which my original test used. The CHANGELOG line claiming "exact scenario coverage" was technically misleading.

This release fixes the test gap and corrects the wording.

What's in v11.4.1

Added

  • tests/kernel-pre-existing-errors-hologram.test.ts — 4 hologram-mode tests:

    • Pre-existing TS1259 + unrelated-symbol edit → safe=true.
    • Pre-existing TS2802 (target:ES5 + downlevelIteration:false + Set iteration) + unrelated-symbol edit → safe=true.
    • JIT-specific: target file enters rootNames only at edit time → still filters correctly.
    • Counter-test: new TS2322 on top of pre-existing TS1259 → safe=false, structured error contains TS2322 (not TS1259).
  • docs/hologram-mode-verify.md — empirical PASS report for the hologram-mode round.

  • docs/v11.4.0-self-exploration.md — honest 10-finding self-audit that drove Phase 1.5. Includes the items I'm still uncomfortable with (code duplication, mocked deps, self-Furia not independent, etc.) for the next iteration.

Verified empirically (no kernel change)

The differential filter at src/kernel/backends/ts-compiler-wrapper.ts:611 holds in hologram mode for TS1259 and TS2802 specifically. The user's original bug report most likely ran against the globally installed @ruso-0/nreki@10.19.0; the fix had shipped in an earlier release.

Tests

1 427 passed / 3 skipped / 0 failed (+4 vs v11.4.0).

Migration

No API change, no file format change, no behavioral change vs v11.4.0. Users on v11.4.0 do not need to upgrade unless they want the new test coverage in their fork or want to read the audit docs.

The v11.4.0 tag at commit 984c781 is preserved unchanged.

🤖 Generated with Claude Code