[WIP] Merge canary branch to trigger npm publication

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Objective

Merge the canary branch into main to trigger the automatic publication of @dportillo-ixs/htmldocs to npmjs.org.

Background

The canary branch now contains:

• ✅ Windows path fix from upstream PR Regenerate pnpm-lock.yaml to fix htmldocs to htmldocs-v2 rename #18
• ✅ Package name changed to @dportillo-ixs/htmldocs
• ✅ npm publication configured for npmjs.org

What this PR does

This PR merges all changes from the canary branch into main, which will:

1. Trigger the release.yml GitHub Actions workflow
2. Compile the package with pnpm run build
3. Publish @dportillo-ixs/htmldocs to npmjs.org using the configured NPM_TOKEN
4. Make the package available for installation via: npm install @dportillo-ixs/htmldocs

Changes included

• Windows path regex escaping fix for esbuild compatibility
• Package renamed from htmldocs to @dportillo-ixs/htmldocs
• Publication registry changed from GitHub Packages to npmjs.org with public access

Expected outcome

After merging this PR to main:

• The release workflow will automatically publish the package to npm
• Users can install the fixed version with: npm install @dportillo-ixs/htmldocs
• The fork becomes a maintained, working version of htmldocs with Windows support

This pull request was created as a result of the following prompt from Copilot chat.

Objective

Merge the canary branch into main to trigger the automatic publication of @dportillo-ixs/htmldocs to npmjs.org.

Background

The canary branch now contains:

• ✅ Windows path fix from upstream PR Regenerate pnpm-lock.yaml to fix htmldocs to htmldocs-v2 rename #18
• ✅ Package name changed to @dportillo-ixs/htmldocs
• ✅ npm publication configured for npmjs.org

What this PR does

This PR merges all changes from the canary branch into main, which will:

1. Trigger the release.yml GitHub Actions workflow
2. Compile the package with pnpm run build
3. Publish @dportillo-ixs/htmldocs to npmjs.org using the configured NPM_TOKEN
4. Make the package available for installation via: npm install @dportillo-ixs/htmldocs

Changes included

• Windows path regex escaping fix for esbuild compatibility
• Package renamed from htmldocs to @dportillo-ixs/htmldocs
• Publication registry changed from GitHub Packages to npmjs.org with public access

Expected outcome

After merging this PR to main:

• The release workflow will automatically publish the package to npm
• Users can install the fixed version with: npm install @dportillo-ixs/htmldocs
• The fork becomes a maintained, working version of htmldocs with Windows support

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.