← Corpus / augment-it / issue
Changelog entries duplicated across augment-it/changelog/ and content/changelog--laerdal/
Eleven backfilled augment-it changelog entries currently live in two places. Either location can be the source of truth — but right now both are, and updates have to be made twice.
- Path
- issues/Changelog-Duplicated-Across-Splash-And-Laerdal-Collection.md
- Authors
- Michael Staton
- Augmented with
- Claude Code on Claude Opus 4.7 (1M context)
- Tags
- Tech-Debt · Changelog · Content-Duplication · Laerdal · Splash
What’s Duplicated
On 2026-05-12, eleven backfilled augment-it changelog entries were copied
(not moved) from the augment-it submodule into the lossless-content
submodule so they’d appear in the “Laerdal Changelog” toggle on the
consulting site (/workflow/laerdal and /log/laerdal-*).
| File (11×) | Source of truth | Copy |
|---|---|---|
2025-01-18_01.md | ai-labs/augment-it/changelog/ | content/changelog--laerdal/ |
2025-01-27.md | same | same |
2025-03-03_01.md | same | same |
2025-07-25_01.md | same | same |
2025-07-25_02.md | same | same |
2025-07-25_03.md | same | same |
2025-07-26_01.md | same | same |
2025-08-01_01.md | same | same |
2025-08-06_01.md | same | same |
2025-08-10_01.md | same | same |
2025-08-11_01.md | same | same |
The copies in content/changelog--laerdal/ have two extra frontmatter
fields injected at the top — project: "Augment-It" and
category: "Archive-Backfill" (or "Technical-Changes") — so they fit
the visual style of the five pre-existing Laerdal entries. Body content
and the rest of the frontmatter are byte-identical to the originals.
Why It Matters
- Edit drift. A correction to any of the eleven entries has to be applied in both places, or the splash and the consulting site will start telling slightly different stories about the same week of work.
- Tanuj’s commits show up twice on the consulting site already. The Laerdal collection had 5 pre-existing entries about Tanuj’s Phase-1 Next.js work; my backfilled copies add another 3 about his module-federation work. That’s fine — they’re complementary, not duplicative. The duplication concern is only between the splash’s source and the Laerdal copy of the same set.
Cleanup Options
Two reversible paths to a single source of truth:
-
Splash reads from
content/changelog--laerdal/. Modifyai-labs/augment-it/splash/src/content.config.tsso the changelog loader points at the Laerdal collection’s path (filtering onproject: "Augment-It"if the Laerdal collection ever broadens beyond augment-it). Delete the originals inai-labs/augment-it/changelog/. Tradeoff: splash now depends on thecontentsubmodule being checked out. -
Laerdal collection reads from
ai-labs/augment-it/changelog/. Modifysite/src/content.config.tsso the Laerdal collection’sglob()loader pulls from bothcontent/changelog--laerdal/ANDai-labs/augment-it/changelog/. Delete the copies incontent/changelog--laerdal/. Tradeoff: consulting-site build now depends onai-labs/augment-it/being present, which is true today but may not always be.
Option 2 is the more aligned choice — augment-it should own its own changelog, the consulting site should aggregate. Same pattern would benefit any future client project that ships its own splash.
How To Recognize It Was Done
ls content/changelog--laerdal/shows only the 5 original entries (or only entries that don’t have a sibling inai-labs/augment-it/changelog/).pnpm buildsucceeds in bothsite/andai-labs/augment-it/splash/./workflow/laerdalon the consulting site still renders all 16 entries.- The splash’s
/changelog/page still renders all 12 entries.
Related
- Original backfill work:
ai-labs/augment-it/changelog/2025-07-25_01.mdthrough2025-08-11_01.md. - Toggle wiring:
site/src/pages/log/[slug].astro(lines 14–51). - Laerdal layout:
site/src/layouts/LaerdalChangelogLayout.astro.