ReadonlyblastOne entry per added/updated capability, or undefined when no DependencyModel was supplied -- an optional layer, matching --ownership/--flow's existing opt-in cost model (the usage scan isn't free).
ReadonlymanifestThe underlying manifest diff -- see diffManifestSnapshots.
ReadonlyrenamedEvery added-field/removed-field pair this run's currently-declared
renamedFrom values correlate into a single rename, sorted by
capability key then current name.
Only ever populated from an authored FieldDocs.renamedFrom -- never
guessed from name similarity, which is the same "prove it, never infer
it" rule AGENTS.md invariant 11 applies to every other derived fact
here. An additive view, not a filter: manifest.updatedCapabilities's
own fields.added/fields.removed still list a correlated rename's two
halves separately, so a consumer that doesn't know about this field
loses nothing.
Field-level only. CapabilityDocs deliberately has no renamedFrom
(see core/document.ts), so there is no renamedCapabilities -- a
capability-level rename has no authored field to correlate from, and
guessing one from a moved file would be exactly the inference this
model refuses to make.
ReadonlyschemaAlways CHANGE_MODEL_SCHEMA_VERSION.
data-cap's Change Model: the manifest diff, plus an optional blast-radius index.