* docs(changelog): build fuller tracker drafts through v0.11.202
* docs(changelog): drop publication flags from tracker files
* docs(changelog): generate titles from tracker sections
* docs(changelog): format titles after version links
Split the single release-tracker.md (101 releases) into date-based files
of 25 entries each, and removed blank lines between #### subsection headings
and their content for a more compact format.
Files: release-tracker-2026-02-19.md through release-tracker-2026-04-04.md
Swaps the teal Mintlify defaults for OpenWork's actual brand palette:
light mode accent #011627 (dark navy), dark mode accent #3b82f6 (blue),
and buttons #011627 (navy) to match openworklabs.com CTAs.
* feat(docs): add changelog page generated from release tracker
Add a script (scripts/generate-changelog.mjs) that parses
changelog/release-tracker.md and generates a minimalistic
changelog.mdx for the Mintlify docs. Each entry shows the date,
a tag (New/Improved/Adjusted/Misc), and either a one-liner (minor)
or bullet points (major). Version headings link to GitHub compare
URLs derived from consecutive versions.
* fix(docs): use Mintlify Update components and href tab for changelog
Switch changelog.mdx to use Mintlify's built-in <Update> component
with label, description, and tags props. Fix the tab config to use
href instead of pages.
* fix(docs): move changelog from tab to sidebar group
Place changelog as a grouped section in the sidebar navigation
instead of a separate tab that was causing redirect issues.
* fix(docs): plain version in description, link in body
The description prop renders as plain text in Mintlify, so markdown
links showed raw. Move version to plain description and put the
compare link as a "View changes" link inside the Update body.
* fix(docs): version as heading, multiple tags, Mintlify conventions
Use version as ## heading inside each Update body, support multiple
tags (New releases, Improvements, Deprecations), indent content
2 spaces per Mintlify convention, remove description prop.
* fix(docs): update changelog tags with emojis and new names
Tags are now: 🚀 New Features, 🐛 Bug Fixes, 🏗️ Refactoring
* feat(docs): group changelog entries by date
Merge same-day releases into a single Update block. Tags are
unioned across versions, Misc is dropped when real tags exist.
Each version remains as an ## heading within the grouped day.
* Revert "fix(i18n/zh): cleanups to Chinese translations (#1341)"
This reverts commit 03ee1f2f0e.
* Revert "feat(i18n): add Thai language + missing translations for all other locales (#1339)"
This reverts commit db0f94e36a.
* Revert "feat(i18n): extract en translations — session area (#1249)"
This reverts commit 3271af47b4.
* Revert "feat(i18n): extract en translations — pages (#1250)"
This reverts commit e006acade6.
* Revert "feat(i18n): extract en translations — context/lib/misc (#1251)"
This reverts commit c349413f09.
* docs: add internal release changelog tracker
Prepare a private release-tracking table for OpenWork so changelog summaries can be reviewed in-repo before anything is published publicly.
* docs: switch release tracker to markdown sections
Replace the release tracker table with oldest-to-newest markdown sections so new OpenWork releases can be appended more intuitively.
* docs: use subsection headings in release tracker
Replace top-level label bullets with subsections so release fields are easier to target while keeping list bullets only where they add structure.
* docs: make publication fields explicit booleans
Set the changelog and docs publication fields to explicit True or False values so the tracker has no ambiguous blanks.
* docs: add release size and importance fields
Track text-line diff size and a normalized major/minor release summary so each release entry can describe both scope and user impact in a machine-friendly way.
* fix(docs): restore migrated share skill links
Republish the example skill bundles on share.openworklabs.com so the docs point at live imports again, and align share bundle examples with the current publisher host.
* fix(server): use canonical shared bundle data urls
Rebuild trusted share fetch URLs to the share service's canonical /b/:id/data endpoint and cover the path with the live provider-config-helper bundle URL.
- Revised the "Importing a skill" documentation for clarity and consistency, including updated descriptions and instructions.
- Enhanced the AUR README to specify the removal of the bundled `/usr/bin/opencode` file to prevent conflicts with `opencode-bin`, ensuring compatibility with existing installations.
Updated dependencies to fix Next.js and React CVE vulnerabilities.
The fix-react2shell-next tool automatically updated the following packages to their secure versions:
- next
- react-server-dom-webpack
- react-server-dom-parcel
- react-server-dom-turbopack
All package.json files have been scanned and vulnerable versions have been patched to the correct fixed versions based on the official React advisory.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
- Add solid-devtools Vite plugin with locator (jsx/component locations) and
@solid-devtools/overlay, loaded before render in dev only.
- Treat baseline message fetch as complete for empty transcripts so
ensureSessionLoaded does not refetch on every prefetch/subagent ensure.
- When streaming delivers the first rows while non-idle, sync the batched
message list immediately so the blueprint empty state does not flash.
Made-with: Cursor
* fix(den): parse skill frontmatter when saving skills
Keep the full SKILL.md payload in the database, derive title and description from frontmatter, and require a frontmatter name in the API. Also include shared packages in the Den web Docker image so the upload flow can be verified end to end.
* fix(den-web): transpile shared utils package
Include @openwork-ee/utils in Next's transpilePackages list so the client skill editor resolves the shared frontmatter helpers during production builds.
* fix(den-web): keep skill parsing local to the app
Move the client-side skill markdown parser into the Den web app so production builds do not depend on resolving a workspace package boundary from a client component.
* refactor(den): share skill frontmatter parsing via utils
Make Den web and Den API both depend on @openwork-ee/utils for skill frontmatter parsing, refresh the workspace lockfile, and keep the Den web build wiring explicit for CI and Docker.
* fix(den-web): build Den from the monorepo root on Vercel
Keep the shared utils package setup, but make Vercel install and build from the repo root so workspace dependencies like @openwork-ee/utils are always available when Den web deploys from its app subdirectory.
* docs(den-web): keep Vercel workspace settings in the dashboard
Remove the app-level Vercel command override from the repo and document the monorepo install/build settings for the dashboard instead.
---------
Co-authored-by: src-opn <src-opn@users.noreply.github.com>
