fabric-gen
Scaffold capability source, run independently versioned generators, and verify an application composition before deployment.
Create a compiler-valid capability without copying a repository template:
fabric-gen init capability case-review
fabric-gen init experience portfolio --directory apps/saas/modules/portfolio
fabric-gen init capability case-review --directory packages/case-review
init experience adds runtime, gateway, component-pack, and application-check
integration files to an existing Supastarter-derived application. It never creates or
replaces the application shell.
Initialization refuses to overwrite either README.md or
fabric.manifest.json.
fabric-gen --input fabric-manifest.json --out generated
fabric-gen --input fabric-manifest.json --out generated --check
--check performs no writes and fails for changed or stale artifacts. Generated files contain a
manifest digest and generator version, never timestamps.
Check the exact artifacts an application will load:
fabric-gen check-application --config fabric.application.json
fabric.application.json uses paths relative to itself:
{
"formatVersion": 1,
"assembly": "./fabric.assembly.lock.json",
"runtimeCapabilities": "./fabric.runtime.json",
"releases": ["./releases/web.json"]
}
The runtime file is an array of { "namespace", "version", "manifestDigest" }
objects derived from the modules actually registered by the application. The
check verifies lockfile integrity, rejects missing, extra, duplicate, or
mismatched runtime capabilities, verifies each promoted experience release,
and requires every release to name the same assembly digest. It does not
inspect caller assertions in place of runtime artifact metadata.