@cosyte/dicom 0.0.15 → 0.0.16

package/CHANGELOG.md

@@ -1,5 +1,64 @@
 # Changelog
 
+## 0.0.16
+
+### Patch Changes
+
+- ce2975a: Fold the `Known limitations` sidebar category into `Troubleshooting`, so the shipped
+  `docs-content/sidebars.json` conforms to the documentation IA spine (`DOCS-STALE-BEHIND-IA040`)
+
+  No source, no public API and no parse behaviour changes. `docs-content/limitations.md` is not
+  renamed and not moved, and the page keeps its URL, so every existing link to it still resolves. One
+  sentence of its prose changes, for the reason given under THE PAGE NO LONGER DESCRIBES ITS OWN
+  POSITION below.
+
+  WHAT SHIPS. The top level of `docs-content/sidebars.json` goes from
+
+      intro, Installation, Quickstart, [Known limitations], Core Concepts, Guides, Troubleshooting
+
+  to
+
+      intro, Installation, Quickstart, Core Concepts, Guides, Troubleshooting[troubleshooting, limitations]
+
+  `Known limitations` was never on the canonical spine, which is
+  `[Overview, Installation, Quickstart, Core Concepts, Guides, API Reference, Troubleshooting]`.
+  The spine's own definition of Troubleshooting is "common error symptoms plus how to debug, plus
+  Known Limitations if the package surfaces them", so this is the label's canonical home rather than a
+  workaround for the lint. The two docs now sit under one heading in the order a reader meets them:
+  `troubleshooting` (what went wrong) then `limitations` (what will never work).
+
+  WHY IT WAS URGENT. `docs.cosyte.com` builds the released corpus and lints each package's SHIPPED
+  sidebar against that spine, in strict mode, where a non-canonical top-level label is a hard error.
+  A finding inside an ARCHIVED release is downgraded to non-gating info, because immutable bytes have
+  no remedy diff. The same finding against the CURRENT release gates, because the remedy is exactly
+  this: cut the next release. So the label sat dormant through `v0.0.14` and became blocking the
+  moment `v0.0.15` was published and became current. It was not a new defect, and it stopped the whole
+  site rebuilding, not just this package's pages.
+
+  WHICH MEANS THE FIX ONLY LANDS ON A RELEASE. `docs` reads `docs-content/` out of the release
+  artifact (`docs-content.tar.gz`), never out of `main`, so this changeset is load-bearing rather than
+  bookkeeping: without a new version the corrected sidebar never reaches the site.
+
+  THE CATEGORY IS NOT FORCED OPEN. The deleted category carried `"collapsed": false`, and
+  `Troubleshooting` deliberately keeps the Docusaurus default instead of inheriting it. That flag
+  existed to keep a one-item category permanently expanded so `limitations` read like a top-level
+  page, a need that disappears once the page lives inside a real two-item category. `Core Concepts`
+  keeps its `"collapsed": false` because it is the five-part reading spine of the package, not a
+  destination a reader navigates to on purpose.
+
+  THE PAGE NO LONGER DESCRIBES ITS OWN POSITION. `limitations.md` opened by claiming the boundary
+  "lives high in the navigation rather than at the end of a troubleshooting page", which this change
+  makes false in the one place a reader can check it: the page is now the last item of the last
+  category, immediately after the troubleshooting page. That sentence is rewritten to say what is
+  actually load-bearing, that the boundary is a page of its own rather than a closing paragraph, and
+  that the introduction and the cookbook link into it. Left alone it would have frozen into an
+  immutable release artifact and been correctable only by cutting yet another release, which is the
+  same failure this change exists to end.
+
+  NO `API Reference` CATEGORY IS AUTHORED HERE, and none may be. The docs site injects it at the
+  canonical position (immediately before Troubleshooting) from the package's generated API set;
+  hand-authoring it is a separate hard error in the same lint.
+
 ## 0.0.15
 
 ### Patch Changes

package/dist/index.cjs

@@ -11,7 +11,7 @@ var __export = (target, all) => {
 };
 
 // src/version.ts
-var VERSION = "0.0.15";
+var VERSION = "0.0.16";
 
 // src/dictionary/index.ts
 var dictionary_exports = {};