ReadonlyabandonedContracts never imported anywhere in the scanned repository.
ReadonlyassertedVariables a developer has re-acknowledged via dynamicAccess, freshly -- see ADR 0037.
ReadonlydependencyEvery contract's ownership/dependency summary.
ReadonlyindeterminateVariables accessed only via dynamic (computed) property access.
ReadonlyparseSchema-discovery parse warnings plus, since ADR 0014, any packages
resolution failures -- surfaced here too (not just from
generateEnvManifest/generateDocumentation) so a team relying only
on --ownership output still learns when a cross-package contract
failed to resolve.
ReadonlyscannedEvery surface actually scanned for usage -- see ADR 0036. Named explicitly next to unconsumedOwnedVariables so "no consumer found" is never read as a stronger claim than what was actually searched.
ReadonlyunconsumedOwned variables with no consumer found in the scanned repository.
ReadonlyunresolvedAdvisory only, never gates onOwnershipIssue -- a contract only
reaches here when an ambiguous barrel re-export makes "abandoned" or
"consumed" both unprovable.
Everything renderUsageReport needs to render the Dependency & Ownership Report -- deliberately independent of (not derived from)
GenerateUsageReportResultingenerate-usage.js, the same wayRenderDocsOptionsindocs.tsdoesn't derive fromGenerateDocumentationResult.generate-usage.tscomposes its own public result type from these building blocks instead, keeping this renderer module importable without its orchestrator.