Resource subsystem redesign: named roots, sidecar pairing, structured ops

CLAUDE.md

@@ -81,13 +81,14 @@ python run_tests.py
 - When logging an exception, pass the exception object to the logger overload (e.g. `_logger.LogError(ex, "...")`); do not interpolate `ex.Message` or `ex.ToString()` into the message string
 - Keep XML doc comments concise but informative: one or two `<summary>` sentences describing *what* the member does, written so a reader who hasn't seen the class can understand it. If one line would just rephrase the member name (e.g. `"Typed counterpart of X"`), use two — conciseness is the constraint, not the goal. Do not embed implementation rationale, caller behavior, or detail already carried by types (enums, records, nullable returns). Avoid inline formatting tags (`<c>`, `<list>`, `<item>`) and multi-paragraph `<remarks>` blocks; plain type names read fine without `<see cref>` prose in summaries
 - Interface members and public types in `Celbridge.Foundation` must always carry a concise `<summary>` — the Foundation abstractions are how a reader understands the system, so every interface method, public record, and public enum there needs enough comment to stand alone. Conversely, skip xmldoc on concrete-class members by default: the interface they implement already documents them, and duplicated comments drift out of sync with the implementation. Exception: when the implementation has behavior that isn't obvious from the signature (unusual threading constraints, hidden side effects, non-obvious failure modes, subtle invariants), add a brief note. Treat the exception as rare — if the summary would just restate the name or repeat the interface comment, skip it
+- Keep inline body comments terse — write only what a first-time reader needs to know that they can't read off the code. Don't narrate what the current change is about, don't recap rationale visible in the surrounding code, don't enumerate edge cases the reader can infer. If a comment approaches paragraph length, the code probably needs restructuring instead
 - Model user or programmatic cancellation as a typed success outcome (e.g., `Result<OutcomeEnum>` with a `Cancelled` value), not as `Result.Fail`; `Result.Fail` stays reserved for genuine errors (precedent: `OpenDocumentOutcome`, `CloseDocumentOutcome`)
 - Minimize `Result<T>` boilerplate at return sites: use implicit conversions (`return value;` for concrete types; `return Result.Fail("message");` for failures). For interface return types, use the `OkResult<T>()` extension from `ResultExtensions`. Always unpack `result.Value` into a named temporary variable before using it
 
 ## Architecture
 
 - Workspace-scoped services are transient and must NOT be injected via constructor DI. Access them through `_workspaceWrapper.WorkspaceService`:
-  - IWorkspaceSettingsService, IWorkspaceSettings, IResourceRegistry, IResourceTransferService, IResourceOperationService, IPythonService, IConsoleService, IDocumentsService, IExplorerService, IInspectorService, IDataTransferService, IEntityService, IGenerativeAIService, IActivityService
+  - IWorkspaceSettingsService, IWorkspaceSettings, IResourceRegistry, IFileStorage, IResourceTransferService, IResourceOperationService, IPythonService, IConsoleService, IDocumentsService, IExplorerService, IInspectorService, IDataTransferService, IEntityService, IGenerativeAIService, IActivityService
 - Project configuration: use `IProjectService.CurrentProject` (singleton) to access the current project, and `project.Config` for its config. To parse `.celbridge` files outside of project loading, use `ProjectConfigParser.ParseFromFile()`
 - The Foundation project (`Core\Celbridge.Foundation`) should only contain abstractions (interfaces, abstract classes), never concrete implementations
 - Never bypass `ICommandService` to call methods directly. Every important operation goes through the command service for automation and auditing support. If a command-based flow has a bug, fix it within the command service pattern (e.g., add new command options or fix the command handling logic)
@@ -100,7 +101,7 @@ Documents auto-save via `DocumentViewModel.OnDataChanged()` → per-view save ti
 - Do not add "discard unsaved changes?" prompts on close — closing always saves.
 - Programmatic edit commands (`EditFileCommand`, `MultiEditFileCommand`, `ReplaceFileCommand`, `ApplyRangeEditsCommand`, `WriteFileCommand`, `WriteBinaryFileCommand`) write straight to disk; there is no editor-routed code path. When the target file is open, the on-disk write triggers a watcher event and the document buffer reloads from disk via `editor.setValue`, which clears Monaco's undo history. Preserve that contract when adding new edit code paths — do not route writes through the open editor, and do not try to preserve undo state across a programmatic write.
 - External edits always win: if a watcher event arrives while a save is queued or in flight, the save is discarded and the buffer reloads from disk. `DocumentViewModel.SaveTextToFileAsync` also raises `ReloadRequested` when the post-write disk hash differs from what we intended to write (i.e. an external write interleaved).
-- `MonitoredResourceChangedMessage` fires on every save; `DocumentViewModel` filters self-triggered events by hash. New consumers should expect high-frequency events.
+- `ResourceChangedMessage` fires on every save; `DocumentViewModel` filters self-triggered events by hash. New consumers should expect high-frequency events.
 
 ## MCP Tools
 

Source/Celbridge/Package.appxmanifest

@@ -5,7 +5,7 @@
   xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities"
   IgnorableNamespaces="uap rescap">
 
-  <Identity  Name="org.celbridge.Celbridge" Version="0.2.7.0" Publisher="CN=AnTulcha"/>
+  <Identity  Name="org.celbridge.Celbridge" Version="0.3.0.0" Publisher="CN=AnTulcha"/>
   <Properties >
     <DisplayName>Celbridge</DisplayName>
     <PublisherDisplayName>celbridge.org</PublisherDisplayName>

Source/Celbridge/Resources/Strings/en-US/Resources.resw

@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?>
+<?xml version="1.0" encoding="utf-8"?>
 <root>
   <!-- 
     Microsoft ResX Schema 
@@ -566,6 +566,12 @@ Do you wish to continue?</value>
   <data name="ConsolePanel_PackageLoadErrorMessage" xml:space="preserve">
     <value>One or more packages failed to load. See the log for details.</value>
   </data>
+  <data name="ConsolePanel_ProjectCheckFindingsTitle" xml:space="preserve">
+    <value>Project Check Findings</value>
+  </data>
+  <data name="ConsolePanel_ProjectCheckFindingsMessage" xml:space="preserve">
+    <value>Project check found {0} issue(s). See log for details.</value>
+  </data>
   <data name="DocumentToolbar_SplitEditorTooltip" xml:space="preserve">
     <value>Split Editor</value>
   </data>
@@ -962,6 +968,15 @@ Do you wish to continue?</value>
   <data name="DocumentEditor_HtmlViewer" xml:space="preserve">
     <value>HTML Viewer</value>
   </data>
+  <data name="DocumentEditor_ProjectFile" xml:space="preserve">
+    <value>Project File</value>
+  </data>
+  <data name="DocumentEditor_PackageManifest" xml:space="preserve">
+    <value>Package Manifest</value>
+  </data>
+  <data name="DocumentEditor_DocumentContribution" xml:space="preserve">
+    <value>Document Contribution</value>
+  </data>
   <data name="WebView_NavigationPrompt_Title" xml:space="preserve">
     <value>Open external link</value>
   </data>

Source/Core/Celbridge.Commands/Services/CommandService.cs

@@ -106,8 +106,7 @@ public async Task<Result> ExecuteAsync<T>(
 
         if (executionResult.IsFailure)
         {
-            return Result.Fail($"Command execution failed")
-                .WithErrors(executionResult);
+            return Result.Fail(executionResult);
         }
 
         return Result.Ok();
@@ -134,8 +133,7 @@ public async Task<Result<TResult>> ExecuteAsync<TCommand, TResult>(
 
         if (result.IsFailure)
         {
-            return Result<TResult>.Fail(result.FirstErrorMessage)
-                .WithErrors(result);
+            return Result.Fail(result);
         }
 
         // The command populated ResultValue during its ExecuteAsync().

Source/Core/Celbridge.Foundation/Console/ConsoleMessages.cs

@@ -45,6 +45,13 @@ public enum ConsoleErrorType
     /// One or more packages failed to load during project discovery.
     /// </summary>
     PackageLoadError,
+
+    /// <summary>
+    /// The workspace-load project consistency check returned non-empty
+    /// findings (broken references, orphan .cel files, or broken .cel files).
+    /// The ConsoleErrorMessage.ConfigFileName field carries the summary text.
+    /// </summary>
+    ProjectCheckError,
 }
 
 /// <summary>