Template library
Reusable artifacts. The current development database has no published installable versions yet.
| Template | Type | Version | Status | |
|---|---|---|---|---|
◇ No published template versions yetCreate a draft, add content, validate it, then publish an immutable version before it can seed an app. Create first template | ||||
The library is intentionally empty until real artifacts are authored. A row is installable only when an immutable published version has a valid payload fingerprint. The CLI must implement this empty state instead of rendering fictional published templates.
Behind this page/templates · CanManageTemplates
Retrieve
List actual version rows, not catalog concepts. Published artifacts are immutable. Surface draft, published and archived status, payload fingerprint state, validation state and ownership scope. The current development database should return an empty published list.
Save
Read-only list. "New template" →sp_NewTemplateVersion creates a Draft to edit.Success
- No mock templates appear after API integration.
- Drafts can be edited; published versions cannot.
- Install actions require an exact version ID and validated fingerprint.
- Empty state links to authoring, not to a fake install.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.