mdrefine 0.1.0-beta.1 → 0.1.0-beta.2

package/docs/quick-start.md

@@ -9,7 +9,7 @@ The CLI requires Node.js 22.12 or newer. Install the package in your document
 workspace:
 
 ```sh
-npm install --save-dev --save-exact mdrefine@0.1.0-beta.1
+npm install --save-dev --save-exact mdrefine@0.1.0-beta.2
 npx --no-install mdtools --help
 ```
 

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

@@ -0,0 +1,83 @@
+# 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.md

@@ -2,14 +2,15 @@
 
 ## Versions and availability
 
-These documents cover `mdrefine@0.1.0-beta.1`. The executable is `mdtools`;
+These documents cover `mdrefine@0.1.0-beta.2`. The executable is `mdtools`;
 prereleases use npm's `beta` channel. Read the
-[beta.1 release notes](releases/0.1.0-beta.1.md) for changes and limitations.
+[beta.2 release notes](releases/0.1.0-beta.2.md) for changes and limitations.
+The [beta.1 notes](releases/0.1.0-beta.1.md) document the initial release.
 
 The registry is the source of truth for package availability:
 
 ```sh
-npm view mdrefine@0.1.0-beta.1 version --registry=https://registry.npmjs.org/
+npm view mdrefine@0.1.0-beta.2 version --registry=https://registry.npmjs.org/
 ```
 
 An `E404` means the requested package or version is unavailable. A version in
@@ -17,6 +18,12 @@ this repository or its documentation does not imply publication. Check
 [GitHub releases](https://github.com/viell-dev/slop-markdown-tools/releases) for
 release announcements and downloadable artifacts.
 
+The initial beta was published locally under npm account `viell`. npm assigned
+both `beta` and `latest` to `0.1.0-beta.1` despite an explicit `--tag beta`;
+removing `latest` returned E400. Both tags were accepted for that release.
+Continue using `--tag beta` for subsequent betas and verify tags after
+publishing.
+
 ## Prepare without publishing
 
 Use Node.js 24 and npm 10 or newer from a clean checkout:
@@ -24,7 +31,7 @@ Use Node.js 24 and npm 10 or newer from a clean checkout:
 ```sh
 npm ci
 npm run release:prepare
-npm publish ./artifacts/mdrefine-0.1.0-beta.1.tgz --dry-run --ignore-scripts --access public --tag beta
+npm publish ./artifacts/mdrefine-0.1.0-beta.2.tgz --dry-run --ignore-scripts --access public --tag beta
 ```
 
 Preparation runs all checks, packs the allowlisted files, installs that exact
@@ -36,12 +43,15 @@ change.
 
 The manual **Release** GitHub Actions workflow performs the same checks plus a
 dependency audit and uploads the artifact for 14 days. Leave `publish` false to
-prepare only. CI independently checks Linux, macOS, Windows, and Node.js 22/24.
+prepare only. CI runs full checks on Linux/Node.js 24, compatibility tests on
+Linux/Node.js 22 and Windows/Node.js 24, and installed-package checks on all
+three targets.
 
 ## Publication prerequisites
 
 Publication requires explicit operator authorization. Preparing a PR or artifact
-does not supply that authorization. Before the first publication:
+does not supply that authorization. For subsequent releases, verify these
+prerequisites rather than repeating the completed bootstrap:
 
 1. Merge the release PR with all required checks passing. Review the tarball
    manifest, release notes, version, and registry name again.
@@ -56,10 +66,16 @@ does not supply that authorization. Before the first publication:
    token is stored in GitHub.
 4. Restrict the GitHub `npm-release` environment to `main` and configure an
    approval gate if an independent approver is available. Verify branch rules
-   still require PRs and the four CI checks. The workflow uses Node.js 24 and
+   still require PRs and the three CI checks. The workflow uses Node.js 24 and
    checks that npm supports trusted publishing.
-5. Only after authorization and authentication setup, set repository variable
-   `NPM_PUBLISH_ENABLED` to `true`. It is disabled during preparation.
+5. Repository variable `NPM_PUBLISH_ENABLED` is `true` after verified trusted
+   publisher setup. This enables the workflow's capability; it does not
+   authorize a release. Preparation uses `publish: false` regardless of this
+   variable's value.
+
+Trusted-publisher settings were verified on 2026-09-18. The first release used
+local authentication and has no OIDC provenance. For workflow releases, verify
+the publication job and the registry provenance attestations after each release.
 
 ## Publish an authorized beta
 
@@ -69,7 +85,8 @@ builds and checks the package again, verifies the artifact checksum, publishes
 that tarball to npm's `beta` channel with provenance, and creates a GitHub
 prerelease at the workflow's commit. Tags use exact versions without a `v`
 prefix. Stable publication deliberately needs a separate policy change; this
-workflow accepts only beta versions and never assigns npm's `latest` tag.
+workflow accepts only beta versions and requests the `beta` tag. See the
+initial-publication exception above before interpreting `latest`.
 
 For an authenticated first publication that cannot use OIDC yet, use the exact
 reviewed tarball with `npm publish <tarball> --ignore-scripts --access public
@@ -85,6 +102,12 @@ versions, tags, and release assets must never be overwritten; corrections use a
 new version. The workflow refuses an existing npm version or tag to make a
 partial release visible instead of silently accepting it.
 
+GitHub enforces immutability for future releases and their assets. Attach all
+assets before publishing a release. The existing beta.1 release predates that
+setting, so its assets are not retroactively locked; its version tag remains
+protected by the repository ruleset. Do not replace its assets or recreate the
+release to change that history.
+
 After publication, verify registry metadata, the `beta` dist-tag, a fresh
 installation, the GitHub release and its assets, and the documentation site. All
 subsequent changes, including prerelease maintenance, continue through PRs.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mdrefine",
-  "version": "0.1.0-beta.1",
+  "version": "0.1.0-beta.2",
   "description": "Configurable Markdown linting and formatting for CommonMark, GitHub, and Obsidian",
   "type": "module",
   "license": "MIT",