@kirchdev/duxt 0.5.0 → 0.5.1-dev-main.48-5d5fca9

package/README.md

@@ -125,7 +125,7 @@ Everything lives under the `duxt` key of `app.config.ts`. The keys most sites to
 Every text field takes a literal, an i18n key, or a per-locale record — a single-language site never sees the other two.
 
 > [!TIP]
-> The full surface — `navigation`, `sections`, `landing`, `feed`, `footer` and the rest — is typed, and the types are the documentation: [`app/types/duxt.d.ts`](app/types/duxt.d.ts) carries a comment per key explaining what it costs and when it is read.
+> The full surface — `navigation`, `sections`, `landing`, `feed`, `footer` and the rest — is typed, and the types are the documentation: [`packages/duxt/app/types/duxt.d.ts`](packages/duxt/app/types/duxt.d.ts) carries a comment per key explaining what it costs and when it is read.
 
 ## 🧪 Development
 
@@ -136,7 +136,7 @@ pnpm install   # wires the husky hooks
 pnpm check     # lint + format + typecheck + tests + policy parity + build + a11y
 ```
 
-The repo root **is** the layer — `nuxt.config.ts`, `content.config.ts`, `app/`, `modules/` and `server/` live there, and `package.json` points at them. `www/` beside it is the site that consumes the layer, and the development target: it deliberately carries the awkward cases — two repositories, four refs, one version of each lifecycle. It is not a template; the exemplary starting point lives in [`kirchDev/duxt-starter`](https://github.com/kirchDev/duxt-starter).
+A pnpm workspace driven by Turborepo. The layer is [`packages/duxt`](packages/duxt) — `nuxt.config.ts`, `content.config.ts`, `app/`, `modules/`, `server/` and the build-time modules under `build/`. [`apps/www`](apps/www) is the site that consumes it, and the development target: it deliberately carries the awkward cases — two repositories, four refs, one version of each lifecycle. The root holds only the workspace and meta configuration, plus `docs/`, which `apps/www` publishes. It is not a template; the exemplary starting point lives in [`kirchDev/duxt-starter`](https://github.com/kirchDev/duxt-starter).
 
 ## 🎨 Assets & branding
 
@@ -148,7 +148,7 @@ The mark is the package name with its first letter bracketed — `[d]uxt` — be
 Every asset, the colour values, why the icon's brackets are redrawn and the font licensing are in [Conventions → Branding](https://duxt.app/conventions/branding).
 
 > [!IMPORTANT]
-> The layer ships **no** branding. `duxt.logo` is unset by default, so `DuxtBrand` falls back to the consumer's own `duxt.title` beside a generic icon: a site extending duxt shows its own name in the header and footer and its own icon in the tab, never this one. These assets belong to this repository and to `www/`, not to the published package.
+> The layer ships **no** branding. `duxt.logo` is unset by default, so `DuxtBrand` falls back to the consumer's own `duxt.title` beside a generic icon: a site extending duxt shows its own name in the header and footer and its own icon in the tab, never this one. These assets belong to this repository and to `apps/www`, not to the published package.
 
 ## 🤝 Contributing
 

package/app/components/DuxtBrand.vue

@@ -8,7 +8,7 @@
  *
  * THE LAYER STAYS UNBRANDED. `logo` is unset by default and the fallback is a
  * generic book icon beside `title` — a site extending duxt must show its own
- * name, never this one. duxt's own `www/` sets `logo` like any other consumer,
+ * name, never this one. duxt's own `apps/www/` sets `logo` like any other consumer,
  * which is also what keeps the option honest: the development site exercises
  * the same path a stranger takes.
  */

package/app/components/DuxtBrunoEntries.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import type { DuxtBrunoEntry } from '../../bruno-model';
+import type { DuxtBrunoEntry } from '../../build/bruno/bruno-model';
 
 /**
  * A dictionary block — headers, query parameters, a form body — as a table.

package/app/components/DuxtCopyPage.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import { stripFrontmatter } from '../../frontmatter';
+import { stripFrontmatter } from '../../build/content/frontmatter';
 
 /**
  * The top action: hand this page to a model, or read its source.

package/app/components/DuxtLandingShowcase.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import { sourcesForRoute } from '../../sources-resolve';
+import { sourcesForRoute } from '../../build/sources/sources-resolve';
 
 /**
  * One feature, given a whole band: its prose on one side and the thing itself

package/app/components/DuxtOpenApiCallbacks.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import type { DuxtOpenApiCallback } from '../../openapi-model';
+import type { DuxtOpenApiCallback } from '../../build/openapi/openapi-model';
 
 /**
  * The requests the API sends BACK, and where it sends them.

package/app/components/DuxtOpenApiClient.vue

@@ -6,7 +6,7 @@ import type {
   DuxtOpenApiSecurity,
   DuxtOpenApiSecurityScheme,
   DuxtOpenApiServer
-} from '../../openapi-model';
+} from '../../build/openapi/openapi-model';
 
 /**
  * The try-it client: the one part of a reference that is not a document.

package/app/components/DuxtOpenApiMedia.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import type { DuxtOpenApiMediaType } from '../../openapi-model';
+import type { DuxtOpenApiMediaType } from '../../build/openapi/openapi-model';
 
 /**
  * One body, in each media type the document offers it in.

package/app/components/DuxtOpenApiParameters.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import type { DuxtOpenApiParameter } from '../../openapi-model';
+import type { DuxtOpenApiParameter } from '../../build/openapi/openapi-model';
 
 /**
  * The parameters an operation takes, grouped by where they go.

package/app/components/DuxtOpenApiResponses.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import type { DuxtOpenApiResponse } from '../../openapi-model';
+import type { DuxtOpenApiResponse } from '../../build/openapi/openapi-model';
 
 /**
  * The responses an operation can send, in the order the parser put them.

package/app/components/DuxtOpenApiSchema.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import type { DuxtOpenApiSchema } from '../../openapi-model';
+import type { DuxtOpenApiSchema } from '../../build/openapi/openapi-model';
 
 /**
  * One schema, drawn as the tree it is — and recursive, because schemas are.

package/app/components/DuxtOpenApiSecurity.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import type { DuxtOpenApiSecurity } from '../../openapi-model';
+import type { DuxtOpenApiSecurity } from '../../build/openapi/openapi-model';
 
 /**
  * What a request has to prove before the endpoint answers it.

package/app/components/content/BrunoOverview.vue

@@ -1,5 +1,8 @@
 <script setup lang="ts">
-import type { DuxtBrunoAuth, DuxtBrunoEntry } from '../../../bruno-model';
+import type {
+  DuxtBrunoAuth,
+  DuxtBrunoEntry
+} from '../../../build/bruno/bruno-model';
 
 /**
  * The collection's front page: what is in it, and how to get it.

package/app/components/content/BrunoRequest.vue

@@ -1,9 +1,9 @@
 <script setup lang="ts">
-import type { DuxtBrunoRequest } from '../../../bruno-model';
+import type { DuxtBrunoRequest } from '../../../build/bruno/bruno-model';
 import type {
   DuxtOpenApiOperation,
   DuxtOpenApiServer
-} from '../../../openapi-model';
+} from '../../../build/openapi/openapi-model';
 
 /**
  * One Bruno request, as the two columns of the reference.

package/app/components/content/OpenApiOperation.vue

@@ -4,7 +4,7 @@ import type {
   DuxtOpenApiSecurity,
   DuxtOpenApiSecurityScheme,
   DuxtOpenApiServer
-} from '../../../openapi-model';
+} from '../../../build/openapi/openapi-model';
 
 /**
  * One operation, as the two right-hand columns of the reference.

package/app/components/content/OpenApiOperations.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import type { DuxtOpenApiExternalDocs } from '../../../openapi-model';
+import type { DuxtOpenApiExternalDocs } from '../../../build/openapi/openapi-model';
 
 /**
  * The endpoints under one tag, as the list a reader scans.

package/app/components/content/OpenApiOverview.vue

@@ -4,7 +4,7 @@ import type {
   DuxtOpenApiSecurity,
   DuxtOpenApiSecurityScheme,
   DuxtOpenApiServer
-} from '../../../openapi-model';
+} from '../../../build/openapi/openapi-model';
 
 /**
  * The reference's front page: what the API is, where it lives, how to get in.

package/app/components/content/Partial.vue

@@ -1,5 +1,5 @@
 <script setup lang="ts">
-import { partialsCollection } from '../../../sources-resolve';
+import { partialsCollection } from '../../../build/sources/sources-resolve';
 
 /**
  * `:partial{name="install"}` — a block written once and rendered in every

package/app/components/content/ProseImg.vue

@@ -101,7 +101,7 @@ const props = withDefaults(
      * focus ring and the dialog were all switched off on every image in the
      * site. It survived from the day the component was written because nothing
      * in the repository rendered one: every `![…]` in the reference sits inside
-     * a code block. `www/demo/docs/3.images.md` and `check:images` are the two
+     * a code block. `apps/www/demo/docs/3.images.md` and `check:images` are the two
      * halves of making sure it cannot again.
      *
      * A default is what suppresses the cast — `isAbsent && !hasDefault` is the

package/app/composables/useDuxtCollection.ts

@@ -1,4 +1,4 @@
-import { sourcesForRoute } from '../../sources-resolve';
+import { sourcesForRoute } from '../../build/sources/sources-resolve';
 
 /**
  * Which collection serves the current route.

package/app/composables/useDuxtNavigation.ts

@@ -1,5 +1,5 @@
 import type { ContentNavigationItem } from '@nuxt/content';
-import { tfplugindocsNavigation } from '../../tfplugindocs';
+import { tfplugindocsNavigation } from '../../build/sources/tfplugindocs';
 
 /**
  * Which collections the navigation is being fetched from.

package/app/composables/useDuxtSearch.ts

@@ -1,4 +1,4 @@
-import type { DuxtResolvedSource } from '../../sources-resolve';
+import type { DuxtResolvedSource } from '../../build/sources/sources-resolve';
 import { searchSources } from '../utils/search-scope';
 // Imported rather than auto-imported, the same as `searchSources` above: this
 // composable is covered by a plain node test, which has no Nuxt globals.

package/app/types/duxt.d.ts

@@ -271,6 +271,23 @@ declare global {
     status?: DuxtSourceStatusInput;
     /** Lifecycle defaults by ref kind; an explicit ref status wins. */
     statusDefaults?: DuxtSourceStatusDefaultsInput;
+    /**
+     * Discover release tags to publish as versions, beside or instead of
+     * `refs`: every release, or the newest one per minor or major line. An
+     * explicit ref still overrides a discovered tag's label, lifecycle, default
+     * and locales. Pre-releases are left out unless asked for.
+     */
+    releases?: {
+      select: 'all' | 'minor' | 'major';
+      prereleases?: boolean;
+    };
+    /**
+     * The one package whose tags this source publishes, in a repository that
+     * tags `<component>@vX.Y.Z` — `'duxt'` reads `duxt@v0.4.0` and ignores
+     * `duxt-typesense@v0.1.0`. Applies to `latest` and `releases`; plain
+     * `vX.Y.Z` tags still count.
+     */
+    tagComponent?: string;
     /**
      * The repository a source read off disk lives in, for links back to it.
      * Not `repo`, which is what makes Content download a source.

package/app/utils/duxt-config.ts

@@ -76,7 +76,7 @@ export const duxtDefaults: DuxtConfig = {
     // the INTERFACE and not a tree or a repository. The dropdown that used to
     // sit beside it pointed at duxt's own tech stack — five links belonging to
     // this project and to no site that extends it. It lives in
-    // `www/app/app.config.ts` now.
+    // `apps/www/app/app.config.ts` now.
     { label: 'duxt.defaults.navigation.docs', icon: 'lucide:book-open-text' }
   ],
 
@@ -96,7 +96,7 @@ export const duxtDefaults: DuxtConfig = {
    *
    * Left empty, the row does not render and the sidebar falls back to the whole
    * tree, which is the right shape for a site that has not split its docs into
-   * sections at all. duxt's own sections live in `www/app/app.config.ts`.
+   * sections at all. duxt's own sections live in `apps/www/app/app.config.ts`.
    */
   sections: [],
 
@@ -107,7 +107,7 @@ export const duxtDefaults: DuxtConfig = {
    * whoever runs the site. Shipping duxt's own repository here gave a stranger
    * extending the layer a GitHub icon pointing at somebody else's project —
    * the same mistake the legal row already settled. kirchDev's own links live
-   * in `www/app/app.config.ts`, where they are an example rather than a
+   * in `apps/www/app/app.config.ts`, where they are an example rather than a
    * default.
    *
    * Their i18n keys went with them. `duxt.defaults.*` translates the defaults
@@ -130,7 +130,7 @@ export const duxtDefaults: DuxtConfig = {
     // something about the state of a project — "beta", "v2 is out" — and the
     // headline and the paragraph under it say what the project IS. The layer
     // knows none of the three. Those two were duxt's OWN marketing showing
-    // through every site that extended it; they live in `www/app/app.config.ts`
+    // through every site that extended it; they live in `apps/www/app/app.config.ts`
     // now, in the record form, because the Nitro routes that read them have no
     // i18n — see `server/utils/duxt-server-text.ts`.
     //
@@ -160,7 +160,7 @@ export const duxtDefaults: DuxtConfig = {
      *
      * Their translations left with them — `duxt.defaults.*` translates the
      * interface the layer draws, never content a site writes. duxt's own cards
-     * live in `www/app/app.config.ts`, where each one POINTS at the page that
+     * live in `apps/www/app/app.config.ts`, where each one POINTS at the page that
      * explains it, which the layer could never know.
      *
      * Left empty, the band does not render: the landing gates the whole section

package/app/utils/openapi.ts

@@ -18,7 +18,7 @@ import type {
   DuxtOpenApiResponse,
   DuxtOpenApiSchema,
   DuxtOpenApiServer
-} from '../../openapi-model';
+} from '../../build/openapi/openapi-model';
 
 /** How deep an example is derived before it is called recursive enough. */
 /**

package/app/utils/search-scope.ts

@@ -1,7 +1,7 @@
 import {
   sourcesForRoute,
   type DuxtResolvedSource
-} from '../../sources-resolve';
+} from '../../build/sources/sources-resolve';
 
 /** Select the editions participating in site-wide search. */
 export function searchSources(

package/app/utils/version-choices.ts

@@ -11,7 +11,10 @@
  * rest of it is: every version bug this layer has had came from prefix work
  * done inline in a component, where it could only be checked by clicking.
  */
-import { compareVersionTags } from '../../sources-resolve';
+import {
+  compareVersionTags,
+  parseVersionTag
+} from '../../build/sources/sources-resolve';
 
 /**
  * What a reader needs to see first: work that may change, the edition they
@@ -33,11 +36,11 @@ function compareEditions(a: DuxtResolvedSource, b: DuxtResolvedSource): number {
 
   const aVersion = a.version!;
   const bVersion = b.version!;
-  const semver = /^v?\d+\.\d+\.\d+(?:-.+)?$/;
 
-  // The shared comparator knows full tags. Demo editions such as `v3.x` are
-  // deliberately not tags, but still sort newest-first inside their group.
-  return semver.test(aVersion) && semver.test(bVersion)
+  // The shared comparator knows full tags, component-prefixed ones included.
+  // Demo editions such as `v3.x` are deliberately not tags, but still sort
+  // newest-first inside their group.
+  return parseVersionTag(aVersion) && parseVersionTag(bVersion)
     ? compareVersionTags(aVersion, bVersion)
     : bVersion.localeCompare(aVersion);
 }

package/app/utils/version-paths.ts

@@ -86,4 +86,4 @@ export function versionSwitchPath(
  * Nuxt scans for auto-imports, and `sources-resolve.ts` is plain logic with no
  * Node imports — the same property that lets `app.config.ts` read it.
  */
-export { versionRelation } from '../../sources-resolve';
+export { versionRelation } from '../../build/sources/sources-resolve';

package/bin/duxt-cache-key.mjs

@@ -37,8 +37,9 @@ Documentation: ${guide}`);
 
 const jiti = createJiti(import.meta.url, { interopDefault: true });
 
-const { duxtSourcesCache, runDuxtSourcesCacheCli } =
-  await jiti.import('../sources-cache');
+const { duxtSourcesCache, runDuxtSourcesCacheCli } = await jiti.import(
+  '../build/sources/sources-cache'
+);
 
 try {
   const rootIndex = argv.indexOf('--root');

package/bin/duxt-og-cache.mjs

@@ -41,7 +41,9 @@ Documentation: ${guide}`);
 
 const jiti = createJiti(import.meta.url, { interopDefault: true });
 
-const { duxtOgImageCacheCommand } = await jiti.import('../og-image-cache');
+const { duxtOgImageCacheCommand } = await jiti.import(
+  '../build/og-image/og-image-cache'
+);
 
 try {
   const { output, exitCode } = duxtOgImageCacheCommand(argv);

package/bin/duxt.mjs

@@ -26,8 +26,8 @@ process.removeAllListeners('warning');
 
 const jiti = createJiti(import.meta.url, { interopDefault: true });
 
-const { runDuxtCli } = await jiti.import('../cli');
-const { duxtReport } = await jiti.import('../report');
+const { runDuxtCli } = await jiti.import('../build/cli/cli');
+const { duxtReport } = await jiti.import('../build/cli/report');
 
 try {
   // `duxtReport` is passed rather than called: usage has to answer on a site

package/{bruno-parse.ts → build/bruno/bruno-parse.ts}

@@ -39,7 +39,7 @@ import type {
   DuxtBrunoParam,
   DuxtBrunoRequest
 } from './bruno-model';
-import type { DuxtSectionInput } from './sections-resolve';
+import type { DuxtSectionInput } from '../sections/sections-resolve';
 
 /** The manifest at the root of every Bruno collection. */
 const MANIFEST = 'bruno.json';

package/{bruno-zip.ts → build/bruno/bruno-zip.ts}

@@ -23,7 +23,7 @@
  * that rebuilds nightly does not publish a new download for a collection nobody
  * changed — the archive is a function of the files, and of nothing else.
  */
-import type { DuxtSectionInput } from './sections-resolve';
+import type { DuxtSectionInput } from '../sections/sections-resolve';
 import { BRUNO_UNPUBLISHED } from './bruno-parse';
 
 /** One file in the archive. */

package/{report.ts → build/cli/report.ts}

@@ -1,13 +1,13 @@
 import { join } from 'node:path';
-import { contentCacheFile, readContentCacheAt } from './content-cache';
-import { readDuxtBuildConfig } from './duxt-app-config';
-import { duxtManifest, duxtSectionTypes } from './sections-resolve';
-import { readSectionReports } from './section-reports';
-import { resolveLatestRefs } from './sources-git';
-import { redirectRules } from './modules/redirects';
+import { contentCacheFile, readContentCacheAt } from '../content/content-cache';
+import { readDuxtBuildConfig } from '../config/duxt-app-config';
+import { duxtManifest, duxtSectionTypes } from '../sections/sections-resolve';
+import { readSectionReports } from '../sections/section-reports';
+import { resolveLatestRefs } from '../sources/sources-git';
+import { redirectRules } from '../../modules/redirects';
 import type { Collected, PageRecord } from './validate-report';
 import { report, walk } from './validate-report';
-import type { DuxtResolvedSource } from './sources-resolve';
+import type { DuxtResolvedSource } from '../sources/sources-resolve';
 
 /**
  * The devtools tab's answers, as text a terminal — or a model — can read.

package/{validate-report.ts → build/cli/validate-report.ts}

@@ -8,9 +8,9 @@
  * can run the SAME checks against the pages the site is actually serving,
  * rather than reprinting a build log that has already scrolled away.
  */
-import { reservedSegments } from './sources-resolve';
-import { packageCommandIssues } from './app/utils/package-command';
-import { resolveDocumentationPath } from './app/utils/documentation-link';
+import { reservedSegments } from '../sources/sources-resolve';
+import { packageCommandIssues } from '../../app/utils/package-command';
+import { resolveDocumentationPath } from '../../app/utils/documentation-link';
 
 export interface PageRecord {
   collection: string;

package/{duxt-app-config.ts → build/config/duxt-app-config.ts}

@@ -1,8 +1,11 @@
 import { existsSync } from 'node:fs';
 import { join } from 'node:path';
 import { createJiti } from 'jiti';
-import type { DuxtSource, DuxtSourcesOptions } from './sources-resolve';
-import type { DuxtSectionTypes } from './sections-resolve';
+import type {
+  DuxtSource,
+  DuxtSourcesOptions
+} from '../sources/sources-resolve';
+import type { DuxtSectionTypes } from '../sections/sections-resolve';
 
 /** The build-time half of `app.config`'s `duxt` key. */
 export interface DuxtBuildConfig {

package/{git-contributors.ts → build/git/git-contributors.ts}

@@ -107,7 +107,8 @@ const SEPARATOR = '\u001f';
 const RECORD = '\u0001';
 
 /** The fields one record carries, in order. */
-const FORMAT = `${RECORD}%P${SEPARATOR}%an${SEPARATOR}%ae${SEPARATOR}%D`;
+const FORMAT =
+  `${RECORD}%H${SEPARATOR}%P${SEPARATOR}%an` + `${SEPARATOR}%ae${SEPARATOR}%D`;
 
 /** What git is asked, and the whole of why each flag is there. */
 const ARGUMENTS = [
@@ -119,10 +120,9 @@ const ARGUMENTS = [
   // bucketing those into the newest tag would credit people for work that has
   // not shipped.
   '--tags',
-  // Keeps a merged branch's commits together instead of letting their commit
-  // dates interleave them with another line of history. It is what makes the
-  // walk below equal to one `rev-list <previous>..<tag>` per release without
-  // paying for one `git` process per release.
+  // Children before their parents is what lets the pass below propagate a
+  // release through the graph. It does NOT make tag ranges contiguous: two
+  // parents of one merge may be walked in either order.
   '--topo-order',
   '--decorate=short',
   '--decorate-refs=refs/tags/*',
@@ -132,12 +132,18 @@ const ARGUMENTS = [
 /**
  * Every release tag, with the people whose commits it carries.
  *
- * ONE `git log` FOR THE WHOLE HISTORY, walked newest-first: a commit carrying a
- * tag OPENS that tag's release, and every commit after it in the walk belongs
- * there until the next tag opens the release before it. That is exactly the
- * range `<previous tag>..<tag>` names, and the alternative — a `git log` per
- * release — is the cost `modules/git-meta.ts` already paid once: the work is
- * never the history, it is spawning the processes.
+ * ONE `git log` FOR THE WHOLE HISTORY, walked children-first and reconstructed
+ * as a graph in memory. Every tag seeds a release number on its commit; that
+ * number flows to its parents, while an older tag replaces a newer number at
+ * its own boundary. A commit therefore belongs to the oldest tag that can
+ * reach it — exactly the set `<previous tag>..<tag>` names — without paying for
+ * one git process per release.
+ *
+ * THE GRAPH IS LOAD-BEARING. Tag markers do not delimit contiguous slices of a
+ * topo-ordered log: where a release merge has the older tag on one parent and
+ * new work on another, git may print the older tag before that parallel branch.
+ * A mutable "current tag" then gives the work to the release before it and
+ * leaves the release that merged it empty.
  *
  * A MERGE COMMIT SETS THE BOUNDARY AND CREDITS NOBODY. It has to be walked,
  * because release-please tags the merge commit its release pull request
@@ -149,40 +155,67 @@ const ARGUMENTS = [
 export function parseReleaseContributors(
   output: string
 ): Map<string, DuxtContributor[]> {
-  const commits = new Map<string, DuxtCommitAuthor[]>();
-  const contributors = new Map<string, DuxtContributor[]>();
-
-  /** The tags whose release the commits now being read belong to. */
-  let current: string[] = [];
+  const commits: {
+    hash: string;
+    parents: string[];
+    author: DuxtCommitAuthor;
+    merge: boolean;
+    tags: string[];
+  }[] = [];
+  const tagGroups: string[][] = [];
 
   for (const record of output.split(RECORD)) {
     if (!record.trim()) continue;
 
-    const [parents, name, email, decoration] = record
+    const [hash, parents, name, email, decoration] = record
       .split('\n')[0]!
       .split(SEPARATOR);
-
     const tags = tagsOf(decoration ?? '');
 
-    if (tags.length) {
-      current = tags;
-      for (const tag of tags) commits.set(tag, commits.get(tag) ?? []);
-    }
+    commits.push({
+      hash: hash ?? '',
+      parents: (parents ?? '').trim().split(/\s+/).filter(Boolean),
+      author: { name: name ?? '', email: email ?? '' },
+      merge: (parents ?? '').trim().includes(' '),
+      tags
+    });
 
-    if (!current.length) continue;
+    if (tags.length) tagGroups.push(tags);
+  }
 
-    // A merge carries more than one parent. It opened the release above and
-    // says nothing else.
-    if ((parents ?? '').trim().includes(' ')) continue;
+  /** The release each reachable commit belongs to, newest group numbered 0. */
+  const owners = new Map<string, number>();
+  const authors = tagGroups.map(() => [] as DuxtCommitAuthor[]);
+  let group = 0;
 
-    const author = { name: name ?? '', email: email ?? '' };
-    if (isGitHubApp(author)) continue;
+  // Seed every boundary before walking. A newer release reaches an older tag's
+  // commit too; the larger number there is what stops that propagation.
+  for (const commit of commits) {
+    if (!commit.tags.length) continue;
+    owners.set(commit.hash, group);
+    group += 1;
+  }
+
+  for (const commit of commits) {
+    const owner = owners.get(commit.hash);
+    if (owner === undefined) continue;
 
-    for (const tag of current) commits.get(tag)!.push(author);
+    // A merge carries more than one parent. It sets and propagates the boundary
+    // but says nothing itself; apps are omitted for the same reason as before.
+    if (!commit.merge && !isGitHubApp(commit.author)) {
+      authors[owner]!.push(commit.author);
+    }
+
+    for (const parent of commit.parents) {
+      const previous = owners.get(parent);
+      if (previous === undefined || owner > previous) owners.set(parent, owner);
+    }
   }
 
-  for (const [tag, authors] of commits) {
-    contributors.set(tag, contributorsOf(authors));
+  const contributors = new Map<string, DuxtContributor[]>();
+  for (const [index, tags] of tagGroups.entries()) {
+    const people = contributorsOf(authors[index]!);
+    for (const tag of tags) contributors.set(tag, people);
   }
 
   return contributors;

package/{search-records.ts → build/search/search-records.ts}

@@ -42,9 +42,9 @@
  * run it without a build.
  */
 import { createHash } from 'node:crypto';
-import type { CachedPage } from './content-cache';
-import type { DuxtResolvedSource } from './sources-resolve';
-import { duxtPageSearchable } from './app/utils/page-controls';
+import type { CachedPage } from '../content/content-cache';
+import type { DuxtResolvedSource } from '../sources/sources-resolve';
+import { duxtPageSearchable } from '../../app/utils/page-controls';
 
 /**
  * One entry of an external search index, as duxt hands it over.

package/{section-reports.ts → build/sections/section-reports.ts}

@@ -1,5 +1,5 @@
 import { join } from 'node:path';
-import type { DuxtResolvedSource } from './sources-resolve';
+import type { DuxtResolvedSource } from '../sources/sources-resolve';
 import type { DuxtSectionTypes } from './sections-resolve';
 import {
   duxtSectionTypes,
@@ -11,7 +11,7 @@ import {
   sectionArtefactExists,
   sectionInputKind
 } from './section-input';
-import { repositoryRoot } from './repository-root';
+import { repositoryRoot } from '../sources/repository-root';
 
 /**
  * Fill in what each LOCAL artefact had to say, for the manifest a module holds.