docs(plugins): .tabularium is the canonical manifest, not manifest.json - #595
Merged
debba merged 2 commits intoAug 7, 2026
Merged
Conversation
The host loads .tabularium first (installer MANIFEST_FILE) and reads manifest.json only as a legacy fallback; id is optional and identity falls back to name. Guide, tutorial and README still framed manifest.json with a required id + display name as the format. - guide/tutorial examples are now .tabularium (slug name, registry $schema, scaffold-matching kind/engine/paradigms) - manifest.schema.json no longer requires id, matching the host (ConfigManifest id: Option<String>) - publishing sections point at registry.tabularis.dev/submit; the registry.json PR is labeled the legacy path
…sh rules - registry.spitzli.dev (dead) -> registry.tabularis.dev in deep-link test fixture and type doc comment; tabularium.wiki/docs/#/... (404) -> docs.tabularium.wiki - document what the registry actually enforces: name slug pattern (pinned), version == tag minus v-prefix, description <= 280 chars, HTTP 422 hard-reject on invalid manifests - publishing steps now include the standalone .tabularium release asset (GitHub renames dotfiles to default.tabularium; registry accepts both) and client-side sha256 + JWS install verification - manifest-checklist: drop nonexistent id core field, .tabularium instead of manifest.json, add constraints + publishing section - tutorial example manifest was missing required version (would 422)
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (10 files)
Reviewed by step-3.7-flash · Input: 127.8K · Output: 31K · Cached: 2.4M |
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
2 participants
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.
Companion to the website-side fix (tabularis.dev/wiki/plugins already stopped presenting
manifest.jsonas canonical). The host has treated.tabulariumas the canonical on-disk manifest for a while (installer.rsMANIFEST_FILE = ".tabularium",manifest.jsonlegacy fallback incompat.rs,ConfigManifest.id: Option<String>with identity falling back toname) — the docs inplugins/still described the old world.Changes
.tabularium: directory trees, example manifest (slugname, noid, registry$schemawith?kind=driver, matching what@tabularis/create-pluginscaffolds since fix(create-plugin): make the scaffolded .tabularium pass registry validation; point docs at tabularis.dev #594), manifest-fields table (name= slug;iddocumented as optional legacy), lifecycle wording, install-locally step, and § 8 publishing now points atregistry.tabularis.dev/submitwith theregistry.jsonPR labeled as the legacy path..tabularium, registry$schema,kind/engine/paradigms).idremoved fromrequired(kept as optional property, documented as legacy), matching the host's actual behavior. The copy served attabularis.dev/schemas/plugin-manifest.jsonupdates automatically on the next website build.Docs + one schema-required-list change; no code touched.