Repository navigation
Description
Tracking issue for cutting v0.1.0, the first citable baseline. Everything below is the current state as of today, not a plan in the abstract — PR #4 has been open and green for a while, and the work that has accumulated on staging since then is what actually decides when it can go.
v0.1.0 means: the first git tag in this repo, the first GitHub Release with an attached data dump, and the first version of the standard anyone can cite. There are no tags yet in either textrefs/textrefs.org or textrefs/registry, so nothing here is a migration — it is all first-time setup.
0. Where this stands (2026-09-03)
Content is complete. Two mechanical steps remain, and both are maintainer
actions.
Sections 1 to 3 are done, every content item in §4 is ticked, and staging is at
ba908c7. #4 is MERGEABLE with all four checks passing (CodeQL, Analyze,
data, linkcheck); it is BLOCKED on one maintainer approval, nothing else. The
full npm run verify is green against the real registry: 0 astro check errors,
137/137 tests, 259,813 pages, all internal links valid.
What is left, in order:
- Dispatch
github-pagesonba908c7. The ruleset requires a deployment
for the SHA being merged, and Pages only auto-runs on push tomain. The last
dispatch was56cab1bon 2026-08-31, now eleven commits stale. Nothing
further is queued forstaging, so this is the last action before approval;
ifstagingmoves again, repeat it on the new tip. See §5. - Approve and merge chore(release): v0.1.0 — first citable baseline #4, then tag, then verify the release workflow. See §5,
and do theworkflow_dispatchdry run first —release.ymlhas still never
run andreferences.jsonlis now 69 MB.
What landed since the 2026-08-27 revision of this section, in eleven commits:
c41a230chore(deps): update dependencies before v0.1.0 #102 — dependency hardening. Clears theform-dataadvisory
(GHSA-hmw2-7cc7-3qxx) and confirms Build(deps): Bump the github-actions group with 2 updates #82 is superseded rather than pending.c9605b5fix(site): suppress the draft banner on the 404 page (#111) #126 — the 404 page no longer carries the draft banner (api: audit against the ReSed API-design criteria — 10 findings, 2 broken published URLs #111 G10).819fcb9docs(association): finalise the founding documents and limit Board members to expense reimbursement (#123) #124 — the association's founding documents, final. Closes the
§4 content item below, and ships F36 with it.d9239bdfix(site): let a whole-query label beat a split match in /find/ #138,990fc4fdocs(standard): state the tombstone projection rule correctly #140,257f17efix(site): keep redirects and untranslated fallbacks out of the sitemap #136,4d1c708perf(site): compile the registry once per build, not twice #139,
2d71119feat(standard): publish the TextRefs ontology #127,c360c02fix(standard): publish license_url as dcterms:rights, not dcterms:license #137,41f2d31chore(agents): track CLAUDE.md and document the GitHub workflow #141 — the/find/
whole-query fix, the tombstone prose correction, the sitemap rules, the
single-compile fix, the published ontology,license_urlasdcterms:rights,
and the agent-instruction gaps.bdd1d60docs(blog): announce the founding of the association #142 — the founding announcement. This was the last content item.ba908c7fix(site): render the resolver-target licence and rights correctly #143 — the resolver-target licence and rights chips
(Resolver-target licence tag shows a full URL instead of an SPDX identifier #133, Reference pages never render license_url, hiding rights for 54,380 targets #144). Found while reviewing feat(standard): publish the TextRefs ontology #127; both would have been frozen by the
tag.
On closing issues. The rule stated in item 1 of the old list — label rather
than close, because Closes does not fire from a merge into staging — has been
replaced in practice: an issue is now closed by hand as soon as its fix reaches
staging, with a comment naming the commit. No issue carries
addressed-in-v0.1.0 any more.
Everything else in this issue is history. The decisions in §2 and §4 are settled
and are not reopened here.
1. The dependency graph
textrefs.org textrefs/registry
------------ -----------------
#63 ADR-0005 preferred citation system ──┐ #11 docs: preferred/additional systems
└─ #67 ADR-0006 relation vocabulary ─┤ #13 ADR-0006 data reclassification
│ └─ based on #11
#71 resolver `vars` mapping ──► #72 ──────┤ #15–#19 resolver review
│ └─ #20 (on #13, blocked on #72)
staging ◄─────────────────┘
│
#4 Release v0.1.0: staging → main
│
tag v0.1.0 → release.yml → GitHub Release + dump
#67 is stacked on #63; #13 is stacked on #11. The two repos are coupled: #67 (schema) and #13 (data) are one breaking change split across repositories.
The resolver review (#72 + #20, closing #71 and textrefs/registry#15–#19) is a second, later cross-repo pair with the same shape: #72 adds the vars resolver field to the compiler, #20 is the data that uses it. #20 is stacked on #13 and stays red until #72 reaches staging. Neither is a v0.1.0 blocker — see §4.
2. Decided: ADR-0005/0006 are in v0.1.0
This was the only real branch point, and everything else follows from it.
- Decided 2026-08-12: land feat(standard)!: preferred citation system and qualified /cite/ aliases (ADR-0005) #63 + docs(decisions): decide mapping relation vocabulary (ADR-0006) #67 first. ADR-0005 and ADR-0006 are in
v0.1.0. The rest of this issue now describes one path, not two.
Rationale, as recommended and now adopted. Both are breaking changes to identifier-bearing structures, and both re-mint IRIs. Before the first tag that costs nothing — every record is draft under ADR-0004 and no identifier has ever been published. After the tag, the same change costs a documented migration against a baseline people may already cite. This is the same timing argument ADR-0006 makes for itself, applied one level up. The counter-argument — that it delays a release which is already green — was weighed and not taken.
Two consequences follow immediately: #60 (ADR-0005), #58 and #59 (ADR-0006) are now v0.1.0 issues, closed by #63 and #67 respectively; and the merge sequence in §3 is the actual plan rather than one of two options.
3. Merge sequence
The two repos guard each other, so the order is not free. There are now two coupled schema+data pairs (#67/registry#13, then #72/registry#20), and the second cannot start until the first is through:
textrefs.orgCI requires thedata/submodule pointer to be an ancestor ofregistry/main(.github/workflows/validate.yml).registryCI validates its records againsttextrefs.org@staging(registry/.github/workflows/validate.yml).
For a coordinated schema+data change neither side can go green first. Sequence:
- 1. Merge feat(standard)!: preferred citation system and qualified /cite/ aliases (ADR-0005) #63 (ADR-0005) →
staging. - 2. Merge docs: document preferred and additional citation systems registry#11 →
registry/main. - 3. Merge docs(decisions): decide mapping relation vocabulary (ADR-0006) #67 (ADR-0006) →
staging, accepting a reddatajob. It is red only because the pinned submodule commit predates the change; this needs an admin merge past a check that cannot pass beforehand. - 4. Retarget feat(works)!: reclassify mappings to alternateOf and isReferencedBy (ADR-0006) registry#13 from
docs/preferred-citation-systemtomain, confirm it is now green against the updatedstaging, merge. - 5. Bump
data/instagingto the newregistry/maintip.stagingis now fully green. - 6. Rebase feat(compile): map locator variables into a provider's own vocabulary (#71) #72 onto the updated
stagingand merge. Its diff currently carries the feat(standard)!: preferred citation system and qualified /cite/ aliases (ADR-0005) #63/docs(decisions): decide mapping relation vocabulary (ADR-0006) #67 commits underneath it, because GitHub cannot base a cross-fork PR on another fork's branch; after steps 1–5 it collapses to the singlevarscommit. Itsdatajob passes from step 5 onward. - 7. Retarget feat(works)!: resolver review — drop non-resolving targets, add NA28/BHS/SuttaCentral/NINJAL registry#20 from
feat/mapping-relation-vocabularytomainand merge. It cannot go green before step 6: registry CI validates againsttextrefs.org@staging, and the data uses thevarsfield that feat(compile): map locator variables into a provider's own vocabulary (#71) #72 introduces. - 8. Bump
data/instaginga second time, to theregistry/maintip carrying the resolver review. - 9. Update chore(release): v0.1.0 — first citable baseline #4 — it is
staging → main, so it picks all of this up automatically, but its description still describes a v0.1.0 without ADR-0005/0006 or the resolver review. Rewrite the summary, add both ADRs to the ADR list, and state the reference count the release actually ships.
All nine steps apply — going straight to #4 is off the table per §2, and steps 6–8 per §4.
4. Before tagging
-
chore(release): v0.1.0 — first citable baseline #4 is
BLOCKED, not failing. All four checks (CodeQL, Analyze, data, linkcheck) pass; it needs a maintainer approval to become mergeable. Confirm CODEOWNERS review is the only thing outstanding. -
CITATION.cffcarries noversionordate-released(CITATION.cff carries no version or date-released #51). This is a genuine release blocker: the file exists to make the release citable and currently cannot describe which release it refers to. Add both, and decide whether to reserve a Zenodo DOI now — theidentifiers:block is present but commented out. -
ROADMAP.md:27already claims the release happened: "done: Publish the Standard draft v0.1.0 as the first citable baseline (releasev0.1.0)". No tag exists. Either the tag lands in this cycle or the line is wrong; also mirror any edit intosrc/content/docs/community/roadmap.md, per the roadmap's own maintenance rule. -
Confirm the spec version story.
specification.md:9says0.1.0-draft,package.jsonsays0.1.0, and the standard pages carrymaturity: working-draft. ADR-0004 and ADR-0006 both deliberately declined a spec bump under theworking-draftclause. Make sure the tagv0.1.0and the spec's0.1.0-draftare understood as different things, and say so in the release notes. -
Regenerate
CHANGELOG.mdvianpm run changelog(git-cliff,cliff.toml). Verify it reads sensibly for a first release — git-cliff has never run against a tag boundary here. -
Close the
addressed-in-v0.1.0issues. Done 2026-09-02: the label now holds nothing open. Each issue was closed by hand with a comment naming the commit that fixed it, as soon as that commit reachedstaging, rather than waiting for the tag — see the note at the end of §0. As of 2026-08-27 the label held Non-SPDX license values are silently dropped from the published JSON-LD #46, Draft record pages are listed in the sitemap #47, github-profile submodule has no consumer #50, CITATION.cff carries no version or date-released #51, docs: Missing whitespace around inline elements on registry pages #53, feat: CitationSystem pages should list works instead of references #55, standard: owl:sameAs instead of skos:exactMatch #58, adr: Introduce a preferred Citation system #60, feat(compile): map locator variables into a provider's own vocabulary #71, docs: consistency audit — 41 findings across the standard, get-started, and mirrored root docs #79, docs: add more systems like IIIF #81, feat: collection endpoints for works and citation systems #83, feat: resolve a reference by work and locator without computing its UUID #84, adr: alternate labels and abbreviations for works #85, feat: resolve a familiar citation to a canonical reference at /find/ #90, feat: name every citation system a work uses in the Work record #91, adr: ranked search over alternative labels, and duplicate-hit disambiguation #92. Every issue this issue named earlier is either in that set or already closed, andtextrefs/registry#15–#19closed with registry#20. -
Label standard: owl:sameAs instead of skos:exactMatch #58, standard: replace skos:closeMatch to link to URL pages #59 and adr: Introduce a preferred Citation system #60
addressed-in-v0.1.0. They carry no labels at all today, so they do not show up in any query that drives the release checklist. -
feat: CitationSystem pages should list works instead of references #55 is already fixed on
stagingbut its issue is still open —03cee88 fix(site): list works instead of references on CitationSystem pages (#55) (#56). It ships in v0.1.0 whether or not anyone decides so; add it to the close-on-release list above rather than leaving it in the triage list below. -
Decided 2026-08-12: the resolver review ships in v0.1.0. feat(compile): map locator variables into a provider's own vocabulary (#71) #72 + feat(works)!: resolver review — drop non-resolving targets, add NA28/BHS/SuttaCentral/NINJAL registry#20 delete six resolver targets that do not address the cited passage, add NA28, BHS, SuttaCentral and NINJAL, and complete the New Testament (John only → 27 books) and the Tanakh (Genesis only → 39 books). So the first citable baseline covers two complete biblical corpora rather than one book of each, instead of publishing records named "New Testament" and "Tanakh" that resolve ~10% of their work. The cost is scale: the registry goes from ~39,200 references to 67,959, and with it
references.jsonlto 54 MB and the built site to 204,347 pages. See §5 and §6 for what that changes. (Superseded on size: chore(data): bump the registry pointer to 455bb27f #95 and chore(data): bump the registry pointer to 7d109195 #96 have since taken it to 86,397 references. The figures below are the current ones.) -
Last item before the release PR: publish the association's founding record. Done. The founding documents landed as
819fcb9(docs(association): finalise the founding documents and limit Board members to expense reimbursement (#123) #124) — statutes Art. 22 dated and signed by both signatories, Art. 15 narrowed to expense reimbursement after the cantonal tax office objected, theArbeitsentwurfreservation removed, and the assured tax exemption of 27 August 2026 stated on both index pages with its condition. The announcement followed asbdd1d60(docs(blog): announce the founding of the association #142). Original text: The tax authorities' decision and the foundational documents belong in the repo and on the site before v0.1.0 is tagged, as part of PR prep. The association section already carries statutes, governance, board, mission and expenses; the founding decision and constitutive documents are what make that section a record rather than a description, and the first citable baseline is the right place to freeze them. -
Triage what is deliberately not in v0.1.0. Re-run 2026-08-27 against every open issue. Three were pulled in and are now fix: link-check extraction, deprecated tombstones, orphaned component, docs label (#3, #99, #48) #101; seven stay out.
Pulled in (fix: link-check extraction, deprecated tombstones, orphaned component, docs label (#3, #99, #48) #101, open against
staging):- Link Checker Report #3 — the Link Checker Report. §7 asks for a clean report at tag time and it still listed 17 errors. Twelve were an extraction bug, not a broken link: the workflow stripped one unbalanced
)and then stripped trailing punctuation, so a URL ending a markdown link inside a sentence kept its)and lychee checked a truncated address. The trim now runs as a loop. 17 errors → 3. - Decide what a
deprecatedrecord page shows: ADR-0004 calls it a tombstone, the templates do not #99 —deprecatedrecord pages. A conformance gap between the spec and the templates, and the tag freezes the spec text, so the two sides ship in agreement. Decided 2026-08-27:deprecatedrenders the existing tombstone presentation withdeprecated-specific copy and the normalsuperseded_bytreatment.deprecated,withdrawnandblockedstay one tombstone category; their user-facing messages carry the difference in reach. This is option 2 in Decide what adeprecatedrecord page shows: ADR-0004 calls it a tombstone, the templates do not #99, and it needs no spec change —specification.md:284and theStatusenum already say it. - Delete the orphaned
CitationBox.astro#48 — the orphanedCitationBox.astro. Self-contained, no consumers, identicaldist/output.
Stay out:
- Single-source the draft and tombstone banner copy #100 (single-source the banner copy) — Decide what a
deprecatedrecord page shows: ADR-0004 calls it a tombstone, the templates do not #99 unblocks it, but it is an internal refactor with no user-visible change. Not worth astagingmove before the tag. - compile: references_range hardcodes the locator separator, so a colon-cited system cannot use it #94 (
references_rangeseparator) — the issue says so itself. It changes the authored data contract, andtextrefs/registry#23is parked behind it. - datapackage.json omits the Frictionless schema field descriptors versioning.md requires #74 (Frictionless field descriptors) — already deferred by design. chore(release): v0.1.0 metadata — CITATION.cff, changelog, checklist fixes #76 softened
versioning.mdtoSHOULDand recorded that exports through v0.1.0 omit it. - feat: Explore WebMCP support for agent-accessible text references #52 (WebMCP) — an exploration. feat: collection endpoints for works and citation systems #83 and feat: resolve a reference by work and locator without computing its UUID #84 shipped its data foundation.
- feat: client-side Reference UUID generator tool #42 (client-side UUID generator) — feat: resolve a reference by work and locator without computing its UUID #84 removed the lookup rationale; needs re-scoping to author-side minting first.
- discussion: should TextRefs integrate with n2t.net / ARK (and when)? #41 (n2t / ARK) and discussion: should TextRefs register the association in ROR (and when)? #40 (ROR) — open discussions. discussion: should TextRefs integrate with n2t.net / ARK (and when)? #41 has identifier-model implications and belongs after the resolver milestone; discussion: should TextRefs register the association in ROR (and when)? #40 is organizational metadata that touches no registry or standard surface.
(feat: CitationSystem pages should list works instead of references #55 was in the earlier version of this list and moved above — it is already on
staging. standard: revisit locator validation mechanism (regex + examples vs. alternatives) #9, deps: upgrade to Astro 7.1 #39, Mapping projection uses a denylist, so draft and deprecated mappings emit unqualified direct edges #45 and Build-time dependency hygiene: spdx-license-ids placement, unused markdown-satteri pin #49 have since closed.) - Link Checker Report #3 — the Link Checker Report. §7 asks for a clean report at tag time and it still listed 17 errors. Twelve were an extraction bug, not a broken link: the workflow stripped one unbalanced
-
Mapping projection uses a denylist, so draft and deprecated mappings emit unqualified direct edges #45 is stale, now that ADR-0006 is in — "Work SKOS projection uses a denylist" — the projection is no longer SKOS after ADR-0006, though the denylist itself (
TOMBSTONE_STATUSES) is unchanged. Retitle or close.
5. Tagging and release mechanics
-
Merge chore(release): v0.1.0 — first citable baseline #4 into
main. -
Tag
mainasv0.1.0and push the tag. This triggers.github/workflows/release.yml. -
Do the
workflow_dispatchdry run ofrelease.ymlbefore tagging. It checks out withsubmodules: recursive, runsnpm run build:data, and attachesdist/dump/*.jsonl+dist/dump/datapackage.json+aliases.jsonwithfail_on_unmatched_files: true. It has still never run. If a dump path is wrong the release fails after the tag is already public.The payload has grown twice since this line was written. Measured on
a5764fb(2026-08-27) with the fullnpm run verify:When this issue was opened After the resolver review Now References ~39,200 67,959 86,397 references.jsonl— 54 MB 69 MB (72,591,804 bytes) aliases.json— 12.9 MB 17 MB (17,521,319 bytes) Pages built — 204,347 259,811 Still far inside GitHub's 2 GB asset limit, but check the workflow's timeout headroom against the current build rather than the old one.
-
Confirm the three ADR links resolve.
identifier-syntax.md,mappings-and-resolver-targets.mdandrelated-systems.mdlink to ADR-0001, ADR-0002 and ADR-0006 atblob/main/decisions/….maincarries onlyADR-TEMPLATE.mdandREADME.mdtoday, so all three 404 and are the only real errors left in Link Checker Report #3. Merging chore(release): v0.1.0 — first citable baseline #4 brings all seven ADRs tomainand resolves them. Re-run the Links workflow after the tag to confirm. -
Confirm the pinned
data/commit at tag time is the one you want frozen into the release —main"consumes pinned SHAs at release time" per the registry workflow's comment. -
Check the generated release notes (
generate_release_notes: true) against the git-cliffCHANGELOG.md; two sources of truth, decide which one leads.
6. Registry side
- The registry uses calendar tags
vYYYY.MM.Nand has none yet. Decide whether v0.1.0 of the standard is accompanied by a first registry export tag, or whether the dump attached to this release is sufficient for now. -
datapackage.json's SemVer-without-vversion needs to be set deliberately for the first export. - The first export ships 86,397 references across 23 works and 13 citation systems — 86,477 records and 172,838 aliases — not the ~39,200 in
stagingwhen this issue was opened, and not the 67,959 the §4 decision produced. chore(data): bump the registry pointer to 455bb27f #95 and chore(data): bump the registry pointer to 7d109195 #96 advanced thedata/pin to7d10919afterwards, adding Dante's Divina Commedia, Hume's Treatise and first Enquiry, and eight Nietzsche works. Say the current figure in the release notes — it is the most visible difference between this baseline and anything cited from an earlier snapshot, and the earlier figure is now wrong in two places rather than one.datapackage.jsonis at version0.1.0.
7. Housekeeping
- Close the dependabot PRs still pointing at
main— Build(deps): Bump the github-actions group with 2 updates #82, Build(deps): Bump nanoid from 3.3.12 to 3.3.18 #70, Build(deps): Bump js-yaml from 4.2.0 to 4.3.1 #69, Build(deps): Bump dompurify from 3.4.7 to 3.4.13 #66, Build(deps): Bump mermaid from 11.15.0 to 11.16.1 #65, Build(deps): Bump fast-uri from 3.1.2 to 3.1.5 #64, Build(deps): Bump postcss from 8.5.15 to 8.5.25 #57, Build(deps): Bump sharp, @astrojs/starlight, astro, starlight-blog and starlight-llms-txt #37, Build(deps): Bump svgo from 4.0.1 to 4.0.2 #35, Build(deps): Bump @astrojs/rss from 4.0.18 to 4.0.19 #33. ci(deps): point Dependabot version updates at staging #78 pointed new version updates atstagingand chore(deps): refresh all dependencies before v0.1.0 #73 landed every bump they carry, so these are superseded rather than pending: merging chore(release): v0.1.0 — first citable baseline #4 bypasses them. Close them at the tag with a note, rather than leaving ten stale PRs against the release branch. (deps: upgrade to Astro 7.1 #39 and Build-time dependency hygiene: spdx-license-ids placement, unused markdown-satteri pin #49 have since closed.) - github-profile submodule has no consumer #50: the
github-profilesubmodule has no consumer — resolve or document before the first release freezes the repo layout. - Link Checker Report #3 is the automated Link Checker report. fix: link-check extraction, deprecated tombstones, orphaned component, docs label (#3, #99, #48) #101 takes it from 17 errors to 3, and the three that remain are the
blob/mainADR links that merging chore(release): v0.1.0 — first citable baseline #4 fixes (§5). Re-run the workflow after the tag and confirm it reports zero.
Every decision is settled. ADR-0005 and ADR-0006 ship in v0.1.0 (§2, 2026-08-12), so does the resolver review (§4, 2026-08-12), and the deprecated rendering question is answered (§4, 2026-08-27). The merge sequence in §3 is through. What is left is §0: land #101, publish the founding record, dispatch Pages, approve and merge #4, tag, and close out.
Activity
maehr commentedon Aug 12, 2026
§3 merge sequence: all nine steps are through
stagingis ata958928and fully green. Both coupled schema+data pairs landed in order, and the second one is in too:staging5c2a6f3registry/main7818b6bstaging(reddata, as designed)7a94c0emain, green, merged0f00bd4data/bump #10e9c824aba818dmain, green, merged237e39fdata/bump #2a958928Both retargeted registry PRs needed a rebase rather than just a base change — their stacked bases had been squashed away — and both then went green against the updated
stagingexactly as §3 predicted.Six corrections to this issue
Investigating the merge gates turned up things this issue gets wrong or misses. Recording them here because several are now fixed:
mainruleset required status checks that could never report. It demanded contextsValidateandLinks— workflow names. The check-runs that actually report are the job namesdataandlinkcheck, so chore(release): v0.1.0 — first citable baseline #4 was waiting on two checks that will never arrive. Fixed: ruleset17092029now requiresdataandlinkcheck; all other rules untouched. §4's "confirm CODEOWNERS review is the only thing outstanding" was also wrong —require_code_owner_reviewisfalse; what chore(release): v0.1.0 — first citable baseline #4 actually needs is 1 approval (bypassable by org admin).mainruleset also requires a successfulgithub-pagesdeployment for the merged SHA, and Pages only auto-runs on push tomain— the live site is deployed by dispatching Pages onstagingmanually. So every timestagingmoves, chore(release): v0.1.0 — first citable baseline #4 needs a fresh Pages dispatch or it stays blocked. Not mentioned anywhere in this issue; it is now step 9.stagingis unprotected. §3 step 3 called for "an admin merge past a check that cannot pass beforehand". No bypass was needed — it was a normal merge.npm run changelogwill not produce a0.1.0section. With no tags andtag_pattern = "v[0-9]*", git-cliff emits## [Unreleased]. It needsgit-cliff --tag v0.1.0.CONTRIBUTING.md:126carries the same bug and is being fixed in the prep PR.release.yml. That workflow runsnpm run build:data= compile + validate, with noastro build. The ~8 min / 204,347 pages figure belongs tovalidate.yml'snpm run verify. Release-job timeout headroom is not a concern.datapackage.jsonviolates its own normative MUST.standard/versioning.mdrequiresschemafield descriptors per resource;writeDump(scripts/compile.ts) emits none. Decided: soften the spec text for v0.1.0 and file a follow-up for real Frictionless descriptors, rather than build them in the release critical path.Also settled: §6's "
datapackage.json's version needs to be set deliberately" needs no action — the compiler reads it frompackage.json, so it is already0.1.0.Two review findings fixed on the way through
Neither was a release blocker; both were merge-blocking conversations, and both turned out to be real:
toStringresolved toObject.prototype's method and expanded into a published URL instead of skipping the entry. Locator vars are now null-prototype and all map lookups are own-property;url_bywith more than one selector variable is rejected at parse time instead of silently dropping resolver targets per reference. Three new tests.52, contradicting the file's own rule that entries are the highest cited verse number, not the count printed. John 7:53 opens the pericope adulterae and chapter 8 already sat at the traditional 59, soJohn.7.53was unmintable. Fixed to53.The reference count changed
67,959, not 67,958 — the John 7:53 fix adds one. The New Testament now yields 7,954. Worth using the corrected figure in the release notes and
datapackage.jsondiscussion in §6.maehr commentedon Aug 12, 2026
Everything up to the tag is done
stagingis at0df2b27,#4isMERGEABLE, and the only thing standing between here andv0.1.0is a maintainer approval on #4. Step 9 of §3 is closed out: Pages was dispatched onstaging, so agithub-pagesdeployment exists for0df2b27— the exact SHA #4 merges — and #4's description has been rewritten around what the release actually ships.Landed since the last update
CITATION.cffversion/date-released (closes #51), changelog, checklist fixes,versioning.mdsoftening.TypeScript stays on 6.x.
typescript@7.0.2is out, butastro checkrefuses it — the native compiler does not expose the programmatic API@astrojs/language-serverneeds (withastro/roadmap#1321). Verified, not assumed.§4 triage: what was pulled in, and what stays out
Reviewing all open issues against the release (§4's last unchecked item), four were pulled in and the rest stay out deliberately:
In (#75):
github-profilesubmodule had no consumer, yet all four workflows cloned it viasubmodules: recursive. The tag freezes.gitmodules, so this was cheaper now than ever after.spdx-license-idsis required at build time; it now sits independencies.Out, and why: #74 (Frictionless descriptors — deliberately deferred, spec softened to match), #45 (mapping projection denylist — see below), #48 (component cleanup, no effect on published records), #42, #52, #9, #40, #41 (open questions and future features, none of which the tag constrains).
#45 is not obsolete. ADR-0006 renamed the relations but the denylist is unchanged — draft and deprecated assertions still project into the direct edges on
Workwithout a status qualifier, and since ADR-0004 keeps all data atdraft, every seed mapping in v0.1.0 ships that way. Retitled rather than closed.Closed as delivered: #39 (Astro 7.1, superseded by 7.2.1), registry#16–#19 (resolver review). #58, #59, #60, #71, #55, #53 are now labelled
addressed-in-v0.1.0so they show up in the release-close query, which they did not before.Pre-tag verification (§5)
The "this has never run" worry about
release.ymlis settled without touching GitHub.npm run build:datawas run locally against the tagged content and emits exactly what the workflow globs, sofail_on_unmatched_files: truewill not trip:validate-datareports 68,005/68,005 records valid. Aworkflow_dispatchdry run was deliberately not used: with no tag in the ref,action-gh-releasewould either fail or create a stray branch-named public release, and the local run exercises the same paths.Zenodo is ready. Both repositories already have an active webhook on
releaseevents, so the concept DOIs mint themselves on the first release — no Zenodo UI step is outstanding. (Those hook URLs embed an access token; worth not pasting hook listings anywhere public.)Link checker (#3) is clean — the latest
links.ymlruns onstagingare green and the report issue has not been touched since June.What remains
MERGEABLEwithdata,linkcheckand CodeQL green and a matchinggithub-pagesdeployment;reviewDecisionisREVIEW_REQUIREDand the author cannot self-approve, so this needs the second maintainer or the org-admin bypass.v0.1.0onmain, thenv2026.08.0onregistry/main(§6 — decided: the registry gets its own first tag and concept DOI).CITATION.cffand the README badge, and close theaddressed-in-v0.1.0issues.actions/setup-nodev6 → v7 (Build(deps): Bump the github-actions group across 1 directory with 2 updates #32) is the one real remaining bump; it is committed locally but needs a credential with theworkflowscope to push.maehr commentedon Aug 13, 2026
The documentation wave is in:
stagingis at3f6670e#80 is squash-merged. It resolves 40 of the 41 findings in #79 and all of #81, and it is the last content change planned before the tag.
This issue predates both, so the pre-tag picture has moved:
actions/setup-nodev6 → v7 — closes the one real remaining dependabot bump from §7 (#32)staging, so the ten superseded PRs stop reopening the §7 questionWhy the docs changed before the tag rather than after
Four of the audit findings would otherwise have frozen wrong statements into a citable baseline: §13's flagship
Workexample was invalid againstWork.safeParsefor want ofpreferred_citation_system_key(ADR-0005), the OpenAPI document advertisedapplication/jsonwhere the implementation emitsapplication/ld+jsonand omittedWork.creatorsentirely, and §14 required BCP 47 validation that all three schema layers implemented asminLength: 2. The last one is now a real sharedLanguageTag, mirrored into the OpenAPIpattern; all 12 registry language values still validate.Two findings were also publishing the wrong branching model — the contributing page told contributors to branch from and PR against
main, which is exactly the workflow this release does not use.#81 reframed the related-systems page around the layer each standard addresses and added IIIF, W3C Web Annotation, BIBFRAME, IFLA LRM and RAMEN, plus URN:NBN — which Appendix B of the spec already listed and that page did not.
Consequence for #4, and it is a blocking one
staginghas moved three times since #4's description was rewritten. Per correction 2 in my earlier comment, themainruleset requires a successfulgithub-pagesdeployment for the SHA being merged, and Pages only auto-runs on push tomain:So #4 needs a fresh Pages dispatch on
stagingat3f6670ebefore it can merge.dataandlinkcheckare re-running against the new tip on their own; the deployment is the one that will not appear by itself. This is the step that has to be repeated every single timestagingmoves, and it is worth doing last, immediately before the approval.§4 checklist
addressed-in-v0.1.0labelling — docs: add more systems like IIIF #81 is now labelled. docs: consistency audit — 41 findings across the standard, get-started, and mirrored root docs #79 stays unlabelled and open: F36, the legal-reservation notice missing from the English association pages, is deliberately excluded from docs: resolve the consistency audit before v0.1.0 (#79) #80 and belongs with the statutes batch, so the audit is 40/41 rather than done.Corrections to the earlier updates
npm testcount moved. Earlier comments and chore(release): v0.1.0 — first citable baseline #4's description cite 25 tests; docs: resolve the consistency audit before v0.1.0 (#79) #80 added the resolver-language and grandfathered-tag cases, so it is 30/30 now. Nothing else in the verification block changed.data/pin is stilltextrefs/registry@237e39f.What remains, unchanged from the last update
stagingat the final SHA.reviewDecisionis stillREVIEW_REQUIREDand the author cannot self-approve.v0.1.0onmain, thenv2026.08.0onregistry/main.CITATION.cffand the README badge, and close theaddressed-in-v0.1.0issues — docs: add more systems like IIIF #81 joins that list.fix(github): label the docs issue template with a label that exists
fix: pre-release cleanup — link check, deprecated tombstones, orphan (#3
maehr commentedon Sep 2, 2026
Open-issue reconciliation on 2026-09-02:
deprecatedrecord page shows: ADR-0004 calls it a tombstone, the templates do not #99, feat: resolve a familiar citation to a canonical reference at /find/ #90, adr: alternate labels and abbreviations for works #85, feat: resolve a reference by work and locator without computing its UUID #84, feat: collection endpoints for works and citation systems #83, docs: add more systems like IIIF #81, docs: consistency audit — 41 findings across the standard, get-started, and mirrored root docs #79, feat(compile): map locator variables into a provider's own vocabulary #71, adr: Introduce a preferred Citation system #60, standard: owl:sameAs instead of skos:exactMatch #58, feat: CitationSystem pages should list works instead of references #55, docs: Missing whitespace around inline elements on registry pages #53, CITATION.cff carries no version or date-released #51, github-profile submodule has no consumer #50, Delete the orphanedCitationBox.astro#48, Draft record pages are listed in the sitemap #47, Non-SPDX license values are silently dropped from the published JSON-LD #46, and Link Checker Report #3 as delivered on staging and included in PR chore(release): v0.1.0 — first citable baseline #4.docs(blog): announce the founding of the association (#142)