Open Markdown Review 0.6.5

Open Markdown Review 0.6.5

• Bundle Windows x64, macOS ARM64 and Linux x64 Go companions in both VSIX packages. Review creation copies only selected launchers into the destination; no separate companion download or participant runtime installation is required.
• Add invited reviewer email lists, initiator-only later invitations, and per-reviewer Finish/Reopen progress. Email identity remains self-asserted.
• Guide finding processing through the creator workbench, published-fix evidence and reviewer verification, while preserving existing comments and source anchors.
• Export a review PDF with native comment annotations and reviewer progress, or a clean document-only PDF. Improve tables, images, Unicode text and document links.
• Keep reading controls beside Export PDF, without an extra document header. Add bounded continuous reading, precise document/heading/finding navigation, and prevent stacked navigation panels from covering discussions in narrow windows.
• Upgrade existing HTML and Go launchers with recoverable backups and exact-byte evidence-preservation checks.
• Keep public extension updates in VS Code's native Marketplace workflow. Update bundled Go and build/schema dependencies with security fixes.

The public release contains the portable and Windows x64 VSIX packages and their SHA-256 files only. Each VSIX includes all three Go companions. The project is licensed under MIT; M.I.R.D.A. is a philosophy, not an additional license.

Core protocol version: 0.6.0. Existing 0.5 and legacy 0.4 packages retain their original interpretation; no review history is silently converted. Real SMB shares remain untested. Managed-browser policies, executable signing/notarization and synchronized-folder qualification have limits. See the implementation and qualification status.

Validation

After the source snapshot was committed, the exact complete VSIX packages passed native Windows x64 and Linux x64 CI qualification and local macOS ARM64 qualification. Checks covered isolated VS Code installation, offline review creation with all three bundled companions, browser collaboration, PDF export, native Go integrity and source/binary vulnerability scans. Real SMB and managed-endpoint qualification remain separate.

Final source/artifact qualification record.

Open Markdown Review 0.5.6

Open Markdown Review 0.5.6

Focused WSL/remote-workspace reliability hotfix with known limitations; not approved for the professional pilot. The framework-neutral core wire version remains 0.5.0, so review packages remain compatible with 0.5.x clients that support their declared capabilities.

Corrected behavior

• A missing or invalid package remembered from an earlier session remains visible as unavailable without failing extension activation or being repeatedly restored as active.
• New creation chooses the next missing or empty .review[-N] folder instead of reusing a partial package. Package creation below .local-preview is refused, and generated preview Markdown is excluded from discovery.
• WSL, SSH, Dev Container and other remote extension hosts do not offer Delete Review because VS Code cannot guarantee a recoverable OS Trash/Recycle Bin there. Remove Review from List remains available and never changes shared files.
• Recovery failures identify the exact immutable path. Acknowledged evidence is still never reconstructed automatically.
• Extensionless PNG, JPEG, GIF, WebP and SVG images are recognized from their captured bytes. Unsupported-image errors identify the source Markdown and reference.

Extension-host artifact selection

The desktop OS and extension host can differ. The extension explicitly runs beside workspace files:

• Use open-markdown-review-0.5.6-win32-x64.vsix for a workspace opened by a local Windows x64 extension host.
• Use open-markdown-review-0.5.6-portable.vsix for WSL, SSH, Dev Containers and other supported hosts, including WSL sessions displayed by Windows VS Code.

Install the artifact in the Extensions section for the active host. Developer: Show Running Extensions identifies where the extension is executing.

Compatibility and limitations

• Existing complete 0.5 review packages are unchanged. No protocol event, manifest, revision, permission or storage-layout change is introduced.
• An incomplete package that has lost acknowledged files remains intentionally fail-closed. Preserve it for inspection and create a new package in a different empty durable folder.
• SMB remains untested, because an authorized CI-only SMB share is unavailable. No SMB compatibility or performance claim is made.
• Reviewer identities remain self-asserted and events unsigned. Role restrictions remain workflow rules rather than authenticated authorization.
• Professional-pilot qualification remains incomplete; see the checked-in implementation status and acceptance criteria.

Standard publication was explicitly authorized on 2026-09-25. This authorization does not grant professional-pilot approval or waive any listed limitation.

Open Markdown Review 0.5.5

Open Markdown Review 0.5.5

Regular release with known limitations; not approved for the professional pilot. This release adds explicit update controls and an ordered public-to-enterprise delivery contract. Review behavior, schemas and framework-neutral core wire version 0.5.0 are unchanged.

Update behavior

• Public mirdadusi.open-markdown-review installations use VS Code's native Visual Studio Marketplace update service. VS Code selects the correct target package, applies its rollout delay, respects per-extension and global update settings, and can be centrally governed by enterprise policy.
• Markdown Review: Check for Updates invokes VS Code's Marketplace update check. Open Update Source opens the trusted Marketplace item. The public extension does not independently download or install a public VSIX.
• The enterprise derivative uses the same update client with a separate, checked-in GitHub Enterprise source identity. It selects win32-x64 only on Windows x64 and portable elsewhere, validates the exact release/tag/repository/asset pair, bounds all responses, never forwards an authentication token to a redirect host, verifies the adjacent SHA-256 file, and only then asks VS Code to install the VSIX.
• Scheduled enterprise checks are optional, run at most daily after activation, use a bounded retry delay, and can be disabled through openMarkdownReview.updateChecks.enabled. Manual checks remain available.
• Enterprise publication is ordered after the public Marketplace publication. The enterprise release gate must observe the same version under mirdadusi.open-markdown-review before it can publish independently built advanta-czechia artifacts.

Installation and updates

Install the public package from the Visual Studio Marketplace:

code --install-extension mirdadusi.open-markdown-review

Enabled Marketplace extensions update automatically unless the user or administrator changes VS Code's extensions.autoCheckUpdates, extensions.autoUpdate, update delay, or per-extension Auto Update setting. Use the extension context menu or Command Palette to trigger an immediate check.

For manual or offline installation, use open-markdown-review-0.5.5-win32-x64.vsix on Windows x64 and open-markdown-review-0.5.5-portable.vsix on other supported VS Code platforms. Verify the adjacent SHA-256 file before installing through Extensions: Install from VSIX.

Compatibility and limitations

This release does not change events, manifests, revisions, browser clients, review permissions, storage layout, or the single-source-of-truth model. Review packages created by 0.5.3 through 0.5.5 therefore use the same declared protocol behavior.

• SMB remains untested, because an authorized CI-only SMB share is unavailable. No SMB compatibility or performance claim is made.
• Professional-pilot qualification remains incomplete. The authoritative open gates are recorded in implementation status and acceptance criteria.
• Reviewer identities remain self-asserted and events unsigned. Role restrictions are workflow rules rather than authenticated authorization.
• Marketplace availability, automatic updates, and rollout timing depend on VS Code settings, applicable enterprise policy, proxy/firewall access, and the Marketplace service.
• Enterprise self-update requires access to the configured GitHub Enterprise release and either a VS Code GitHub Enterprise session or compatible GitHub CLI authentication for a private repository.

See the security model, Marketplace publishing runbook, and support guide.

Open Markdown Review 0.5.4

Open Markdown Review 0.5.4

Regular release with known limitations; not approved for the professional pilot. This release prepares the existing 0.5.3 implementation for a clear public Visual Studio Marketplace presentation. Review behavior and core wire version 0.5.0 are unchanged.

Marketplace presentation

• Adds an original 256-pixel Marketplace icon and light-theme screenshots of review setup, the VS Code review toolbox, and the portable browser participant experience.
• Reworks the README opening so an evaluator can understand the local-first model, installation choices, supported content, single source of truth, and current qualification status before entering the detailed documentation.
• Adds focused Marketplace metadata, search keywords, free-pricing declaration, public support guidance, and a private vulnerability-reporting path.
• Adds a deterministic presentation check for required files, screenshot references, icon size, public metadata, version consistency, and accidental internal repository markers.
• Adds repeatable Marketplace packaging for a portable VSIX and a Windows x64 VSIX. Each package receives a SHA-256 checksum; the Marketplace build allows vsce to rewrite repository-relative documentation links for the hosted listing.
• Documents a manual first-publication process using a short-lived, least-privilege Azure DevOps personal access token. No CI workflow or long-lived repository secret is introduced.

Installation

After Marketplace publication, open Extensions in VS Code and search for Open Markdown Review, or run:

code --install-extension mirdadusi.open-markdown-review

For manual or offline installation, use open-markdown-review-0.5.4-win32-x64.vsix on Windows x64 and open-markdown-review-0.5.4-portable.vsix on other supported VS Code platforms. Verify the adjacent SHA-256 file before installing through Extensions: Install from VSIX.

Browser-only participants receive the complete review folder and open its review-named HTML launcher; they do not install a Marketplace extension.

Compatibility and limitations

This release does not change schemas, event types, revision format, browser behavior, VS Code commands, or protocol capabilities. Packages created by 0.5.3 and 0.5.4 therefore use the same declared protocol behavior. Existing 0.4 packages retain the legacy reader and are not silently migrated.

• SMB remains untested, because an authorized CI-only SMB share is unavailable. No SMB compatibility or performance claim is made.
• Professional-pilot qualification remains incomplete. The authoritative open gates are recorded in implementation status and acceptance criteria.
• Reviewer identities remain self-asserted and events unsigned. Role restrictions are consistent workflow rules, not authenticated authorization.
• Browser access depends on Chrome/Edge File System Access support, user permission, and applicable enterprise policy. A local HTML file cannot silently inherit Windows identity or access neighboring folders.

See the complete behavior introduced in 0.5.3, the security model, and the support guide.

Open Markdown Review 0.5.3

Open Markdown Review 0.5.3

Regular release with known limitations; not approved for the professional pilot. This rebuilt patch completes the review workflow, portable-package publication and browser cold-open work accumulated for 0.5.3. Core wire version remains 0.5.0.

Added and fixed

• Comment and Suggest actions remain reachable after deep scrolling. Comment and suggested-edit cards link to their exact source positions, and clicking either document marker returns to its finding card.
• New reviews use initiator-managed finding control. Reviewers may reply while a thread is open; only the immutable manifest initiator may decide, close, or reopen it. A closed finding exposes only Reopen to the initiator and no write actions to other reviewers until reopening.
• The toolbox always displays the participant's current stance. Approve and Reject are available without an active stance; after either decision, only Withdraw is available; withdrawing restores Approve and Reject.
• The findings side panel defaults to comments and suggested edits from every Markdown document. It can be narrowed to the selected document, keeps document locations and navigation, receives off-document peer findings through live synchronization, persists its VS Code view preference, explains empty scopes, and remains reachable in narrow editor columns.
• PDF export is a self-contained offline review archive. It includes a deterministic challenge register, every frozen document with a per-document challenge map, a dedicated comments/responses/findings section with complete replies and lifecycle history, participant stance history, rendered Mermaid/images/tables, external-reference disclosures, internal links, and the exact audit appendix/inventory. The PDF is derived evidence; .review/ remains the sole source of truth.
• New packages can declare the optional sanitized-html-v1 capability and commonmark-gfm+sanitized-html-v1 renderer profile. VS Code, the portable browser and PDF export then share a fail-closed structural HTML subset for headings, paragraphs, emphasis, lists, links, images, code, quotes and tables. Scripts, styles, embedded frames, event handlers and unsafe URL schemes remain inert.
• Raw HTML images and explicit attachment references are captured as content-addressed package resources; external links are inventoried for audit. Text, images, tables and cells retain source anchors so findings navigate consistently between rendered content and discussions. Packages that do not declare the capability continue to show raw HTML as inert text.
• New reviews generate a review-named Review-<name>.html launcher bound only to the expected review ID, title and exact manifest digest. The browser rejects a different selected folder and reconnects automatically only while its previously granted directory permission remains available.
• VS Code can publish a verified complete package copy to an empty local, synchronized, shared-drive or Git folder. It rejects links and unexpected content, hashes and re-reads every file, validates the destination, checks the source again and then switches the active connection without deleting the original package.
• A separate private Link Local Source Workspace workflow reports exact, changed and missing reviewed documents without placing native source paths in shared evidence. Multi-root creation explicitly selects one Markdown source root; extra roots remain resource-only.
• Explicit DOCX, legacy/current Visio and EMF attachments can be carried as bounded content-addressed originals behind their review rendering without executing them.
• Cold open now reports manifest, event and rendering progress immediately. Ordinary Markdown reviews admit verified descriptors first and load only the selected document and visible resources; approval and audit/export paths still perform a fresh whole-revision verification. On the 49-document/300-resource reference package this reduced local admission from 205 reads/16.8 MB to 4 reads/216 KB before the first document.
• Regression coverage includes deterministic archive finding references, simultaneous and cross-document participants, review-wide filtering/navigation, incremental updates, scope restoration, responsive widths, initiator-only lifecycle controls, stance transitions, and complete PDF export independent of UI filters.

Installation and compatibility

• Windows x64: open-markdown-review-0.5.3-win32-x64.vsix.
• Other supported VS Code platforms: open-markdown-review-0.5.3-portable.vsix.

Both packages include SHA-256 checksum files and standard VSIX metadata without a pre-release marker. Install through Extensions: Install from VSIX, then reload VS Code. Existing generated HTML clients are executable artifacts and are not replaced automatically; use Markdown Review: Update Portable Browser Client with its explicit backup and confirmation to migrate a legacy generic filename or obtain the new browser UX.

Existing 0.4 packages retain the legacy reader. Existing 0.5 packages remain readable under their declared capabilities; creator-controlled lifecycle semantics apply only when the package declares that capability. Existing review evidence is not rewritten or migrated.

Validation and limitations

Before release preparation, the changes passed 112 unit/protocol tests, six real Chromium scenarios, PDF content/internal-link inspection, sanitized-HTML rendering/export checks, the complete 49-document/300-resource reference-package audit, and isolated VS Code extension-host checks on macOS. The tag-driven release workflow independently repeats Linux/portable and Windows validation, browser and extension-host tests, dependency audits, packaging, and checksums before publication.

• SMB remains untested, because an authorized CI-only SMB share is unavailable. No SMB compatibility or performance claim is made.
• Professional-pilot qualification remains incomplete. Interruptible Mermaid rendering, remaining participant cancellation and platform source-save durability, containment-race and optional-extension conformance, local Windows browser folder permissions, native Windows relocation/fault injection, shared-drive reference-workload performance, and independent user-task acceptance remain open.
• Reviewer identities remain self-asserted and unsigned. Creator-only controls are consistent workflow rules, not authenticated access control. Audit hashes do not authenticate participants or prove that disconnected clients have synchronized.
• Browser folder access remains subject to Chrome/Edge permission behavior and enterprise policy. A file-based HTML client cannot silently inherit Windows identity or access neighboring files without a browser grant.

Open Markdown Review 0.5.2

Open Markdown Review 0.5.2

Regular release with known limitations; not approved for the professional pilot. This patch adds review-removal actions and improves reviewer identity and navigation in VS Code. Core wire version remains 0.5.0; there is no package migration or second source of review content.

Added and fixed

• Update Sharp and its native/WASM packages to 0.35.4, and the affected js-yaml 4 dependency to 4.3.2, addressing the Sharp/libheif advisory and js-yaml merge-budget advisory. Dependency audit gates remain enabled.

• Remove Review from List disconnects a current or legacy review locally without deleting shared files. Explicit reconnection works even after a restart; automatic legacy discovery does not bring a removed review back.

• Delete Review… confirms the exact folder and inventory before moving the entire dedicated package to OS Trash/Recycle Bin. It protects source/workspace roots, rejects links/junctions and unexpected top-level files, checks for changes during confirmation, and coordinates local operations. There is no permanent-delete fallback.

• Removal closes all of that review's toolbox tabs and clears its active selection and authoring-resume shortcuts, while preserving other reviews and private recovery journals. Late writes from closed toolboxes are rejected.

• Creation passes both Reviewer ID and Display Name into the VS Code toolbox. Later edits are remembered privately per review, including across reopening; a received review never borrows its creator's identity.

• One Reviews list replaces the duplicate “Reviews” and “Review Packages (0.5)” interfaces. Creation, opening and tab focus update Active Review and the status bar. Closing a toolbox retains the selection; sidebar commands reopen it and wait until the toolbox is ready.

• Windows drive/directory casing aliases are treated as one local connection for registration, active selection, removal and reconnection; display and private journal paths retain their original spelling.

• Regression tests cover deletion cancellation/failure, changed and unsafe folders, active-review cleanup, duplicate tabs, reconnection, identity handover and the first comment's author. Slidev navigation assertions wait for the selected slide's evidence.

Installation and compatibility

• Windows x64: open-markdown-review-0.5.2-win32-x64.vsix.
• Other supported VS Code platforms: open-markdown-review-0.5.2-portable.vsix.

Both packages include SHA-256 checksum files and standard VSIX metadata without a pre-release marker. Use Extensions: Install from VSIX, then reload the VS Code window. This release does not automatically replace executable HTML in existing shared reviews; Markdown Review: Update Portable Browser Client remains explicit and backed up. VS Code uses its installed trusted toolbox. Browser participants continue opening OpenMarkdownReview.html and granting folder access.

Existing 0.4 packages retain the legacy reader. Markdown, Mermaid, tables, images, attachments and optional Slidev static review remain available. Replies, decisions, suggested edits and audit exports keep their existing wire semantics. Whole-package filesystem deletion does not invent a review.deleted event or edit individual historical events. Previous tags, binaries and checksums are unchanged.

Validation and limitations

The changes passed 106 unit/protocol tests, four real-browser scenarios and isolated VS Code extension-host checks on macOS before publication. The release workflow independently gates publication on Linux/portable and Windows validation, browser and extension-host tests, dependency audits, packaging and checksums for the tagged source.

• SMB testing is skipped and remains untested, as requested because an authorized CI-only share is unavailable. No shared-drive compatibility claim is made.
• Trash transport itself is not qualified by simulated-trash tests. If a drive/provider cannot use Trash/Recycle Bin, deletion fails without a permanent fallback. Inspect the folder after a storage error. Stop other VS Code, browser and CLI writers before deleting a shared review: deletion may synchronize to other participants, and local checks do not lock other machines or eliminate filesystem races.
• Removal closes tabs and discards unsaved drafts only after confirmation. Recover a successfully trashed package using the OS, then reconnect it. If the review is itself the open workspace, open the parent/source workspace before deleting. Git changes are never committed or pushed automatically.
• Professional-pilot qualification remains incomplete. Mermaid interruption, participant cancellation/filesystem safety, local Windows browser permissions, reference-workload performance and independent usability gates remain open. A regular release label does not override release-qualification.json.
• Reviewer identities remain self-asserted and unsigned. Audit hashes do not authenticate reviewers or establish that disconnected participants have synchronized. Slidev static-review restrictions and the isolated author-test-runtime advisory exceptions documented in 0.5.1 still apply.

Open Markdown Review 0.5.1

Open Markdown Review 0.5.1

Regular release with known limitations; not approved for the professional pilot. This release adds optional Slidev static review through three separate layers: framework-neutral core protocol, versioned presentation profile, and a shared client adapter. Core wire version remains 0.5.0.

Added

• A concrete Slidev profile specification, JSON schema and immutable schema/descriptor/resource bindings. Older or unsupported clients fail closed instead of silently treating a presentation as ordinary Markdown.
• Shared VS Code/CLI authoring with explicit project trust, pinned Slidev 52.19.1, automatic local src: imports/ranges, repeated-import identities, and include/exclude speaker-note policy.
• Frozen themed slide images, slide navigation, selectable exact source text, whole-slide visual comments and source wording comments in the same VS Code/HTML toolbox. Replies, decisions, resolutions, suggestions and review approval/rejection reuse core events.
• Audit PDFs containing all slide images, included notes, frozen source, discussion, replies and decisions, with profile/schema/image hashes in the exact inventory. Opening or reviewing a package does not execute Slidev or contact a review server.
• Parser/schema/security regression tests and a real Slidev-to-browser-to-PDF fixture, included in Linux and Windows CI. CRLF source selection, repeated visual targets, note redaction and no participant network requests are checked.

Installation

• Windows x64: open-markdown-review-0.5.1-win32-x64.vsix.
• Other supported VS Code platforms: open-markdown-review-0.5.1-portable.vsix.

Both assets have SHA-256 checksum files and use standard VSIX metadata, without a pre-release marker. Install through Extensions: Install from VSIX. Browser participants receive the review folder with OpenMarkdownReview.html; they install no Slidev runtime. Existing HTML entry files are executable clients and require an explicitly approved, backed-up update to obtain the new adapter.

Only Slidev authors install the matching project-local renderer/theme/Playwright runtime. See the creation guide. The trusted author-side build may briefly start Slidev's local build server; participant review remains file-based/serverless.

Known limitations

• Professional-pilot qualification remains incomplete. The existing Mermaid interruption, cancellation/filesystem safety, Windows native browser permission, performance and independent usability gates remain open. A regular release label does not override release-qualification.json.
• SMB testing is skipped and remains untested, as previously requested because an authorized CI-only share is unavailable. Shared-drive behavior is not certified; no SMB functionality was removed.
• Slidev v1 reviews static exports, not interactive components, animation timing, video or separate click states. It does not provide rectangular pixel anchors, pixel-to-word mapping or a reproducible build/dependency archive. Custom preparsers/addons and disabled/hidden slides are rejected.
• Authors must inspect captured pages before sharing. Frozen source/assets and rendered views are independently hashed, not a proof of honest rendering or byte-identical remote dependency use. Notes exclusion removes trailing speaker-note comments, not every possible secret or component-rendered text. Redacted source cannot be automatically patched back to a nonmatching original file.
• The isolated authoring test/example runtime includes two recorded, unpatched upstream image-size advisories in the unused PPTX export path. It is not shipped in the client. The application audit remains unmodified; the fixture accepts only the specifically documented advisories and must not be used for PPTX exports.
• Reviewer identities remain self-asserted. Audit hashes do not authenticate reviewers, sign approvals or establish that disconnected participants have synchronized.

The 0.5.0 tag, binaries and checksums are unchanged.

Open Markdown Review 0.5.0

Open Markdown Review 0.5.0

Note: This is a regular GitHub release with known limitations. SMB testing was skipped because a CI-only share is unavailable. The release is not approved for the professional pilot or production sign-off; publication does not close the outstanding qualification gates listed below.

Included

• One local-first review package and shared reviewer toolbox in VS Code and a generated, double-clicked HTML file. No application server or browser extension.
• Parameter-driven CLI and graphical VS Code creation, multiple reviews, custom storage folders and immutable revisions.
• Markdown, Mermaid diagrams, images, tables/cells and captured external attachments.
• Anchored comments and replies, linked highlights, accept/reject decisions, resolve/reopen, strikeout/replacement suggestions and explicit source application.
• Revision approval/rejection/withdrawal, concurrent event publication, bounded caching and eventual synchronization.
• Audited whole-revision PDF export including comments, replies, decisions and exact-byte evidence; resumable publication and export retry.
• Protocol 0.5 schemas and shared implementation; existing 0.4 packages retain their legacy VS Code reader without silent migration.
• MIT licensing for project code and a separate non-binding M.I.R.D.A. philosophy, with bundled third-party notices.

Install

Download the appropriate VSIX and its matching SHA-256 checksum:

• Windows x64: open-markdown-review-0.5.0-win32-x64.vsix.
• Other supported VS Code platforms: open-markdown-review-0.5.0-portable.vsix.

In VS Code choose Extensions: Install from VSIX, select the downloaded file, and reload if prompted.

The GitHub pre-release label was removed at the user's request. The attached VSIX files are the original CI-tested builds and retain their internal pre-release packaging marker. The source tag, binaries and SHA-256 checksums were not replaced; their embedded documentation records the original build status.

Authors create a review from the Review Activity Bar or the CLI. Browser participants receive the complete review folder, double-click OpenMarkdownReview.html, explicitly grant access to the adjacent folder, and enter their reviewer identity. Browser access is not inherited Windows authentication. VS Code opens that same entry file with its installed trusted client.

Validation and limitations

The exact release commit passed Linux/portable and Windows CI and the tagged release workflow, including 84 core/protocol/release-policy tests, browser and VS Code integration checks, dependency audits and target packaging.

• SMB remains untested. CI-only share provisioning is unavailable and testing is excluded by user decision. No SMB compatibility, ACL, interruption-recovery or latency qualification is claimed.
• Actual local Windows browser folder grants, restart/revocation and enterprise permission-policy scenarios remain unqualified. The native-picker fixture depends on excluded SMB setup. Origin-private storage/IndexedDB and native-bridge tests do not replace native permission evidence.
• Mermaid lacks the specified hard interruptible rendering deadline. Full participant cancellation and CLI error-class parity remain incomplete.
• Adversarial native path replacement, external-editor races, platform ACL/replacement and power-loss durability are not fully qualified. Keep source control and backups.
• Optional presentation-extension conformance, complete accessibility/selection coverage, reference-workload latency/memory and independent user-task acceptance remain outstanding.
• Reviewer identities are self-asserted; events are unsigned. Audit hashes identify observed exact bytes, not authenticated people or globally complete synchronization.

Use non-critical evaluation material and retain backups. Read the full implementation status, qualification record, and README before starting.

Open Markdown Review 0.4.6

Full Changelog: v0.4.5...v0.4.6

Open Markdown Review 0.4.5

Full Changelog: v0.4.4...v0.4.5