MaraudersMapMD v1.1.24–v1.1.27: Fact Check Skill, History Fixes & Repo Cleanup
Four releases shipped on February 18, 2026 — a busy day on the MaraudersMapMD codebase. Here's what landed across v1.1.24 through v1.1.27.
v1.1.27 — History Retention: The Math Was Wrong
The most impactful fix in this batch. The document history engine was silently miscalculating retention windows, which could cause valid snapshots to be pruned earlier than intended.
The root cause: retention time comparisons were mixing days with milliseconds. The fix moves everything to a consistent millisecond-based window throughout retentionEngine.ts, making expiry calculations precise and predictable.
Beyond the math fix, history.mode = interval now behaves correctly — snapshots are scheduled on inactivity rather than on a naive timer, and cleanup is properly registered and torn down. The History: Prune History Now command was also upgraded: it now enforces retention policies across all indexed history files (not just the current document), respects the global storage limit, and honors the history.snapshotCompression setting (gzip or none) across every snapshot type.
The History panel's Refresh action was rewired correctly, and checkpoints are now protected from being swept during pruning runs.
Files changed: historyCommands.ts, retentionEngine.ts,
snapshotStore.ts, historyActions.ts,
history.js, retentionEngine.test.ts
v1.1.26 — Rewrite Prompt: Installation Guard Restored
The MaraudersMapMD-skill Rewrite Prompt had lost its companion-file validation in a prior refactor. This release restores the full installation guard.
The skill now verifies that all required Python companion scripts are present (shards_db.py, shards_search.py, shards_to_json.py) before proceeding. Output versioning is also enforced: rewritten files are named <filename>.rewritten_vN.md, explicitly blocking chained names like rewritten.rewritten.md. The execution contract is clarified — the skill requires an explicit Use MaraudersMapMD skill invocation and follows a strict Step 1 → Step 2 workflow.
Files changed: aiService.ts (+/- 60 lines), package.json
v1.1.25 — Repository Cleanup
A housekeeping release. Internal development documents that had no business being in the public repository were removed:
docs/prd.mdanddocs/prd.rewritten.md(881 lines of internal product spec)PUBLISHING.md(internal marketplace guide)docs/brand/icon-source.png(build artifact)
.gitignore was updated to prevent similar files from being committed in the future. No functional changes.
v1.1.24 — Fact Check Skill + Skill Ecosystem Expansion
The headline feature of this batch. MaraudersMapMD now ships with three integrated AI skills:
| Skill | Purpose |
|---|---|
| Rewrite | 5-phase editorial readability rewrite |
| PPT | Markdown → presentation-quality .pptx/.pdf |
| Fact Check | Validates quantitative claims in your document |
The Fact Check skill (previously called "RC Check" — renamed for clarity) adds an AI: Copy Fact Check Prompt command and a toolbar button in the preview panel. Running it generates a prompt you can feed to any AI assistant to audit numbers, statistics, and factual assertions in your Markdown.
Each skill now ships with an explicit companion file manifest: the extension validates that all required files are present before allowing the skill to run, preventing silent failures from incomplete installations. A dedicated install script (install-factcheck-skill.sh) is included.
This release also cleaned up stale integration tests that were referencing a wrong extension ID, and removed a 2,080-line fixture file that was inflating test run times.
Files changed: aiService.ts (+95 lines), package.json (+18),
scripts/install-factcheck-skill.sh (new),
htmlTemplate.ts, usagePanel.ts, previewManager.ts
What This Adds Up To
MaraudersMapMD is converging on a stable, three-skill AI workflow:
- Write your document in Markdown with live preview
- Rewrite it for readability using the editorial skill
- Fact-check it before publishing
- Export it to PDF, HTML, or a presentation deck
The history system improvements in v1.1.27 make long-running document projects significantly more reliable — if you work on large specs, RFCs, or documentation that accumulates dozens of snapshots over time, this fix is worth the update.
Install or update from the Open VSX Marketplace.