@ai-ecoverse/slicc-spectrum 1.101.0 → 1.101.1

package/README.md

@@ -474,7 +474,7 @@ It closes, clearing the field, when the request leaves `waiting` or while the va
 #### `<slicc-updates>`
 
 Install / Update: component states, version changes, last checks, download and link counts, action buttons, failures with Retry, and collapsible install logs behind a quiet chevron, which stay open across a layout switch.
-A row with a pending version change (`from → to`, or a package's `version → offered`) and release notes shows a What’s new disclosure after the row's actions (in package rows, after the command chips), next to the Install log, `details[data-releases]` with `summary[data-action="whats-new"]`, which stays open across a layout switch like the log. It lists every release after the installed version up to the new one, newest first, each as `.release[data-version]` with its version linking to the release page (`a[data-action="release-notes"]`, named "Kernel 1.13.0 release notes") and its notes rendered as markdown in strict mode (`markdown(text, { strict: true })`: raw HTML tags are dropped and their text kept as plain text, only `https:` links stay links, and an image becomes a link with its alt text, so nothing loads; the notes' headings sit one level under the release's, through `level`). Notes over 8 KB (8,192 characters) per release are cut at the last line break before that, with "…" and a Read the full notes link (`[data-cut]`, named "Read the full notes for Kernel 1.13.0"); a release whose `url` isn't `https:` shows its version as plain text. The `<!-- cert-verify -->` block is dropped, and a block that starts with "certified" shows as a subtle Certified badge (`[data-certified]`); a heading line naming the version is dropped too, since the link already shows it. Without notes in the range there is no disclosure.
+A row with a pending version change (`from → to`, or a package's `version → offered`) and release notes shows a What’s new disclosure after the row's actions (in package rows, after the command chips), next to the Install log, `details[data-releases]` with `summary[data-action="whats-new"]`, which stays open across a layout switch like the log. It lists every release after the installed version up to the new one, newest first, each as `.release[data-version]` with its version linking to the release page (`a[data-action="release-notes"]`, named "Kernel 1.13.0 release notes"). Only the newest (`.release[data-newest]`) shows its notes; each older release is a collapsed header, `details.release` with `summary[data-action="release"]` holding the same chevron, its version link and badge across the full row and named "Kernel 1.12.2 notes, certified", that opens to its notes indented under its title and stays open across a layout switch like the disclosure (an older release without notes is a plain header). The notes are rendered as markdown in strict mode (`markdown(text, { strict: true })`: raw HTML tags are dropped and their text kept as plain text, only `https:` links stay links, and an image becomes a link with its alt text, so nothing loads; the notes' headings sit one level under the release's, through `level`). Notes over 8 KB (8,192 characters) per release are cut at the last line break before that, with "…" and a Read the full notes link (`[data-cut]`, named "Read the full notes for Kernel 1.13.0"); a release whose `url` isn't `https:` shows its version as plain text. The `<!-- cert-verify -->` block is dropped, and a block that starts with "certified" shows as a subtle Certified badge (`[data-certified]`); a heading line naming the version is dropped too, since the link already shows it. Without notes in the range there is no disclosure.
 An up-to-date row (no pending change) links its installed release with Release notes next to the version; an installed optional package without one links its npm page instead (`a[data-action="npm-page"]`, named "npm page for Biome 2.2.4"). Pins and additions in Your packages show no link. Every link opens in a new tab.
 An install shows one bar for update rows and package rows alike: it fills 0–50% while downloading and 50–100% while linking (`value` against `max-value="100"`). While the row runs it never goes back, not when pnpm's total grows and not when progress drops out between passes. While a download reports `bytes` with a total above 0, the first half fills by bytes and the value label reads "10.0 MB of 40.0 MB". Otherwise, and always while linking, the label falls back to the phase's "n of m" count. The bar starts at 0 again once the row settles.
 Opens at boot until the agent is ready without failures.

package/dist/slicc-ui.js

@@ -45180,6 +45180,21 @@ var SliccUpdates = class extends ModelElement {
       .release {
         min-width: 0;
       }
+      .older-releases {
+        display: grid;
+        grid-template-columns: minmax(0, 1fr);
+        gap: var(--swc-spacing-200);
+      }
+      .older-releases > details > summary {
+        width: 100%;
+      }
+      .older-releases > details[open]:not(:last-child) {
+        margin-block-end: var(--swc-spacing-200);
+      }
+      .older-releases > .older,
+      .older-releases > details > :not(summary) {
+        padding-inline-start: calc(var(--swc-workflow-icon-small) + var(--swc-spacing-75));
+      }
       .title {
         margin: 0;
         font-size: var(--swc-font-size-100);
@@ -45365,22 +45380,36 @@ var SliccUpdates = class extends ModelElement {
     const shown4 = date.toLocaleString("en-GB", { dateStyle: "medium", timeStyle: "short" });
     return b`<span>Checked <time datetime=${date.toISOString()}>${shown4}</time></span>`;
   }
+  #title({ release: release3, certified }, label) {
+    return b`${secure(release3.url) ? b`<a class="swc-Link swc-Link--standalone" href=${release3.url} target="_blank" rel="noopener noreferrer" data-action="release-notes" aria-label=${`${label} ${release3.version} release notes`}>${release3.version}</a>` : release3.version}${certified ? b`<swc-badge size="s" variant="positive" subtle data-certified>Certified</swc-badge>` : A}`;
+  }
+  #notes({ release: release3, body: body4, cut }, label, level) {
+    return b`${body4 ? b`<div class="markdown">${markdown(body4, { strict: true, level })}</div>` : A}
+      ${cut && secure(release3.url) ? b`<p class="cut" data-cut><a class="swc-Link swc-Link--standalone" href=${release3.url} target="_blank" rel="noopener noreferrer" data-action="release-notes" aria-label=${`Read the full notes for ${label} ${release3.version}`}>Read the full notes</a></p>` : A}`;
+  }
+  #older(key2, entry, label, level) {
+    const version2 = entry.release.version;
+    if (!entry.body) {
+      return b`<div class="release older" data-version=${version2}><p class="title" role="heading" aria-level=${level}>${this.#title(entry, label)}</p></div>`;
+    }
+    const id = `${key2}:${version2}`;
+    return b`<details class="release" data-version=${version2} ?open=${this.#logs.has(id)} @toggle=${this.#logs.details(id)}>
+      <summary data-action="release" aria-label=${`${label} ${version2} notes${entry.certified ? ", certified" : ""}`}>${chevron}<span class="title" role="heading" aria-level=${level}>${this.#title(entry, label)}</span></summary>
+      ${this.#notes(entry, label, level)}
+    </details>`;
+  }
   #whatsNew(key2, label, entries, level) {
     if (!entries.length) return A;
+    const [newest, ...older] = entries;
     return b`<details data-releases ?open=${this.#logs.has(key2)} @toggle=${this.#logs.details(key2)}>
       <summary data-action="whats-new">${chevron}What’s new</summary>
-      <div class="releases">${entries.map(
-      ({
-        release: release3,
-        body: body4,
-        certified,
-        cut
-      }) => b`<div class="release" data-version=${release3.version}>
-          <p class="title" role="heading" aria-level=${level}>${secure(release3.url) ? b`<a class="swc-Link swc-Link--standalone" href=${release3.url} target="_blank" rel="noopener noreferrer" data-action="release-notes" aria-label=${`${label} ${release3.version} release notes`}>${release3.version}</a>` : release3.version}${certified ? b`<swc-badge size="s" variant="positive" subtle data-certified>Certified</swc-badge>` : A}</p>
-          ${body4 ? b`<div class="markdown">${markdown(body4, { strict: true, level })}</div>` : A}
-          ${cut && secure(release3.url) ? b`<p class="cut" data-cut><a class="swc-Link swc-Link--standalone" href=${release3.url} target="_blank" rel="noopener noreferrer" data-action="release-notes" aria-label=${`Read the full notes for ${label} ${release3.version}`}>Read the full notes</a></p>` : A}
-        </div>`
-    )}</div>
+      <div class="releases">
+        <div class="release" data-version=${newest.release.version} data-newest>
+          <p class="title" role="heading" aria-level=${level}>${this.#title(newest, label)}</p>
+          ${this.#notes(newest, label, level)}
+        </div>
+        ${older.length ? b`<div class="older-releases">${older.map((entry) => this.#older(key2, entry, label, level))}</div>` : A}
+      </div>
     </details>`;
   }
   #releaseLink(label, version2, releases, npm) {