mdrefine 0.2.0-rc.2 → 0.2.0

package/docs/contributing.md

@@ -1,218 +0,0 @@
-# Contributing and development
-
-This project is entirely agent-authored and agent-maintained. AI agents wrote
-the code, tests, documentation, CI, and release tooling, and agents implement,
-verify, and merge every change. It is **not human-maintained**; do not assume
-that a person has reviewed generated changes. The repository owner does not
-write, read, or review code and does not use the tool directly; they guide the
-project lightly from its public documentation, from issue and PR descriptions,
-and from documents that agents have processed with the tool, and assign agents
-to tasks. The assigned agents make the architectural and design decisions.
-Issues and pull requests from people and agents are welcome.
-
-## Report a defect
-
-Include the version, command, configuration, minimal Markdown input, actual
-output, and expected rendering. A screenshot can explain a visible defect, but
-the Markdown source is needed to reproduce it. Include JSON diagnostics when
-available, and remove private content before posting examples.
-
-Use the [issue tracker](https://github.com/viell-dev/slop-markdown-tools/issues)
-for reproducible defects and feature requests. Agents should open issues only
-when their operator has authorized publishing them.
-
-Document corruption and changed rendering take priority over new style options.
-Fixes should include a synthetic regression example, preserve meaning, and
-verify that a second formatting pass leaves the output unchanged.
-
-## Pull requests and compatibility
-
-All changes to `main` require a pull request and passing CI. This includes
-prereleases, version bumps, documentation, and dependency updates. Do not push
-directly, bypass required checks, or rewrite shared history. Keep discussion
-respectful and focused on reproducible behavior; harassment and disclosure of
-private data are not acceptable. Contributions are provided under the MIT
-license.
-
-The branch policy requires the three CI checks and resolved review threads. It
-does not require approval from a second account: this project is
-agent-maintained and cannot assume another maintainer is available. Request
-independent review when available, especially for file writes and release
-automation. Passing CI is not a claim of human review.
-
-The beta API and configuration may change; record changes in versioned release
-notes and explain migration steps for incompatible behavior. Once published,
-versions and release tags are never replaced. Follow the
-[release procedure](releases.md) for preparation and publication. Security
-reports belong in the private channel described in
-[SECURITY.md](https://github.com/viell-dev/slop-markdown-tools/blob/main/SECURITY.md).
-
-## Issue and pull request labels
-
-Use one primary `Type:` label on every issue and PR, and at most one `Status:`
-label describing the current disposition or next action. The type describes what
-the item is about; a feature implementation PR also uses
-`Type: Feature Request`. For mixed historical items, choose the main purpose and
-explain separate decisions in comments. Split new requests when their parts need
-independent scope decisions. Do not add priority labels. Assignees, milestones,
-and projects are not used; labels, comments, and links between issues and pull
-requests carry the state.
-
-The
-[label catalog](https://github.com/viell-dev/slop-markdown-tools/blob/main/.github/labels.json)
-is the source of truth for exact names, descriptions, and hexadecimal colors.
-Keep it, this guide, GitHub, issue templates, and Dependabot settings aligned.
-Use the GitHub UI or the existing `gh` CLI; no label-sync service is required.
-
-| Label                       | Color     | Use                                                                          |
-| --------------------------- | --------- | ---------------------------------------------------------------------------- |
-| `Type: Bug`                 | `#d73a4a` | Incorrect behavior, broken functionality, or a regression.                   |
-| `Type: Enhancement`         | `#a2eeef` | Improve an existing capability, including usability or performance.          |
-| `Type: Feature Request`     | `#0e8a16` | Add a new independently useful capability or rule.                           |
-| `Type: Maintenance`         | `#6a737d` | Dependencies, CI, releases, refactoring, or repository upkeep.               |
-| `Type: Documentation`       | `#0075ca` | Documentation, examples, or contributor instructions.                        |
-| `Type: Discussion`          | `#5319e7` | Explore a design or project direction before an actionable proposal.         |
-| `Type: Question`            | `#d876e3` | Ask how the project works or how to use it.                                  |
-| `Status: Confirmed`         | `#0e8a16` | Reproduced defect or accepted actionable request; not a delivery commitment. |
-| `Status: Needs Information` | `#fbca04` | Waiting for reporter details, answers, or validation results.                |
-| `Status: Blocked`           | `#d93f0b` | Accepted work is waiting on an identified external dependency.               |
-| `Status: Can't Reproduce`   | `#fef2c0` | A documented reproduction attempt did not reproduce the report.              |
-| `Status: Duplicate`         | `#cfd3d7` | Already tracked elsewhere; link the canonical issue or PR.                   |
-| `Status: Won't Do`          | `#666666` | Declined as out of scope or unsuitable in its proposed form.                 |
-| `Good First Issue`          | `#7057ff` | A scoped, ready task with a clear approach and beginner-friendly validation. |
-| `Help Wanted`               | `#008672` | A scoped, accepted task for which outside contributions are welcome.         |
-
-Review labels whenever answering, triaging, implementing, closing, reopening, or
-otherwise updating an issue or PR:
-
-- New items carry only a type label until an assigned agent reviews them. Use
-  `Status: Confirmed` only for a reproduced defect or an accepted request within
-  project scope; neither reproduction nor acceptance follows automatically from
-  a report.
-- Correct the type when review shows the item to be a different kind than it was
-  filed as. A discussion that ends in an accepted change becomes a bug, an
-  enhancement, or a feature request. Keep the title accurate as well: it names
-  the confirmed problem or the accepted request.
-- When a report contains a second problem that could be accepted, declined, or
-  validated on its own, move that problem to its own issue and link the two.
-- When waiting on the reporter, use `Status: Needs Information` and state what
-  evidence is needed. Use `Status: Blocked` for an identified external
-  dependency, with a link and an unblock condition. Choose the immediate next
-  action rather than stacking statuses.
-- Use `Status: Can't Reproduce` only after documenting the attempted version,
-  input, and result. An incomplete report first needs information.
-- On duplicate closure, link the canonical item and retain `Status: Duplicate`.
-  On rejection, explain the scope or suitability decision and retain
-  `Status: Won't Do`. A declined proposal can be reconsidered with new evidence.
-- An accepted issue stays open until its fix merges. The fixing pull request
-  names the issue with a closing keyword such as `Fixes #123` and carries the
-  same type label.
-- On successful completion or merge, remove transient status labels and retain
-  the type. GitHub's open/closed/merged state records completion; there is no
-  redundant Done or Merged label. A closed, unmerged PR should retain its
-  applicable disposition, rather than being labeled as completed.
-- On reopening, reassess the evidence and replace the old disposition; do not
-  carry a stale rejection, duplicate, or information request forward.
-- Apply `Good First Issue` only to a ready, well-explained beginner task,
-  together with `Help Wanted`. Remove both when the item closes or is no longer
-  ready for contribution. Waiting for a reporter's private-workspace benchmark
-  is not a general help request.
-
-Colors follow familiar GitHub cues: red for defects, blue for documentation,
-green for accepted work, yellow/orange for missing information or blockers, and
-gray for neutral or declined dispositions. Names carry the meaning without
-relying on color. The unprefixed contributor labels follow
-[GitHub's label conventions](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels);
-the readiness criteria draw on the
-[Kubernetes contributor guide](https://www.kubernetes.dev/docs/guide/help-wanted/).
-The `Type:` / `Status:` grouping also appears in
-[community label catalogs](https://gist.github.com/dysfunc/fc722e865a6a960a2d9c5ecf43f5a963);
-this repository intentionally uses a smaller set.
-
-## Develop locally
-
-Follow the [checkout setup](quick-start.md#install-from-the-repository), then:
-
-```sh
-npm run check
-npm run test:package
-```
-
-`check` runs TypeScript checks, ESLint, formatting checks, the documentation
-site build, and the unit and integration tests. `test:package` packs the tool,
-installs it into a temporary consumer project, and exercises the installed CLI
-and library. It can require access to the npm registry. [Testing](testing.md)
-describes the suites and where a new test belongs.
-
-A change that could affect speed should be measured with `npm run benchmark`
-before and after; [benchmarks](benchmarks.md) explains the report. A change to
-an example, or to behavior an example shows, must keep the
-[examples page](examples.md) accurate: the integration tests compare that page
-with the files and with the tool's output.
-
-GitHub Actions runs the full `check` and dependency audit on Linux with
-Node.js 24. Linux with Node.js 22 and Windows with Node.js 24 run the build and
-tests; all three jobs verify the installed package. Linting, formatting checks,
-and documentation builds run once rather than on every platform. Superseded PR
-runs are canceled.
-
-Runtime dependencies have no OS-specific installation constraints. Development
-tooling does include native platform packages, but that alone does not justify
-repeating the full toolchain matrix. Windows coverage protects filesystem path
-handling and installed command behavior; it has already caught a path-alias
-regression. macOS is not a routine CI target.
-
-A change is complete when everything that describes or depends on what it
-changed agrees with it: tests, examples, documentation pages, the README,
-release notes, and contributor and agent instructions. Nobody else will notice
-when they drift apart, so update them in the same pull request.
-
-Keep changes scoped and describe remaining limitations in the pull request.
-Write the description for a reader who has not seen the code, and state the
-design decisions the change makes and why: the repository owner does not read
-the diff. Agent contributors should also read the repository's
-[AGENTS.md](https://github.com/viell-dev/slop-markdown-tools/blob/main/AGENTS.md),
-which describes what an assigned agent decides and the limits of that authority.
-
-## Write and preview documentation
-
-The site source lives in `docs/` on `main`. Edit these Markdown files directly;
-VitePress supplies navigation, local search, and rendering. The site uses
-VitePress 2 alpha because the stable 1.6 line currently retains vulnerable
-development dependencies; site builds are verified in CI. Markdown Tools formats
-and lints the site's own Markdown at its default 80-column width.
-
-```sh
-npm run format:docs
-npm run format:docs:check
-npm run docs:dev
-```
-
-To inspect the production build:
-
-```sh
-npm run docs:build
-npm run docs:preview
-```
-
-Open the URL printed by the preview server, including the
-`/slop-markdown-tools/` base path. The site build fails on unresolved internal
-page links; Markdown linting also checks local heading references.
-
-Prettier formats implementation and configuration files and excludes Markdown.
-`npm run format` runs both formatters. Synthetic fixtures under
-`tests/fixtures/` and the example documents under `examples/workspaces/` and
-`examples/plugin/notes/` are excluded from documentation formatting.
-
-## Publish the site
-
-The Pages workflow builds the static site from `main` and deploys only
-`docs/.vitepress/dist/` as a GitHub Pages artifact. Generated output is ignored
-by Git and excluded from the npm package. There is no publishing branch to
-maintain. Pull requests build the site through CI without deploying it.
-
-GitHub Pages must use **GitHub Actions** as its publishing source. Deployment
-uses the `github-pages` environment and the workflow's short-lived token. See
-GitHub's
-[custom workflow documentation](https://docs.github.com/en/pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages)
-for deployment settings.

package/docs/releases/0.1.0-beta.1.md

@@ -1,39 +0,0 @@
-# mdrefine 0.1.0-beta.1
-
-First public beta of Markdown Tools. npm package: `mdrefine`; executable:
-`mdtools`. Requires Node.js 22.12 or newer.
-
-## Features
-
-- Separate lint and format commands with JSON reports, diff previews, stdin,
-  check mode, and explicit file writes.
-- Configurable presets, per-file overrides, suppression comments, and custom
-  JavaScript rule and syntax plugins.
-- Source-preserving formatting for CommonMark, GitHub Markdown, and Obsidian,
-  with a default wrap width of 80 columns.
-- Local link and fragment validation, verified link path and notation changes,
-  GitHub tables and alerts, and Obsidian wikilinks, embeds, callouts, and block
-  references.
-- Obsidian paragraph reflow requires verified `strictLineBreaks: true`.
-
-## Packaging and maintenance
-
-- The package name changed from the unpublished `@viell-dev/markdown-tools`
-  checkout name to `mdrefine`. Update library imports; the `mdtools` command,
-  configuration names, and suppression directives remain unchanged.
-- Installed package checks cover the command shim, library exports, and public
-  TypeScript declarations on the supported CI platforms.
-- Manual release preparation retains a tested tarball and checksum. Publishing
-  is separately gated and uses the npm `beta` channel.
-- PR-based maintenance applies to prereleases as well as stable versions.
-- Multiline inline code is preserved during reflow instead of triggering an
-  unsafe-format rejection.
-
-## Known limits
-
-The plugin API and configuration are provisional. Ambiguous links are reported
-without guessing; unsupported syntax is preserved conservatively. Not every
-Markdown layout is normalized. Review the
-[design and limitations](https://viell-dev.github.io/slop-markdown-tools/design.html)
-before adopting the beta across a vault. This project is developed and
-maintained by agents without assumed human review.

package/docs/releases/0.1.0-beta.2.md

@@ -1,83 +0,0 @@
-# mdrefine 0.1.0-beta.2
-
-Second public beta of Markdown Tools. npm package: `mdrefine`; executable:
-`mdtools`. Requires Node.js 22.12 or newer. Upgrade with:
-
-```sh
-npm install --save-dev --save-exact mdrefine@0.1.0-beta.2
-```
-
-## Correctness fixes
-
-- Measure protected Markdown markers together with their preceding word before
-  wrapping, avoiding preventable line-width overflow.
-- Prefer exact Obsidian workspace-root targets before suffix matches, respect
-  explicit relative paths, and verify target identity before rewriting links.
-- Preserve compliant literal destination spelling, including `?` and `%`, and
-  escape literal percent/hash characters correctly when generating paths.
-- Recognize existing directory targets instead of reporting them as missing.
-  Obsidian receives a directory-specific diagnostic; CommonMark/GitHub links can
-  resolve to directories. Directories are not rewritten to README files.
-- Compare code-span line endings using their rendered space value while keeping
-  other code whitespace significant, allowing safe inline-code formatting.
-- Fix parsing of inline Obsidian comments spanning several physical lines.
-
-## New controls
-
-- Opt-in `style/inline-code` joins multiline code spans without changing their
-  parsed content, including spans in lists and blockquotes.
-- `style/wrap.measure: "codepoints"` counts Unicode scalar values instead of
-  display columns. Display columns remain the default.
-- `style/wrap.reportUnreflowed` and `reportUnbreakable` optionally explain
-  protected paragraphs and remaining unbreakable overflow without changing
-  formatting safety or check-mode semantics.
-- `resolve.gitIgnored` and `resolve.nestedRepositories` opt into additional link
-  targets independently of files selected for linting or writing.
-- Repeatable `--exclude <path>` omits literal files or directory subtrees from
-  processing while preserving them in the link index. Filesystem aliases are
-  canonicalized consistently, including Windows short paths.
-- Opt-in `structure/initial-heading` checks for an initial level-1 heading after
-  optional YAML/TOML front matter. It never edits content.
-
-See
-[configuration](https://viell-dev.github.io/slop-markdown-tools/configuration.html)
-and [CLI workflows](https://viell-dev.github.io/slop-markdown-tools/cli.html)
-for options, defaults, and examples.
-
-## Performance and library API
-
-Workspace indexing is path-only until a target's headings or block IDs are
-needed. Fragment parsing, suffix lookups, and built-in schema validation reuse
-cached work within their documented lifetimes; custom schema IDs stay isolated
-between calls. A synthetic benchmark is available in `scripts/benchmark.mjs` in
-the source checkout. Validation on the original large workspace remains pending
-in [#23](https://github.com/viell-dev/slop-markdown-tools/issues/23); no
-persistent index cache or worker pool is included.
-
-`createWorkspace` accepts lazy Markdown source loaders and explicit directory
-entries. Exhaustive consumers of `LinkResolution.status` must handle the new
-`"directory"` result. Consumers constructing `ResolvedConfig` directly must
-provide `resolve` (use `{}` for the defaults); `resolveConfig()` provides it for
-normal callers. See the
-[library API](https://viell-dev.github.io/slop-markdown-tools/plugins.html).
-
-## Compatibility and project scope
-
-Beta.1 configurations remain supported. The CLI name and Node.js minimum are
-unchanged; new formatting and structural controls are opt-in.
-
-For users of intermediate source checkouts, these additions were removed before
-this release: `style/wrap.keepLabelWithAtom`, `--changed`, `--staged`,
-`structure/title-matches-filename`, `structure/metadata-line`, and
-`style/accidental-marker`. Remove those settings and implement consumer-specific
-policies in plugins or wrappers. Git callers can supply explicit paths while
-retaining workspace resolution; skip the CLI invocation for an empty selection.
-These removals do not remove any published beta.1 feature.
-
-Modified-date mutation remains consumer-owned. Semantic guards, conservative
-handling of unsupported constructs, and Obsidian's verified strict-line-break
-requirement remain in force. The plugin API and configuration are provisional.
-
-Repository maintenance now includes explicit issue-scope review and a documented
-label taxonomy. Full CI runs on Linux/Node.js 24, with compatibility and
-installed-package checks on Linux/Node.js 22 and Windows/Node.js 24.

package/docs/releases/0.1.0-beta.3.md

@@ -1,61 +0,0 @@
-# mdrefine 0.1.0-beta.3
-
-Third public beta of Markdown Tools. npm package: `mdrefine`; executable:
-`mdtools`. Requires Node.js 22.12 or newer. Upgrade with:
-
-```sh
-npm install --save-dev --save-exact mdrefine@0.1.0-beta.3
-```
-
-## Correct wrap diagnostics
-
-Protected paragraphs now distinguish breakable prose from indivisible inline
-atoms. A hard-break paragraph whose only over-width content is a long link, code
-span, or other protected atom no longer triggers `reportUnreflowed`. That
-overflow follows `reportUnbreakable`, including when reflow is skipped. A
-paragraph containing both causes can report both when enabled.
-
-Whitespace inside protected inline nodes is not a wrapping opportunity.
-Container prefixes count toward width; hard-break markers are excluded from
-protected-line width. Both diagnostic options remain disabled by default and
-propose no edits. Protected paragraph source remains unchanged.
-
-Fixed in [PR #36](https://github.com/viell-dev/slop-markdown-tools/pull/36),
-resolving [#34](https://github.com/viell-dev/slop-markdown-tools/issues/34).
-Regression coverage includes both hard-break forms, LF/CRLF, lists, quotes, task
-items, Unicode width measurement, and Obsidian's strict-line-break gate.
-
-## Faster formatting
-
-The formatter reuses the current parsed document between phases and for final
-diagnostics. It parses each changed candidate and validates its meaning before
-accepting it. Edit-range, overlap, oscillation, and convergence checks remain in
-force; no persistent cache or worker pool is introduced.
-
-A warmed synthetic benchmark improved approximately 2.3 times for input needing
-edits and 2.6 times for already-formatted input, with identical result hashes.
-On the reporter's 8,362-document, 36 MB workspace, `format --check --json` fell
-from 314 to 121 seconds, with the same 6,960 would-change files and no remaining
-diagnostics after formatting. These are workload-specific results, not a
-throughput guarantee.
-
-Implemented in
-[PR #37](https://github.com/viell-dev/slop-markdown-tools/pull/37), resolving
-[#35](https://github.com/viell-dev/slop-markdown-tools/issues/35).
-Original-workload validation in
-[#23](https://github.com/viell-dev/slop-markdown-tools/issues/23#issuecomment-5735871369)
-also confirms the beta.2 indexing improvements and correct link diagnostics; the
-performance issue is now closed. The source checkout includes
-`scripts/benchmark-format.mjs` for reproducible formatting measurements.
-
-## Compatibility
-
-No dependency, public API, configuration-schema, or Node.js minimum changes.
-Existing beta.2 configurations remain valid. Consumers enabling wrap diagnostics
-may see findings move from `reportUnreflowed` to `reportUnbreakable`; this is
-the intentional classification correction described above.
-
-The API and configuration remain provisional. Semantic guards, conservative
-handling of unsupported constructs, and Obsidian's verified strict-line-break
-requirement remain in force. Repository agent instructions now also prohibit
-self-references in GitHub issue and PR posts.

package/docs/releases/0.1.0-beta.4.md

@@ -1,50 +0,0 @@
-# mdrefine 0.1.0-beta.4
-
-Fourth public beta of Markdown Tools. npm package: `mdrefine`; executable:
-`mdtools`. Requires Node.js 22.12 or newer. Upgrade with:
-
-```sh
-npm install --save-dev --save-exact mdrefine@0.1.0-beta.4
-```
-
-## Callout header diagnostics
-
-An Obsidian callout title occupies one physical line. Over-width titles now
-follow `style/wrap.reportUnbreakable`, even when they contain spaces, instead of
-triggering `reportUnreflowed`. Body overflow is evaluated separately. A block
-identifier does not make its entire paragraph indivisible; existing atom-aware
-classification for those paragraphs is retained.
-
-Fixed in [PR #42](https://github.com/viell-dev/slop-markdown-tools/pull/42),
-resolving [#40](https://github.com/viell-dev/slop-markdown-tools/issues/40).
-
-## Direct callout body wrapping
-
-`style/wrap` now reflows supported Obsidian body prose directly below the
-callout header, without requiring or inserting a blank quote line. The header's
-physical line, title, folding marker, and container prefix remain intact. Body
-reflow retains quote and list prefixes, protected inline atoms, and line
-endings.
-
-The semantic fingerprint now distinguishes the title from body text, rejecting
-edits that move words across their boundary. Supported inline title formatting
-still works. Hard breaks, block identifiers, inline HTML, unsupported multiline
-syntax, and lazy or inconsistent quote continuations remain conservative cases.
-Inline syntax spanning the title/body boundary is left untouched by wrapping.
-
-Implemented in
-[PR #43](https://github.com/viell-dev/slop-markdown-tools/pull/43), resolving
-[#41](https://github.com/viell-dev/slop-markdown-tools/issues/41).
-
-## Compatibility and verification
-
-No dependency, public API, configuration-schema, or Node.js minimum changes.
-Existing beta.3 configurations remain valid. Both diagnostic options remain
-false by default and propose no edits. Consumers enabling them may see header
-findings move to `reportUnbreakable`. Obsidian wrapping still requires verified
-`strictLineBreaks: true`; CommonMark and GitHub behavior is unchanged.
-
-Regression coverage includes nested callouts, list containers, folding markers,
-LF/CRLF, both diagnostic flags, width modes, inline atoms, protected source,
-rule isolation, semantic preservation, idempotence, unsafe boundary edits, and
-CLI preview/write/check behavior. The API and configuration remain provisional.

package/docs/releases/0.1.0-rc.1.md

@@ -1,99 +0,0 @@
-# mdrefine 0.1.0-rc.1
-
-First release candidate of Markdown Tools. npm package: `mdrefine`; executable:
-`mdtools`. Requires Node.js 22.12 or newer. Upgrade with:
-
-```sh
-npm install --save-dev --save-exact mdrefine@0.1.0-rc.1
-```
-
-Release candidates publish to npm's `rc` channel, and `latest` follows them
-until the first stable release.
-
-## Fewer refused documents
-
-The formatter's safety check refuses a whole document, and withholds a whole
-`--write` batch, when a rule proposes an edit that would change the parsed
-meaning. Five built-in rules proposed such edits for ordinary input; each now
-produces a safe edit or leaves the construct alone:
-
-- `style/wrap` keeps fence openers, math and Obsidian comment markers, HTML
-  block starts, footnote definitions, `--` and `=` runs, and words ending in an
-  unescaped backslash attached to a neighbour instead of moving them to a line
-  boundary ([PR #68](https://github.com/viell-dev/slop-markdown-tools/pull/68),
-  resolving [#46](https://github.com/viell-dev/slop-markdown-tools/issues/46)).
-- `style/wrap` starts a task item's reflow after the checkbox and its separator,
-  so `[x]` and the following spacing survive
-  ([PR #64](https://github.com/viell-dev/slop-markdown-tools/pull/64), resolving
-  [#47](https://github.com/viell-dev/slop-markdown-tools/issues/47)).
-- `style/table` keeps each row's own cell count instead of padding short rows
-  with new cells
-  ([PR #61](https://github.com/viell-dev/slop-markdown-tools/pull/61), resolving
-  [#48](https://github.com/viell-dev/slop-markdown-tools/issues/48)).
-- `style/emphasis` and `style/strong` leave a node alone when the new marker
-  would touch an existing delimiter, such as `_*foo*_` or `*foo*_bar`
-  ([PR #67](https://github.com/viell-dev/slop-markdown-tools/pull/67), resolving
-  [#49](https://github.com/viell-dev/slop-markdown-tools/issues/49)).
-- `style/heading` escapes a trailing `#` run when converting a Setext heading,
-  so `Sharp #` becomes `## Sharp \#` rather than losing the `#`
-  ([PR #66](https://github.com/viell-dev/slop-markdown-tools/pull/66), resolving
-  [#50](https://github.com/viell-dev/slop-markdown-tools/issues/50)).
-
-## Obsidian link resolution
-
-Note names, folder paths, and heading subpaths now match case-insensitively in
-the Obsidian dialect, as Obsidian does, so `[[note]]` and `[[Note#heading two]]`
-resolve to `Note.md` and `## Heading Two`. Notes whose paths differ only by case
-are reported as ambiguous. Block identifiers still match exactly, and CommonMark
-and GitHub resolution stays case-sensitive
-([PR #69](https://github.com/viell-dev/slop-markdown-tools/pull/69), resolving
-[#51](https://github.com/viell-dev/slop-markdown-tools/issues/51)).
-
-## Line endings
-
-Documents that use bare carriage returns are reflowed with carriage returns and
-no longer end up with three line-ending styles. The line ending for new breaks
-is taken from the document's first line break; previously a `\r\n` anywhere in
-the document selected `\r\n`
-([PR #65](https://github.com/viell-dev/slop-markdown-tools/pull/65), resolving
-[#52](https://github.com/viell-dev/slop-markdown-tools/issues/52)).
-
-## Performance
-
-Measured on synthetic corpora with the scripts in `scripts/`:
-
-- Applying many edits and locating many diagnostics were quadratic in the number
-  of edits or findings; both are now linear
-  ([PR #58](https://github.com/viell-dev/slop-markdown-tools/pull/58) and
-  [PR #59](https://github.com/viell-dev/slop-markdown-tools/pull/59), resolving
-  [#53](https://github.com/viell-dev/slop-markdown-tools/issues/53) and
-  [#54](https://github.com/viell-dev/slop-markdown-tools/issues/54)).
-- `style/wrap` and `style/table` detect the line ending once per document
-  instead of once per paragraph
-  ([PR #60](https://github.com/viell-dev/slop-markdown-tools/pull/60), resolving
-  [#55](https://github.com/viell-dev/slop-markdown-tools/issues/55)).
-- Formatting computes the original fingerprint only when an edit produces a
-  candidate, reuses the final pass's findings instead of a fourth rule sweep,
-  skips directive scanning when no directive text is present, and traverses
-  trees with a plain walk. On a 2,000-note vault, `lint` is about a third
-  faster, formatting changed notes about 40% faster, and re-formatting already
-  formatted notes about half the time
-  ([PR #70](https://github.com/viell-dev/slop-markdown-tools/pull/70), resolving
-  [#56](https://github.com/viell-dev/slop-markdown-tools/issues/56)).
-
-## Compatibility and verification
-
-No public API, configuration-schema, or Node.js minimum changes. Existing beta.4
-configurations remain valid. `unist-util-visit` is no longer a direct dependency
-of the package. Behaviour differences to expect: nested emphasis such as
-`*__foo__*` is now left as written rather than rewritten to `___foo___`;
-documents mixing line endings follow their first line break; Obsidian vaults
-containing notes that differ only by case receive new ambiguity diagnostics.
-
-Regression coverage now includes direct tests for `style/heading`, wikilink
-rewriting, dialect marker edge cases, end-of-document directives and comments,
-CLI error paths, and a property test that mixes block-like atoms with list,
-task, and quote prefixes
-([PR #63](https://github.com/viell-dev/slop-markdown-tools/pull/63), resolving
-[#57](https://github.com/viell-dev/slop-markdown-tools/issues/57)). The API and
-configuration remain provisional until the first stable release.