This repository was archived by the owner on Nov 19, 2026. It is now read-only.
Repository navigation
Add dynamic CMS key registry and manifest sync - #1
Merged
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
The running CMS can register website-defined keys without a CMS catalog change. Import the recovered implementation from
ec11af0d-4ef6-44e3-8d47-cf832242a93c_30_a_all_code.tar.gz, compared withcms-main.zip; the original export matches source/base commite69a53e345c97a86d7cfb866cd0fcacea508963efile for file.Includes typed manifest helpers, shared field validation, a sync client and CLI, and a minor Changeset. Import review replaced custom error classes with functional factories, fixed prototype-named collection loading and inherited CLI command lookup, and enforced stale-head rejection for no-op syncs, with regression tests.
The legacy contract catalog and English seed remain for transitional tooling. Website manifest ownership, deploy integration and final legacy removal remain a separate handoff; this PR does not complete every phase of the archived plan.
Excluded generated contract builds and release packages,
.wranglercaches/databases,.dev.vars, macOS metadata and archived agent instructions. The repository's instructions remain intact. No export notes or disposablescripts/review.shrunner were present in either archive; neither was introduced. No relocations or binary replacements were needed.Evidence
After: Local D1 tests register keys through sync and serve their text, retain unused keys, freeze retired definitions, and preserve editor text.
bun run validate: 273 tests in 24 Worker/contract files, plus 27 Node CLI/release tests, all passing. Includes type checks, lint, formatting, complete contract/CLI builds, package packing and independent installation.constructor:toString, inherited command names, and stale expected heads on unchanged syncs.Merge Danger
Door: one-way for database schema adoption.
Rewrites
0001_init.sqlfor a fresh database, consistent with the archived plan and checked-in placeholder remote D1 IDs. This is not an upgrade migration for a database that has already applied the old schema. Preserve existing local data and use a fresh test database; hosted provisioning/deployment acceptance is not established by these tests.Blast Radius: CMS
Changes admin response shapes (coverage, key status), removes
/v1/admin/catalogin favor of public/v1/definitions, and changes the database schema. Coordinate web integration before deployment. The retained legacy seed tooling is transitional, not a completed web cutover.