Repository navigation
feat: read the catalogue from each project's own record - #67
Merged
Merged
Conversation
kieronlanning
enabled auto-merge (squash)
November 15, 2026 10:10
The record for a project now lives in that project's repository at .config/purview-docs.yml, and the site reads it at build time from the default branch. A project owns its own words and pointers, so the record changes in the same pull request as the thing it describes instead of drifting in a second repository: zodsharp's record still listed net8.0 and net9.0 two releases after the project dropped them. - Discovery is the organisation's repository list: a repository that publishes the file is a catalogue project, so joining the catalogue needs no pull request here. - The 18 records that lived here are deleted, each having been published to its project repository first. - Fetched records are cached under src/.cache/manifests and snapshotted into src/fixtures/manifests, so rendering never performs network I/O and an offline build still resolves the whole catalogue. - A record a project owns wins over a local file with the same id, and the leftover copy is reported by `just check-projects` so it gets deleted. - ADR 0013 records the decision and its consequences.
kieronlanning
force-pushed
the
feat/project-owned-catalogue-records
branch
from
November 15, 2026 10:12
3c92dfe to
7cdb522
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The catalogue record for a project now lives in that project's own repository, at
.config/purview-docs.yml, and the site reads it at build time from the default branch (ADR 0013, added here).Why: every entry under
src/src/data/projects/was written here, by this repository, for projects that live elsewhere and move without asking. That is a drift engine with no detector —zodsharp's record still listednet8.0andnet9.0two releases after the project dropped them — and correcting any of it meant a cross-repository pull request, which is exactly the friction that makes a record stale.What changes:
sync-manifestslistspurview-dev's repositories and reads.config/purview-docs.ymlfrom each; a 404 means "not a catalogue project". Joining the catalogue is one file in the project's repository and no pull request here.src/.cache/manifests/manifests.json(gitignored) withsrc/fixtures/manifests/index.jsonas the committed offline snapshot;DATA_MODEselects live/auto/cache/fixture, so rendering never performs network I/O.just check-projectsrather than silently ignored — the migration path for the rest of the catalogue.projects[zodsharp] (purview-dev/zodsharp (.config/purview-docs.yml at main)).Evidence (all run against the live manifests):
bun test tests/unit— 362 pass, 0 fail (was 356; 6 new tests for the manifest cache and the loader).just check-projects— passed: 18 projects, 1 collaboration.bun run lint,bun run format:check— clean.Manifests synced: 18 project-owned record(s) from 19 repositories.src/src/data/projects/is gone entirely (git does not keep an empty directory), and the catalogue still resolves in full — offline from the fixture, live from the projects.Follow-up worth knowing: the site repository's canonical name is
purview-dev/purview-dev.github.io;purview-dev/purview-devis a rename alias. The new manifests name the canonical one, and this repository's own docs still use the alias in prose.