@cosyte/terminology 0.0.10 → 0.0.11

package/CHANGELOG.md

@@ -1,13 +1,89 @@
 # Changelog
 
-All notable changes to this project will be documented in this file.
+## 0.0.11
 
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-Versions and publishing are managed with [Changesets](https://github.com/changesets/changesets);
-this file is maintained by hand (Changesets handles the version bump and publish only).
+### Patch Changes
 
-## [Unreleased]
+- 9b5b390: The npm `description` no longer carries an em dash (`EMDASH-CONFORMANCE`).
+
+  The brand rule bans U+2014 on every cosyte surface, and this string is the most visible one the
+  package has: it is the subtitle on the npm package page and the one line shown in every npm search
+  result. It now reads with a colon, which is what the rule's own remedy list names first.
+
+  Scoped deliberately to the description alone. The full tree sweep for this repo is a separate unit,
+  still queued, and lands with the CI gate that keeps it swept: a gate without the sweep reds CI on
+  arrival, and a sweep without the gate grows the character back.
+
+- 1374d15: `CHANGELOG.md` is now written by the release rather than by hand, so the copy inside every published tarball stops presenting already-shipped work as unreleased.
+
+  The file is listed in `package.json#files`, so it ships with the package. For the whole of this package's published history `.changeset/config.json` disabled Changesets' own changelog generation, which meant no release ever wrote a version heading into it and nothing ever rolled its single hand-maintained `[Unreleased]` heading over. Entries that had gone out sat under that heading beside entries that had not, with nothing to tell a reader which was which, while the package published its way to `0.0.10` on top of them. A later note in the same file described the changelog generator as off, which is a maintenance instruction pointing the wrong way inside a document a consumer reads.
+
+  The mechanism changed rather than the sentences: `changelog` now names the default Changesets generator, so each release writes its own version heading and the changeset summary becomes the entry a reader sees. Correcting the headings by hand would have left in place the mechanism that produced them, to produce them again on the next release.
+
+  The hand-written history is preserved verbatim, moved under a new `Released before this file was generated` heading with generated sections above it. No entry was reworded, re-ordered, re-wrapped or re-sorted, and this was measured against the registry rather than against the repository: every entry is byte identical to its copy inside the published `0.0.10` tarball, which is what an installed copy holds. What was dropped was scaffolding for the workflow that no longer runs, together with the prose it belonged to: the `[Unreleased]` heading, its link definition at the foot of the file, the preamble calling the file hand-maintained, and the note that described the generator as off. What release attribution the file had is kept rather than flattened: the heading that note sat under is retitled to name the versions its entries went out in, so a reader can still separate the entries that shipped in `0.0.10` from those that shipped across `0.0.2` through `0.0.9`, and from the dated `0.0.1` section below them. Two facts that note carried are kept because they remain true: no version between `0.0.2` and `0.0.10` has a section of its own, and `0.0.3` never reached npm.
+
+  The release's Prettier pass is left on, derived from this package having no `.prettierignore` and a format check that covers root markdown, so the archived history is already Prettier-canonical and comes through a release unchanged.
+
+  No runtime code, public API, type, diagnostic code or result changed.
+
+- 7ae2c1b: The README lockup now links to cosyte.com (`ASSETS`).
+
+  The `<picture>` block above the H1 is wrapped in an anchor to https://cosyte.com, per the founder
+  requirement of 2026-08-06. Nothing inside the block moved: the `<source>`, the `<img>`, the alt text
+  and both tile URLs are byte-identical.
+
+  What the anchor does was measured on both surfaces by `fhir`, not assumed, because fourteen READMEs
+  carry this shape. On GitHub the anchor works and the colour-scheme switch keeps working, because the
+  `<img>` stays a direct child of `<picture>`, which is the condition the HTML spec puts on `<source>`
+  applying at all. On an npm package page the anchor is lost: npm wraps a README image in its own
+  anchor to the image file, a nested anchor is not representable, so the parser closes ours early and
+  the image ends up linked to the image file rather than to cosyte.com. Shipped anyway by founder
+  decision of 2026-08-07: on npm that is no worse than the unlinked lockup it replaces, and GitHub is
+  where these READMEs are read.
+
+## Released before this file was generated
+
+Every release section above this heading is written by
+[Changesets](https://github.com/changesets/changesets) from the changesets in `.changeset/`, newest
+release first. The release writes its own version heading, so nothing above this line is maintained
+by hand: a change is recorded by adding a changeset, and that changeset's summary is the entry a
+reader sees here.
+
+Everything from here down to `## [0.0.1]` was maintained by hand, and all of it has shipped. It
+accumulated under a single `[Unreleased]` heading that no release ever rolled over, so the file mixed
+released work in with work that had not gone out and gave a reader no way to tell them apart, while
+the package published its way to `0.0.10` on top of it. What release attribution the file does have
+is carried by headings, and both of them are kept: the entries between here and the next heading went
+out in `0.0.10`, the entries under `Released in 0.0.2 through 0.0.9` went out across those versions
+without ever being split any finer, and `## [0.0.1]` below has a dated section and a release link of
+its own.
+
+The entries are left exactly as they were written rather than re-sorted into version sections:
+re-sorting would rewrite text that published tarballs already carry, and no version from `0.0.2` to
+`0.0.10` has a section of its own or a compare link. Measured against the registry rather than against
+this repository, because the registry is what an installed copy holds: every entry below is byte
+identical to its copy inside the published `0.0.10` tarball. Nothing below was reworded, re-ordered
+or re-wrapped; neither what was removed nor what was added is an entry.
+
+What was removed was scaffolding for the hand-written workflow that no longer runs, together with the
+prose that scaffolding belonged to: the `[Unreleased]` heading itself, its link definition at the foot
+of the file, the preamble that described this file as maintained by hand, and the note under the next
+heading, which described the generator as off and pointed at the work this change performs. That
+heading is kept and retitled to say which releases its entries went out in.
+
+One consequence is left standing rather than edited, because editing it would rewrite published text:
+an entry in the `0.0.2` through `0.0.9` block refers to "the `[Unreleased]` entry above", and no such
+heading exists any more.
+
+`0.0.3` never reaching npm is deliberate now, though it began as a consequence rather than a choice:
+a leftover changeset meant that release run only opened the next version PR, and the content shipped
+in `0.0.4`. It is not a hole to be filled, because publishing a `0.0.3` now would place it after
+`0.0.4` in registry order.
+
+The entries below follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the generated
+sections above use the format Changesets writes, which is a version heading and a list of the
+changes that release consumed. Versions follow the cosyte pre-alpha ladder, `0.0.x` until first
+alpha, rather than [Semantic Versioning](https://semver.org/spec/v2.0.0.html) alone.
 
 ### Fixed
 
@@ -248,26 +324,12 @@ test/fixtures/<name>` staged as `:120000 120000 <sha> <sha> R100` with **two** p
   file wins regardless of the argument allow-list and no argv-level pin can reach it. This change
   narrows nothing there, and the gate's docblock keeps stating it as the known limit it is.
 
-## Released, pending a per-version split
-
-> **Everything between this heading and `[0.0.1]` has already SHIPPED.** It accumulated under
-> `[Unreleased]` across the releases from `0.0.2` through `0.0.9`, because this file is maintained by
-> hand and the Changesets changelog generator is off (`"changelog": false` in
-> `.changeset/config.json`), so no release run ever moved an entry out of that section. Reading any
-> of it as work still awaiting a release was wrong, which is why the heading changed and the entries
-> did not.
->
-> **What is deliberately NOT done here, and is tracked as `TERMINOLOGY-CHANGELOG-GAP`:** splitting
-> this into one `## [x.y.z]` section per published version, and the founder-owned question of whether
-> to turn the generator on across the repos that share this layout. No version from `0.0.2` to
-> `0.0.9` has a section of its own below, and none has a compare link. The `[Unreleased]` link at the
-> foot of this file now spans `v0.0.9...HEAD`, which is what that section actually holds; it spanned
-> `v0.0.1...HEAD` while this block was mislabelled.
->
-> **`0.0.3` never reached npm, and LEAVING it that way is the deliberate part.** The gap itself was
-> a consequence, not a choice: a leftover changeset meant that release run only opened the next
-> version PR, and the content shipped in `0.0.4`. It is not a hole to be filled, because publishing a
-> `0.0.3` now would place it after `0.0.4` in registry order.
+## Released in 0.0.2 through 0.0.9
+
+These entries accumulated under `[Unreleased]` across those versions and were never split per
+version; none of them has a section of its own or a compare link. One entry below carries a
+`[Superseded]` annotation that was added during the `0.0.10` cycle, so that annotation shipped later
+than the entry it annotates.
 
 ### Changed
 
@@ -1322,5 +1384,4 @@ ladder (`0.0.x` until first alpha).
   `WARNING_CODES` entry, and the parse-oriented option/warning types). This package is an engine, not
   a parser; that placeholder surface never shipped.
 
-[Unreleased]: https://github.com/cosyte/terminology/compare/v0.0.9...HEAD
 [0.0.1]: https://github.com/cosyte/terminology/releases/tag/v0.0.1

package/README.md

@@ -1,7 +1,9 @@
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png">
-  <img alt="Cosyte: a plus mark set in two overlapping rounded squares, one solid and one outlined, beside the Cosyte wordmark" src="https://cosyte.com/tile/cosyte-lockup-tile-on-light-1200x300.png">
-</picture>
+<a href="https://cosyte.com">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png">
+    <img alt="Cosyte: a plus mark set in two overlapping rounded squares, one solid and one outlined, beside the Cosyte wordmark" src="https://cosyte.com/tile/cosyte-lockup-tile-on-light-1200x300.png">
+  </picture>
+</a>
 
 # @cosyte/terminology
 

package/dist/index.cjs

@@ -4776,7 +4776,7 @@ function approximateMatch(graph, query, options = {}) {
 }
 
 // src/index.ts
-var VERSION = "0.0.10";
+var VERSION = "0.0.11";
 
 exports.COMPLEX_MAP_SOURCE_SYSTEM = COMPLEX_MAP_SOURCE_SYSTEM;
 exports.DIAGNOSTIC_CODES = DIAGNOSTIC_CODES;