Editor Authored Content Workspace Manifest And Cache
Purpose
The editor authored-content workspace manifest gives tools one projection of scenes, catalog snapshots, dependency graph state, diagnostics, source manifests, and operation context. Use it when adding editor actions that open, rename, replace, repair, or inspect authored content.
Steps
- Load catalog and scene summaries through the workspace cache.
- Compare signatures, fingerprints, and the sorted enabled-validator ID selection before reusing projections.
- Read the manifest lanes needed by the editor surface.
- Use operation contexts for open, rename, replace, and repair actions.
- Disable actions when source ownership, dependency graph, or diagnostics are stale.
- When extension lifecycle changes, invalidate the old projection immediately and let the background service rebuild using only validators owned by enabled extensions. Background results are installed only when their captured validator selection is still the desired selection.
Expected Outputs
The manifest should identify available sources, diagnostics, dependency graph status, catalog snapshots, and operation availability. Cached projections should rebuild when input signatures or enabled validator IDs change. Validator selection is a first-class build input, while the diagnostics runner still caches completed work by provider ID, provider version, and provider input signatures.
Common Mistakes
Common mistakes include bypassing operation contexts, reusing a cache after a source moved, treating missing summaries as valid empty data, letting a repair action run with stale dependency owners, omitting validator lifecycle from the workspace key, or allowing a superseded background job to install reports after an extension toggle.
Recovery Paths
Refresh the workspace manifest, rebuild the affected cache lane, and inspect disabled action reasons. If summaries are unavailable, fix source loading before running rename or repair actions.